Website Sprint.
Built from what makes you money.
A website built from what actually makes you money, not from a template and a wishlist. Four weeks. Fixed fee. Starts with a paid diagnostic you keep either way.
- Written business diagnostic + one success metric
- Sitemap, narrative, and copy direction in Figma
- Production Next.js site on Vercel with real content
- Analytics, tokens, and a written handover
- ·An SME whose site should move enquiries, bookings, or sales
- ·Founders who will sit in a diagnostic before any wireframe
- ·Teams that want the repo, Figma, and tokens in their name from day one
- ·Buyers who will stop if the diagnostic says the site is not the constraint
- ·You need five pages by Friday
- ·A template skin with stock copy and a contact form
- ·SEO ranking promises or traffic guarantees
- ·Anyone who wants estimates by the hour
How the Website Sprint runs.
Same rhythm as every ROQ CX sprint: paid checkpoints, named artefacts, a clean stop between phases if the evidence says stop.
Pressure-test the business model.
- Working session: what a customer is worth, where enquiries come from, what happens in the ten minutes after a form submit
- What the site is actually supposed to move
- Written diagnostic + a single success metric, signed
- Phase 01 is paid work with a deliverable whether or not the build follows
Argument before pixels.
- Sitemap and page-by-page argument derived from the diagnostic
- Copy direction, not final polish
- Two divergent directions, kept low-fi on purpose so feedback stays honest
- Artefacts: Figma + copy doc
Ship the production site.
- Next.js, TypeScript, Tailwind, shadcn/ui on Vercel
- Supabase where there is data
- Real content, not lorem
- Artefacts: GitHub repo + staging URL
Instrument and leave you the keys.
- Analytics and event tracking against the success metric
- Error tracking, CI/CD, design tokens
- Written handover
- Artefacts: HANDOVER.MD · tokens · dashboard
- Access to whoever owns the commercial model
- Existing analytics, CRM, or enquiry logs if you have them
- Brand assets and domain access
- A decision-maker available between phases
- DIAGNOSTIC.PDF + signed success metric
- Figma + copy doc
- GitHub repo + staging URL
- HANDOVER.MD · tokens · analytics dashboard
- Proceed into structure + build after the diagnostic
- Stop after the diagnostic if the site is not the constraint
- Narrow scope and rebuild the success metric
- Hand the artefacts to an in-house team
Roughly 30% of our sprints end in a deliberate kill.
If the diagnostic says the site is not the constraint, we say so and the engagement can stop there. Phase 01 is paid work with a deliverable either way. That kill rate is the system working, not a failure mode.
Fixed fee. Published floor.
Starts at AED 18,000 ($5,000 USD). Fixed fee. No retainers, no T&M, no scope-creep invoices. You own the repo, Figma, tokens, and content from minute one.
- Multi-locale or multi-brand sites
- Complex CMS or authenticated customer portals
- Integrations beyond the default stack (custom CRM, ERP, booking engines)
- Content production volume beyond agreed page set
Quick answers.
Not as a separate SKU today. It is phase 01 of the Website Sprint. If we stop after it, you still keep the written diagnostic and the signed success metric.
Then the engagement ends after phase 01. You keep the diagnostic. About 30% of ROQ CX sprints end in a deliberate kill. We would rather stop than ship a site that cannot move the metric.
You. Repo, Figma, tokens, and content sit under your accounts from minute one. No lock-in.
No. We instrument one success metric and hand you the dashboard. Rankings, traffic volume, and conversion percentages are outside the fixed fee.
Next.js, TypeScript, Tailwind, shadcn/ui on Vercel. Supabase where there is data. Same default as our product sprints.
Yes. Fixed fee per engagement, cancellable between milestones. Everything built so far stays yours.
We'll pressure-test the idea, agree on the success metric, and decide if a sprint is the right shape.