Approved specification
Goals, non-goals and testable acceptance criteria — in writing, in a version 1.0 approved by you.
Most projects don't fail because of code, but because of unclear requirements and wishes that change along the way. In the Spec Sprint we define together exactly what gets built — in writing, testable and approved by you. Afterwards everyone knows what they get and what it costs.
A finished result with value of its own — as a page in your Confluence or as a PDF. The specification is yours and can be implemented by anyone.
Goals, non-goals and testable acceptance criteria — in writing, in a version 1.0 approved by you.
Every work package with its effort in hours. You see what the project costs before implementation starts, and where scope can be saved.
The specification broken down into issues with acceptance criteria — the basis for implementation, by me or by anyone else.
Five steps from the first conversation to acceptance — the specification is done after step three and belongs to you.
You describe the project, goals and constraints; I ask the questions that would get expensive later.
I write the first draft with goals, non-goals, acceptance criteria and a list of open questions.
Open questions are resolved together, then you approve version 1.0 — with effort estimate and issue list.
Based on the specification: a package or billed by effort, by me or by anyone else.
Acceptance is checked against the criteria in the specification — not against memories of conversations.
Three sizes, one hourly rate. Which one fits, we'll settle in the intro call.
One clearly outlined requirement, for example a new section, a set of checkout rules or a small automation.
Several related features or a connection to ERP, PIM or a payment provider.
A project with many stakeholders and dependencies — relaunch, platform migration or an app of your own.
Payment before the start. If you book the implementation with me, 50 % of the Spec Sprint is credited against it. All prices net.
New wishes are welcome. They are assessed as a change request with effort and date and, once you approve, added to a new version of the specification. That keeps it clear what has been commissioned.
My process is open: phases, approval points and templates are published on GitHub.
You still have a finished result: the specification is yours, and any agency or developer can implement it.
Only for an existing shop with an unclear starting point. Otherwise we start directly with the Spec Sprint.
The Spec Sprint is a finished result with value of its own — you get a specification you can use independently of me.
25 minutes, free of charge. Afterwards you'll know whether I'm the right fit — and what the next sensible step would be.