Fundamentals

What is a developer flat?

Why small changes pile up, why agency processes are too heavy for them – and how an ongoing delivery model closes that gap.

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

Request → prioritise → build → review → release: the basic principle of a developer flat

TL;DR

In short: What is a developer flat?

A developer flat is a monthly model in which a company draws on development work, website changes, technical implementation and ongoing digital improvement through an external team. Instead of commissioning every initiative separately, you get predictable monthly costs, a fixed point of contact and a continuous delivery process. Tasks are prioritised together and worked through one after another. The distinction matters: a genuine developer flat is neither a prepaid card nor a plain maintenance package, but a structured model for recurring digital work.

Most websites don't fail at launch. They fail afterwards.

Then come new offers, campaigns, bugs, customer feedback, tracking requests, forms, landing pages. And at some point you realise: the website is no longer a project. It is an ongoing workspace – just like the web app, the customer portal or the integration with your ERP.

The problem: each of these tasks is too small for a project on its own. Together they are too big to handle on the side. So they pile up. The price change waits three weeks for a quote. The trade-fair landing page arrives after the trade fair. The broken form stays broken because nobody feels responsible.

The usual routes only help so much. An agency needs a brief, a quote, an approval and a slot in the calendar for every change. A freelancer is often technically strong, but may be fully booked or ill tomorrow. An in-house developer costs money every month, is hard to hire – and rarely covers development, design and quality assurance at the same time.

This is exactly the gap a developer flat fills: ongoing delivery capacity for a fixed monthly price, with a clear process instead of one-off commissioning. What that means in practice, where the limits are and how to spot a good offer is what this article covers.

Definition: the developer flat explained simply

A developer flat is a subscription model for development work. The company pays a fixed monthly amount and in return gets permanent access to an external delivery team. Requirements are submitted continuously, prioritised together and implemented one after another – without a separate quoting process for every task.

01Monthly subscription instead of individual commissions
02Continuous development instead of a one-off project with a final sign-off
03Tasks are prioritised and delivered in sequence
04External technical capacity without building your own staff structure
05Costs are known in advance and therefore easy to budget
06Delivery starts faster because not every task is re-estimated

How it works

1
Submit a request

Describe the task briefly – no quote request, no formalities.
2
Prioritise together

What creates impact first moves to the front. The order is visible.
3
Build

The team works through the queue in order.
4
Review quality

A second person checks before release.
5
Go live

Approve, release, next task. No new round of quotes.

What is typically included in a developer flat?

The scope differs from provider to provider. In practice, the following tasks usually fall within a developer flat:

Changes to existing website pages
New landing pages for campaigns and sales
Technical bug fixing
Web development on existing systems
Automation of recurring workflows
Smaller features in web apps
Preparation of integrations with third-party systems
Conversion optimisation
Technical advice before decisions
Quality review before release

This list does not mean that every developer flat delivers everything, without limit and all at once. Providers who promise that are simply postponing the problem. What is realistic is a model with a queue, joint prioritisation, defined response times and clear rules about what gets planned as a separate project.

Real-world example

One mid-sized company, three departments, one queue

01Situation

A trading company with 40 employees runs a website, a small shop and a customer portal. Marketing wants landing pages, sales wants new forms, management wants a dashboard. So far: three quotes, three waiting periods, three vendors.
02Approach

All requests go into one shared list. Priorities are set once a week. The trade-fair landing page moves up, the dashboard is planned as a separate initiative, the forms go through the standard process.
03Result

No more quote per task, one contact for all three departments, fixed monthly costs. Big topics stay plannable, small topics no longer pile up.

What a developer flat is not

The term is used inconsistently in the market. These distinctions help when evaluating an offer:

