Agency comparison

Why classic agencies are often too slow for ongoing delivery

The agency isn't the problem – the project process is. Why small changes get stuck in quote loops, when project logic is still right and how an ongoing delivery system makes the difference.

Reading time approx. 9 minutes · Last updated 4 Sept 2026

Project pipeline versus delivery channel – the same task, two completely different routes to go-live

TL;DR

In short: why do agencies often feel slow for ongoing delivery?

Classic agencies are usually built around projects: briefing, quote, concept, delivery, sign-off. This model works well for clearly bounded initiatives, but can become slow when many small, ongoing tasks pile up. If every change has to be requested, costed, scheduled and approved again, friction builds up. Companies with regular demand for website changes, landing pages, web development or technical adjustments therefore often don't need another one-off project, but an ongoing delivery system. This is exactly where a developer flat, a website flatrate or software development as a subscription can make sense.

Many companies aren't unhappy because agencies do bad work. They're unhappy because the working model no longer fits the demand.

A good agency delivers clean concepts, thoughtful design and solid execution. The problem isn't quality, it's pace: anyone running marketing campaigns today, testing new offers, fixing technical errors, building landing pages and trying out digital ideas needs ongoing speed – not a new project every few months.

This article explains, objectively, how classic agency processes are structured, where they work brilliantly and where they hit their limits. No agency bashing – just an honest assessment of which model fits which kind of work.

How classic agency processes are structured

A typical agency process follows a clear chain of steps. This structure isn't accidental – it has evolved over years because it makes projects plannable and billable:

01Request: a company signals demand, usually by email or form
02Briefing: goals, scope and framework conditions are clarified
03Quote: the agency calculates effort, price and timeline
04Approval: the company reviews, negotiates and confirms
05Scheduling: the task is fitted into the agency's capacity
06Delivery: the team works through the task in the planned window
07Revision rounds: feedback is incorporated, often across several rounds
08Sign-off: the result is reviewed and formally accepted
09Invoice: the work is billed, the project is considered closed

This process creates structure, commitment and predictability. But it can become noticeably heavy for small, frequent tasks – not because any single step is wrong, but because the sum of these steps repeats for even the smallest change.

Why this process makes sense for one-off projects

For clearly bounded initiatives, classic project logic is still the right choice. It fits particularly well for:

01Relaunches with a defined start and end point
02Branding projects with a concept and creative phase
03Campaigns with a fixed timeframe and clear goal
04Complex concept phases that need calm and depth
05Clearly bounded projects with a defined scope
06Fixed budgets and deadlines set from the start

Why it slows down ongoing tasks

As soon as a one-off initiative turns into many small, recurring tasks, the same process shows its weaknesses:

01Every small task turns into a mini-project with its own briefing and quote
02Quotes and coordination often take longer than the change itself
03Approval loops block speed even though the task itself is small
04Capacity is scheduled project by project, leaving little room for short-notice requests
05Priorities inside the company shift faster than the agency process can react
06Customers end up doing too much coordination themselves: chasing, reminding, checking status

Real-world example

One price change, three weeks of lead time

01Situation

A retailer changes prices for two product categories and needs an adjusted landing page, a new form field and a homepage banner. Three small tasks, one week before the campaign starts.
02What happens

At the agency this becomes three requests, one combined quote, two scope questions, one approval round and a slot in the sprint after next. The campaign launches with old prices. In the delivery system the same three tasks land in the list, are prioritised the same day and go live reviewed within days.
03Result

The difference isn't in working time – that was similar in both cases. It's in the waiting time between steps. With ongoing demand, exactly that waiting time adds up to weeks.

Examples from everyday work

These situations are familiar from the daily operations of many companies – not as a criticism, but as a description of where project logic and ongoing demand collide:

Landing page for a new campaign

Marketing is planning a promotion in two weeks. The matching landing page first needs a quote – the campaign often starts before the page is ready.

A form isn't working properly

A contact form is losing enquiries. By the time the fix is requested, scheduled and delivered, valuable leads are gone.

An offer needs to go live today

A seasonal offer needs to be visible immediately. A classic change request often needs more lead time than the promotion itself lasts.

Tracking needs adjusting

A new campaign needs an extra conversion event. The technical change is small, but the path to get there often isn't.

A customer needs a new subpage

A new service should get its own page. Technically that's hours of work, but in a project process it often takes weeks.

The website needs correcting after feedback

Customers point out an error in a description. The fix itself is trivial, the route to making it usually isn't.

A web app needs a small feature change

An internal tool should display one extra field. Technically a minor change, organisationally often its own mini-project.

The real difference: project work vs. operating mode

Behind these examples lies a fundamental difference in mindset: agencies typically sell projects. A project has a start, an end and a defined result. That's exactly what the internal organisation is built around – from costing to capacity planning.

But companies increasingly need something else: digital operations. Websites, web apps and digital channels are rarely finished today. They get tested, adjusted, corrected, extended – continuously, not once.

Digital work is therefore no longer just launch, but permanent fine-tuning. Anyone who ignores this and keeps thinking in pure project logic slows themselves down systematically, regardless of how good each individual delivery is.

Cost logic

Steps per agency order

From request to invoice – and from scratch again for every change.

Steps in a delivery system

