What a $5,000 Sprint Ships, Day by Day

Two engagements start the same Monday. One is a retainer. By the end of the quarter it has produced a discovery deck, a competitive audit, a brand workshop with sticky notes, a positioning document, and a roadmap with the first real build penciled in for next quarter. Thirteen weeks in, nothing a customer could touch is live. The other is a two-week sprint. Ten working days later it has shipped one thing, running in production, and the engagement is already over.

Buyers assume the fixed price is where the thin work hides. Five thousand dollars, flat, two weeks: surely that means a template, a rush job, a corner cut somewhere you will find in month three. The instinct is understandable and, on this offer, backwards. The vague retainer is the one that hides the absence of shipping, behind a quarter of research nobody asked to buy. Concreteness is what a padded engagement cannot survive. Publish the ten days and the thin work has nowhere left to hide.

So we published the ten days. Not a range, not a "typical engagement," but the actual shape of a sprint, day by day, ending in the single deliverable that goes live on day ten. If you have ever signed a scope and wondered what you were actually going to get, this is the answer written down before the invoice clears.

What does a two-week marketing sprint actually deliver?

A two-week marketing sprint delivers one shipped, working deliverable, live in your own accounts by day ten, for $5,000 flat. Not a strategy to build one later, not a deck describing one: the thing itself, in production. A single deliverable is the entire point of the format. One landing page wired to real conversion tracking, or one identity system, or one automation, built and handed over inside two weeks, because a sprint that tries to ship five things ships none of them.

The constraint is doing the work here, not the ambition. Ten working days is enough time to build one thing to a standard you would own for years, and not enough time to build two. That is a feature. The scope conversation that most engagements defer for a quarter happens on day one of a sprint, because the deadline will not let it slide. You decide what the one deliverable is, everything else goes on a list for later, and the clock starts.

The ten working days, deliverable by deliverable

Here is one representative sprint, framed as a composite with round steps so you can see the machine rather than a specific client's private timeline. The single deliverable is a conversion-instrumented landing page: one page, built in owned code, wired end to end to server-side conversion tracking and your CRM, live on your domain. The deliverable changes from sprint to sprint. The discipline does not.

1. Day one, scope lock and access. The one deliverable gets named in a single sentence and written down. Everything else you mention goes on a parked list, explicitly out of scope. You hand over access to the accounts the work touches: domain and DNS, analytics, the CRM. The ship date is set to day ten and does not move.
2. Day two, the single conversion. We define the one action the page exists to produce: the booked call, the submitted form, the started checkout. Everything on the page will earn its place by moving a stranger toward that one event, or it gets cut. The copy skeleton and the section order come out of that decision, not out of a template.
3. Day three, the copy draft. The headline, the offer, the objection order, and the single call to action, drafted in full. This is the day the argument the page has to make gets written down, before a pixel of design exists, because a page designed before it is written is just decoration.
4. Day four, the build begins. The page goes into owned code, not a drag-and-drop builder you would be renting by the month. Structure, layout, and the responsive behavior that keeps it holding its shape on a phone. What gets built here is yours to inspect and change, which is the whole reason it is not built inside someone else's platform.
5. Day five, build and load budget. The build continues against a hard performance budget. Images compressed, fonts subset, scripts kept off the critical path, because a page that takes four seconds to load has already lost a share of the traffic you paid to send it. Speed is a conversion feature, so it is engineered on the way in, not patched afterward.
6. Day six, wire the tracking. The conversion event gets instrumented server-side, so it fires from your infrastructure instead of depending on a browser pixel that a privacy setting can quietly block. The event hands off to your CRM. The thank-you path and the confirmation are built. This is the plumbing that separates a page you can measure from a page you can only admire.
7. Day seven, prove it end to end. We fire a real test lead through the whole path and confirm it lands where it should: the form submits, the server-side event records, the contact appears in your CRM tagged correctly, the analytics agree with reality. A conversion you cannot see in your own accounts is a conversion you do not really have.
8. Day eight, one revision pass. You review the working page, not a mockup, and we take one structured round of changes: copy corrections, a design fix, a reordered section. One pass, because a sprint has a revision window, not a revision loop, and the deadline is what keeps the loop from ever opening.
9. Day nine, hardening. Final speed check, metadata and the social preview card, the analytics double-checked, the form failing gracefully if a network call drops, staging promoted toward production. The unglamorous day that decides whether day ten is a launch or a scramble.
10. Day ten, ship and hand over. The page goes live on your domain, running in your accounts, with a one-page runbook that says how it works, how to change the copy, and how to read the conversions. The engagement ends with the thing running and the keys in your hand, not with a proposal for phase two.