Not a prepaid balance: With prepaid, a company buys a block of hours that gets used up. After that, work stops or a reorder follows. A developer flat, by contrast, provides ongoing capacity.
Not a maintenance contract: Maintenance keeps operations stable: updates, security, backups. A developer flat may include or connect to operations, but its core is further development.
Not a one-off fixed-price project: A fixed-price project has a defined scope, an end date and a sign-off. A developer flat is designed to run continuously and has no fixed project end.
Not an agency billing by the hour: In the hourly model every task is estimated, approved and invoiced. That costs time before the actual work starts. In the subscription model this quoting cycle disappears for standard tasks.
Not a pure design flat: Design flats deliver graphics, layouts and visual assets. Without development, the technical side stays open.
Not a hosting or support package: Hosting and support ensure availability. They do not replace delivery capacity for new requirements.

The core point: a genuine developer flat does not simply sell hours, but ongoing delivery capacity with a process, prioritisation and responsibility for the result.

Who benefits from a developer flat?

Small and medium-sized businesses

Regular digital demand, but no in-house development department.

Startups

Fast product iteration without building a permanent team too early.

Agencies

Technical delivery as an extended workbench when internal capacity is lacking.

Companies with ongoing website changes

Campaigns, price updates, new pages, seasonal content.

Teams with portal or web app ideas

Step-by-step build-up instead of one large one-off project.

Companies without recruiting capacity

Developer roles are expensive, hard to fill and hard to assess.

Marketing and sales teams

Ideas should be testable in days, not quarters.

When is it worth it?

Is a developer flat right for you?

A fit if

New website or web-app tasks come up every week
Tasks pile up because quotes take too long
You need development, design and QA – not just one person
You want predictable monthly costs instead of fluctuating invoices
A permanent developer position isn't worth it (yet)

Not a fit if

You need a single, clearly scoped project with an end date
No technical demand arises for months
Nobody in-house can decide priorities
You expect ten deliveries running in parallel
A large project (migration, platform) is the main focus

Benefits of a developer flat

Before

One-off commissioning

Every change: brief, quote, approval, slot
Weeks of lead time for small tasks
Changing contacts, context gets lost
Fluctuating invoices and change orders
Small topics pile up

After

Developer flat

Submit, prioritise, build
Starts straight from the queue
One contact who knows the system
One fixed amount per month
Website keeps moving

Predictable monthly costs: One fixed amount per month instead of fluctuating invoices and change orders.
Faster delivery: Tasks start straight from the queue without a separate estimate each time.
Fewer quoting loops: The administrative effort per task drops significantly.
Fixed point of contact: Context is preserved and briefings get shorter.
Continuous development: The website or application keeps moving instead of freezing.
Less dependence on individuals: A team absorbs holidays, sickness and absences.
Better prioritisation: What creates impact first gets built first.
More speed for marketing and sales: Campaign pages and tests no longer depend on free capacity.

Limits and risks

The model has clear limits. Knowing them leads to a better decision:

Not everything at once

A flat increases frequency, not parallel capacity. Anyone expecting ten tasks at the same time will be disappointed.

Prioritisation is mandatory

Without a clear order you end up with a long list and no visible progress.

Large projects need planning

Migrations, complex platforms or integrations should be planned, not pushed into the running queue.

Hidden prepaid

Some providers call their model a flat but bill hours internally. You can tell by quotas, caps and renegotiations.

Speed without quality assurance

Fast delivery without a review process creates follow-up errors and rework.

Unclear communication

Without documented requirements and status, misunderstandings arise on both sides.

Developer flat vs. agency, freelancer, in-house hire and prepaid

No model is inherently better. What matters is how regular and how predictable your delivery demand is.