Report, triage, deliver, review, approve – no quote loop.

Decisive question

Is your demand a project with an end – or an operation without one?

Classic agency vs. ongoing delivery system

The following table sets both models side by side along the criteria that make the difference in daily practice.

Classic agency (project mode)

Every task starts with a quote
Capacity planned per project
Rotating teams depending on workload
Communication via project management
Strong at concept and relaunch

Ongoing delivery system

Tasks flow into a prioritised list
Fixed monthly capacity
Consistent team with context
Direct channel, short paths
Strong at continuous development

Comparison of classic agency work and an ongoing delivery system across nine criteria
Criterion	Classic agency	Ongoing delivery system
Starting a task	Request, briefing, quote, approval	Submit the task, go straight into delivery
Billing	Project price or individual invoice per task	Fixed monthly scope
Speed	Depends on quoting and planning cycles	Continuous, no new quote cycle
Prioritisation	According to the agency's project plan	According to company needs, aligned continuously
Communication	Per project, often new contacts	Continuous, dedicated contacts
Demand for change	Treated as a new initiative	Scheduled as an ongoing task
Scalability	Limited by project capacity	Flexible within the agreed scope
Responsibility	Ends with project sign-off	Remains as long as the collaboration runs
Suitable for	Bounded initiatives with a clear end	Regular, recurring delivery demand

What alternatives exist?

Beyond the classic project agency, several models cover ongoing demand to varying degrees:

Developer flat: A monthly model for ongoing technical delivery: changes, new features and fixes are handled continuously instead of commissioned one by one.
Website flatrate: Focused on websites: ongoing adjustments, new pages, landing pages and technical fixes are included in the scope, not a one-off project.
Software development as a subscription: For web apps and internal tools: development runs continuously instead of in separately renegotiated project phases.
External developer team: A fixed team handles ongoing tasks, knows the context and history, and doesn't need to be onboarded again for every request.
In-house developer: Full control and immediate availability, but fixed personnel cost and dependence on a single person.
Freelancer: Flexible and often fast, but availability, prioritisation and quality assurance aren't always plannable depending on workload.

How it works

1
Report the need

Describe the task briefly, no briefing document.
2
Triage

Priority, scope, questions – in minutes, not meetings.
3
Deliver

Straight from the list, no new quote.
4
Review

Four-eyes principle before go-live.
5
Approve

Short feedback, next task moves up.

Why speed alone isn't enough

Fast delivery isn't an end in itself. Without quality checks, speed can even be dangerous: errors go live, fixes create new errors, responsibilities blur.

Good ongoing delivery therefore needs not just speed but clear processes: proper prioritisation, defined approvals and functioning quality management. Speed without structure is just haste with a different name.

An ongoing delivery system doesn't replace structure with speed – it relocates it: away from repeated quote cycles, towards recurring coordination and review routines.

How companies recognise they've outgrown project logic

These signals suggest that a pure project model no longer matches actual demand:

01New digital tasks arise every week
02Quotes for small changes take too long
03Marketing regularly waits on technical delivery
04The website is constantly being adjusted instead of finished once
05Internal processes increasingly need to be digitised
06Freelancers are hard to plan around and change often
07The agency reacts slowly to small, urgent changes
08Too many open small tasks pile up without a clear path to delivery

When is it worth it?

Project or delivery system – which fits your demand?

A fit if

Several small to medium tasks arise every month
Marketing regularly waits for website changes
Quotes for small things cost more time than the work itself
You want one contact who knows the context
Changes should go live reviewed and promptly

Not a fit if

A clearly bounded relaunch with an end date is coming up
A branding or concept project needs a creative phase
Nothing will change for months after the project
An internal team handles ongoing delivery
The initiative is one-off and budgeted

How LootSquad understands ongoing delivery

LootSquad sees digital delivery as a continuous process. Companies shouldn't have to buy every small change separately; instead, clear contacts, prioritisation, technical delivery and quality checks should make them faster and more capable of acting.

Conclusion

Classic agencies aren't fundamentally too slow. They just often work according to a project logic that no longer fits ongoing digital tasks optimally. Companies with regular demand need a model that organises changes, technical tasks and development on an ongoing basis.

Frequently asked questions about agencies and ongoing delivery

Why do agency processes often take a long time?

Because they're built around projects: briefing, quote, approval, scheduling, delivery, sign-off. This structure creates commitment, but it repeats for every small change and adds up to noticeable waiting time.

When is an agency still the right choice?

For clearly bounded initiatives with a defined start, end and budget – such as relaunches, branding projects or complex concept phases. There, project logic remains the right way of working.

What's an alternative to a classic agency?

Models such as a developer flat, a website flatrate or software development as a subscription reflect ongoing demand better, because changes are scheduled continuously instead of commissioned individually.

Why is a developer flat faster?

Because tasks are submitted and prioritised directly, without needing a new quote, a new approval and new scheduling for every change.

What does ongoing digital delivery mean?

It describes an operating mode in which websites, web apps and digital channels are permanently adjusted, corrected and developed further – instead of being finished once and left unchanged afterwards.

Don't want to start a new agency process for every change?

With LootSquad, companies get ongoing digital delivery for websites, web apps and technical tasks. Predictable, structured, with clear contacts.

View developer flat