None of those ten days is guesswork. The server-side tracking wired on day six is the same class of plumbing we rebuilt for Skin and Self, where the entire fight was getting conversion data to reconcile against real bookings instead of inflated platform numbers. A sprint is short because the work is scoped, not because the work is shallow.

A deadline is not pressure applied to good work. It is the only thing that reliably forces an agency to decide what actually matters and ship it before the month absorbs the decision.

Why does a fixed sprint out-ship a quarter of retainer discovery?

Because a hard deadline forces scope, and an open-ended retainer rewards discovery over shipping. When there is no ship date, the safest and most billable move in any given week is more research, another audit, one more alignment call. Nothing is ever wrong, and nothing is ever done. A two-week sprint removes the option to defer, so the work a retainer can postpone for a quarter has to happen in the first two days.

This is not a knock on retainers as a category. Ongoing operations genuinely need one, and we run them; the mechanism only turns against you when the engagement has no shippable edge and the incentive quietly inverts toward activity over output. We wrote about the sharper version of that in the retainer trap: the model's built-in reason to keep you busy rather than finished. A sprint is the structural opposite. Its revenue is fixed the moment you book it, so the only way through is to ship.

Run the round numbers. A quarter at an infrastructure retainer is thirteen weeks and, at $5,000 a month, fifteen thousand dollars. If that quarter produces a strategy and a roadmap and nothing live, you have paid fifteen thousand dollars for a plan. Three sprints over the same quarter, at $5,000 each, cost the same fifteen thousand and put three finished things into production. Same spend. The only variable that changed is the deadline, and the deadline is the difference between shipped and pending. If you are weighing which shape to buy, retainer, project, or sprint walks the decision, and the full set of pricing models sits next to it.

Should your first engagement with an agency be a sprint?

If you have been burned before, yes: a sprint is the smallest reversible commitment an agency can offer. Five thousand dollars, two weeks, one deliverable you own outright, and no contract to unwind when it ends. You find out how a shop actually works by watching it ship one real thing, not by signing a year and discovering the answer in month four.

A sprint is a reversible entry point in the literal sense. When it ends, you hold the deliverable, it runs in your accounts, and you owe nothing further. If the work was good, the next engagement is an easy yes and you already know what their shipping looks like. If it was not, you keep the thing anyway and walk, out five thousand dollars and two weeks instead of a year and a five-figure exit. That is why the runbook on day ten matters as much as the page: the handover document, not the system, is the real deliverable, and it is what lets you leave with the work still working.

A sprint is not the right container for everything. A full website is a project that opens at eight thousand dollars, not a two-week sprint, and pretending otherwise is how corners get cut; what a website should actually cost draws that line honestly. But when the job is one clear, shippable thing, the sprint is the format that proves the work before you commit to more of it.

Our prices sit in the open on the pricing page: $5,000 flat for a two-week sprint, one shipped deliverable, no range that triples once you are on the call. If you have one clear thing that needs to be live, and you are tired of paying for quarters that produce plans, that is exactly what the format is built for. Book a call and tell us the one deliverable. We will tell you honestly whether it fits in two weeks, and if it does not, what it actually is.