Comparison of developer flat, classic agency, freelancer, in-house developer and prepaid model
Model	Advantages	Disadvantages	Best suited for
Developer flat	Predictable costs, continuous delivery, little quoting effort, a team instead of one person	Limited parallel capacity, prioritisation required, quality depends heavily on the provider	Regular, fluctuating delivery demand without an in-house developer team
Classic agency	Broad expertise, large projects feasible, formal acceptance processes	Quoting and coordination loops, longer lead times, higher cost per change	Clearly scoped projects with defined scope and budget approval
Freelancer	Direct contact, often lower hourly rate, high specialisation	Availability fluctuates, risk of absence, rarely a second pair of eyes for quality	Clearly defined individual tasks and specialist topics
In-house developer	Full availability, deep product knowledge, short paths	High fixed costs, recruiting effort, knowledge monopoly, limited breadth	Permanent full utilisation and long-term product development
Prepaid model	Transparent billing, no ongoing contract, good cost control	Quota runs out, reorders slow things down, no continuous planning	Sporadic, well-plannable demand without ongoing development

What does a developer flat cost?

Costs depend on the scope of services, the committed response times, the complexity of the tasks and the composition of the team. A model covering only website maintenance is priced well below a model that covers development, design, quality review and technical advice.

A developer flat can be cheaper than a permanent hire when a company needs technical delivery regularly but does not yet want to build its own full-time team. If one person would be fully utilised permanently, this calculation often reverses.

Cost logic

1×

Monthly price

One amount instead of individual invoices, change orders and quote loops.

Quotes per task

Standard tasks start without a costing round.

Point of contact

Context is retained – briefs get shorter with every task.

The monthly price alone is not enough for a sound assessment. It makes sense to compare along these points:

01Speed: How quickly does a typical task start and finish?
02Quality: Is there a review before release?
03Communication: How transparent are status and effort?
04Process: How are tasks submitted and prioritised?
05Resilience: What happens during holidays or sickness?
06Technical understanding: Is your own system really understood?
07Responsibility: Who is liable for errors and rework?

How do you recognise a good developer flat?

01Clear task prioritisation with a visible order
02Transparent communication about status and effort
03A fixed point of contact instead of changing contacts
04Proven technical competence in the relevant stack
05Proper quality review before every release
06A traceable process from request to go-live
07Realistically stated service limits
08Binding response times
09No hidden prepaid rules in the small print
10Genuine ongoing delivery instead of mere account management

How LootSquad understands the model

LootSquad does not see a developer flat as a plain hourly model, but as ongoing digital delivery for companies. The focus is on clear processes, fixed points of contact, technical implementation, quality review and predictable monthly collaboration. Tasks are documented, prioritised and reviewed before release; larger initiatives are deliberately planned instead of being squeezed into the running queue.

Conclusion

A developer flat is particularly worthwhile for companies that have regular digital tasks but do not want to coordinate new quotes, new alignment rounds or individual freelancers every time. What matters is that the model does not just sound affordable, but works cleanly in day-to-day operations: with traceable prioritisation, reliable communication, reviewed quality and honestly stated limits.

Frequently asked questions about the developer flat

What does developer flat mean?

A developer flat is a monthly model through which a company draws on development work continuously instead of commissioning every initiative separately. Costs are fixed per month; tasks are prioritised and implemented one after another.

Is a developer flat really unlimited?

No. What is usually unlimited is the number of requests, not simultaneous delivery. Reputable providers work with a queue and clear prioritisation: tasks are handled in sequence and larger initiatives are planned.

Which companies benefit from a developer flat?

Mainly companies with regular but fluctuating delivery demand: ongoing website changes, landing pages, smaller web app features, technical adjustments. For a single, clearly scoped large project, a fixed-price project is often the better fit.

What is the difference between a developer flat and a maintenance contract?

A maintenance contract secures operations: updates, backups, security, bug fixing. A developer flat additionally covers further development, i.e. new pages, new features and ongoing adjustments.

Is a developer flat cheaper than an in-house developer?

That depends on demand. If you can keep one person fully utilised permanently, in-house is often cheaper. If demand fluctuates or you need several skills (development, design, quality review), a subscription model is often cheaper and more flexible because there are no fixed costs for recruiting, onboarding and downtime.

Read on

Want to make digital delivery more predictable?

With LootSquad you get an external delivery team for websites, web apps and ongoing digital projects. With clear processes, fixed points of contact and predictable monthly costs.

View the developer flat