Why I renamed sprints to agentic development.

Why I Renamed Sprints to Agentic Development

I renamed the sprint framing to agentic development so the offer matches how delivery actually works.

The previous wording suggested short, isolated engagements. In practice, most projects need a scoped setup phase followed by ongoing technical ownership. The new model reflects that reality.

What changed

1. Positioning Any engagement starts with a quote form and scoped technical plan, then continues as an active monthly retainer.

2. Lane structure Work is now framed by technical complexity:

• Lean Build (no DB/auth)
• Core Product Build (DB/auth)
• Commerce Build (payments/ecommerce)
• Multi-Stream Scale (parallel delivery streams)

3. Public pricing language Public setup ranges are shown in AUD, with medians by lane and monthly retainers. Every project has a 3-month minimum retainer.

4. Routes and tools Sprint tool routes were renamed:

• /tools/sprint-assessment -> /tools/scope-assessment
• /tools/sprint-calculator -> /tools/project-cost-calculator

Legacy routes are redirected so existing links keep working.

What did not change

• Historical experiment and story content remains intact for context.
• The technical guardrails stay the same: server-side validation, pricing integrity checks, and strict CI.

Why this is better long-term

This rename removes ambiguity in scope, pricing, and ownership. It sets clearer expectations for both sides:

• clients know what lane they fit into,
• pricing maps to complexity,
• and delivery continues past launch with an explicit support model.

If you are planning work, start with the quote form at /services/get-quote.