Create+
Build+
Grow+
Systems+
Guides+
Updates+
Case Studies+
AboutContact
Start a project
Home/Guides/Engagement Models
✦ Guide / Build  —  The playbook, in plain words

How do you work with an agency?

One-off project, monthly retainer, a team that's effectively yours — the engagement model decides what the relationship looks like after the handshake. Here's each model in plain words, and the hybrid most modern agencies actually run.

Topic: Working with an agencyReading time: 7 minLevel: Beginner-friendly
§ 01 — The definition

What an engagement model actually is.

Engagement model, defined

An engagement model defines how a client and an agency work together over time — a one-off project with a start and an end, an ongoing monthly retainer, a dedicated team that works only for you, on-demand blocks of hours, or a hybrid that changes shape as the product matures.

It's the third of three choices that shape any agency relationship. The development methodology decides how the team works day to day; the pricing model decides how cost is calculated; the engagement model decides the shape of the relationship — does it end, does it repeat monthly, or does the team effectively become yours? Getting this one right matters most, because it decides what happens after launch.

What it decides
The shape of the relationship — one-off, ongoing, or embedded.
What it isn't
The price. That's the pricing model — chosen alongside, not instead.
The key question
“What happens after launch?” — the model you pick is the answer.
The modern default
A hybrid: fixed sprints early, project build, ongoing care after.
§ 02 — The models

The four models, in plain words.

01
Project-BasedDefined start, defined end
The classic: a defined scope, a delivery, a handover, and the engagement closes. Clean and containable — and the reason so much software quietly decays, because nobody owns what happens after launch. Best for genuinely finite work: a site build, a migration, an audit.
Shape — scope → build → handover → done.
02
RetainerFixed monthly, ongoing
A fixed monthly fee covering an agreed mix — maintenance, small improvements, support, meetings. Predictable for both sides, and the standard for work that never really finishes: marketing, CRO, content, and software care. The risk to watch: retainers drift into “hours used” instead of outcomes — a good one is tied to a plan.
Example — $3,000/month: maintenance + improvements + support + meetings.
03
Dedicated TeamYou effectively rent a team
The client rents a team that works only on their product — near-employee focus without hiring, onboarding or managing headcount. Best for long-term product development where there's always a roadmap. It's also the model AI is quietly reshaping: an AI-powered team covers the same roles with far fewer people.
Example — 2 developers + 1 designer + 1 QA, $18,000/month, exclusively yours.
04
On-DemandBuy hours as needed
No standing commitment — you buy blocks of hours when something needs doing, and top up when they run out. Maximum control, minimum momentum: fine for occasional fixes, wrong for anything that needs to compound week over week.
Example — a block of 25 support hours, used as needed.
§ 03 — Side by side

Commitment vs. momentum, compared.

Engagement models compared: best fit, commitment, and what happens after launch
ModelBest forCommitmentAfter launch
Project-basedFinite builds, migrations, auditsOne-offNobody's job — the quiet decay risk
RetainerCare, marketing, continuous workMonthlyOwned, at an agreed pace
Dedicated teamLong-term products with a roadmapHigh, monthlyFully owned — the team lives in it
On-demandOccasional fixesNoneReactive only
Hybrid lifecycleNew products, end to endGrows with certaintyBuilt in from day one
§ 04 — In practice

The hybrid most agencies actually run.

Real products don't fit one model, because requirements become clearer as the product evolves. So the modern default is a hybrid that changes shape by phase — fixed and small while the idea is unproven, flexible during the build, ongoing once it's live:

Discovery sprint
Fixed price · one-off
Prototype sprint
Fixed price · defined outcome
Build phase
Project · T&M or milestones
Growth phase
Subscription / retainer · ongoing

The growth phase is the part most engagements get wrong — treated as an optional upsell instead of the point. Software is never truly finished; it's improved through small, high-impact iterations— maintenance, optimisation, new features, AI improvements, analytics, CRO and experimentation — rather than infrequent, expensive rebuilds. That's the thinking behind micro-builds, and it's why the ongoing phase deserves as much design as the build itself.

See it applied

This hybrid is exactly how we engage.

Discovery Sprint → Prototype Sprint → The Build → Care & Growth. Fixed while it's unproven, ongoing once it's live — every sprint's output yours to keep.

See Bigello's packages
§ 05 — Common questions

Engagements, answered.

What's the difference between a retainer and a project?

A project has a defined scope, start and end — deliver, hand over, close. A retainer is ongoing: a fixed monthly fee covers an agreed mix of maintenance, improvements and support, month after month.

Projects suit finite builds; retainers suit work that never really finishes.

What is a dedicated team?

You effectively rent a team — say two developers, a designer and a QA engineer — who work only on your product for a monthly cost. Near-employee focus without hiring. Best for long-term products with a continuous roadmap.

Is an engagement model the same as a pricing model?

No. The engagement model is the shape of the relationship over time; the pricing model is how cost is calculated within it. A retainer engagement usually uses fixed monthly pricing; a project engagement might be fixed-price, milestone-based or time & materials.

Which model should a new product use?

Usually the hybrid: fixed-scope discovery and prototype sprints, a project engagement for the build, then a retainer or subscription for growth. It matches how certainty grows as the product evolves — and makes sure someone owns the product after launch.