Question 1

What is a Follow-on Sprint?

Accepted Answer

A standard five-day sprint run after your first one — the next build on something already live. A new feature, a V2, the next chunk. Same model and price as a V1 Sprint, pointed at a product that already exists.

Question 2

What is low-fat support?

Accepted Answer

Keep-the-lights-on support for a live site or web app — patches, uptime and small fixes. The cheapest way to keep something running once it's shipped, for clients who don't need active development.

Question 3

What is a Strategy Sprint?

Accepted Answer

A five-day sprint focused on product strategy — making sure you're building the right thing. It helps a team define direction, proposition and roadmap, which matters even more in an AI world.

Question 4

How much does a Follow-on Sprint cost?

Accepted Answer

£10,000 + VAT per sprint — the same flat price as every five-day sprint.

Question 5

How much does a Strategy Sprint cost?

Accepted Answer

£10,000 over five days with the same senior team. (Scope and deliverables are being finalised — confirm current details on a call.)

Question 6

How much does low-fat support cost?

Accepted Answer

From £500/month. (Exact scope and response times are being finalised — confirm current details on a call.)

Question 7

How is a Follow-on Sprint different from a V1 Sprint?

Accepted Answer

A V1 Sprint builds a new product from zero. A Follow-on Sprint adds to a product that's already live, with the same senior team who already know it.

Question 8

When would I need a Strategy Sprint instead of a UX Sprint?

Accepted Answer

When the bigger question is "what should we build, and why" rather than "design what we've decided to build." It shapes proposition, customer journey, priorities and roadmap before design begins.

Question 9

How is low-fat support different from the Subscription?

Accepted Answer

Low-fat support is reactive maintenance — keeping a live product ticking over. The Subscription is active design and development capacity for building and improving.

Question 10

What does a Strategy Sprint produce?

Accepted Answer

Direction and clarity: proposition and positioning, customer journey and opportunities, and a prioritised view of what to build and what not to. It can flow straight into a UX or V1 Sprint.

Question 11

When should I use a Follow-on Sprint instead of the Subscription?

Accepted Answer

Use a Follow-on Sprint for one big, defined piece of work (a major feature or a V2) that's too large to flow through the Subscription one task at a time. Use the Subscription for a continuous stream of smaller work.

Question 12

What does low-fat support cover?

Accepted Answer

Patches, uptime monitoring and small fixes to keep a live product healthy. It's deliberately minimal.

Question 13

When should I choose low-fat support?

Accepted Answer

When your product is shipped and stable and you just need someone to keep it running, rather than to actively build new things.

Question 14

Do I get the same team for a Follow-on Sprint?

Accepted Answer

Yes — the same senior people who designed and built the original product, so there's no re-briefing.

Question 15

Who is the Strategy Sprint for?

Accepted Answer

Teams who need to align on direction before committing design and build resource — for example shaping early ideas into an initial prototype and experience direction.

Question 16

What do I get from a Follow-on Sprint?

Accepted Answer

The same as any five-day sprint: pre-flight scoping the Friday before, daily show-and-tells, and the agreed feature designed and/or built and handed over by Friday.

Question 17

Can a Strategy Sprint lead into design and build?

Accepted Answer

Yes — it's the strategic front door. Once direction is clear, a UX Sprint designs it and a V1 Sprint builds it.

Strategy Sprints, Follow-on Sprints & support