Web development retainer or subscription? Choose the right model.

Short answer: a traditional web development retainer usually reserves a fixed number of hours or a named person. A subscription such as TUNDRÄ accepts unlimited requests into a queue but works on one or two at a time. The better choice depends on whether you need guaranteed capacity or flexible outcomes.

What “web development retainer” can mean

The term is used for several different commercial models. Two proposals can both say “monthly retainer” while creating very different expectations about capacity, response time and unused budget.

How the TUNDRÄ subscription differs from a retainer

TUNDRÄ is a managed service, not staff augmentation and not an hourly capacity reservation. You can keep a reasonable number of eligible requests in the portal. Maintain moves one active task at a time; Grow moves up to two. The team triages, implements, checks and documents each item before the next ready task moves forward.

The current public prices are $1,450 per month for Maintain and $2,450 per month for Grow. Both are month-to-month plans. The four-hour and two-hour SLAs are initial-response commitments, not promises that every task will be completed in that time.

Subscription vs retainer: the decision criteria

1. How predictable is the work?

If next month is already planned in detail, a reserved-hours retainer can be easy to budget and schedule. If priorities change every week, a task queue avoids rewriting a statement of work each time a form breaks or a campaign page becomes urgent.

2. Do you need capacity or outcomes?

A capacity agreement is useful when your team directs the work and needs a known number of engineering hours. A managed queue is better when you want to describe the outcome, review key decisions and leave implementation, QA and release ownership with the provider.

3. What happens to unused time?

Ask whether hours expire, roll over or convert into a credit. A queue subscription has no hour bank: the commercial limit is concurrent work, not a time allowance. That is simpler for a full backlog but poor value when there is no meaningful work to send.

4. How will urgent work enter the plan?

Define what “urgent” means before an incident. TUNDRÄ can move confirmed checkout, payment, lead-form, security and launch failures ahead of ordinary queue work, but the response SLA still does not guarantee a resolution time. A business that requires guaranteed restoration targets needs a separately scoped incident-response agreement.

5. Where does project knowledge live?

Continuity is often the hidden value of any monthly model. TUNDRÄ keeps the brief, decisions, files, approvals, changelog and follow-up notes in the client portal. A good retainer should define an equivalent source of truth so knowledge does not disappear into calls or one contractor's inbox.

A practical monthly cost comparison

Do not compare only the headline fee. Add the work your own team must still perform: writing technical briefs, recruiting, assigning tickets, checking changes, coordinating release and rebuilding context after a handoff.

Questions to ask any retainer provider

1. Are we buying hours, access, outcomes or a task queue?
2. How many tasks or workstreams can be active at once?
3. Does “response time” mean acknowledgement, diagnosis or completion?
4. What happens when a request is too large for the standard scope?
5. Who handles QA, production release and rollback?
6. Where will code, credentials, decisions and change history live?
7. Which third-party costs remain ours?
8. How do cancellation, handoff and unfinished work operate?

Frequently asked questions