The On-Site Sprint Model
1–3 days on-site. Rapid prototype. Remote production.
Products go wrong when the people building them never meet the people using them. I fly in, sit with your team and the people the product is for, work out what it has to do, and leave a working demo behind before I board the flight home. The production build is finished in focused remote work.
Four stages, no discovery phase
The same shape every time, so the engagement is predictable before you commit to it.
Fly In
Day 1
I travel to your location. We sit in one room with the people who can actually decide — and, where possible, someone who will use the thing — whiteboard the domain logic, and audit the messy real inputs, not the sanitised version.
Less lost in translation between the business and the build.
Live Demo
Before I leave
Before I step onto the plane, I show a working proof-of-concept built in your stack. Clickable, running against your data shape, demoed to your stakeholders.
You see architectural proof in action before paying for the full build.
Fly Out
Weeks 1–3
I return to a deep-work environment and harden the POC — multi-tenancy, auth, error paths, the parts that decide whether it survives contact with real users.
Focused build time, with few meetings.
Ship
Handoff
Production deployment, documentation, and handover to your internal team — or an automated maintenance setup if there is no team to hand it to yet.
Something that runs after I am gone.
Pick the shape that fits the problem
You are not buying hours. You are buying a condensed result with a fixed end date.
The 1-Day Blueprint
Product & architecture blueprint, API scaffolding
- 8 hours on-site with leadership and tech leads — and, where possible, the product's users
- Unblock stalled technical decisions, whiteboard the database schema
- Live scaffolding and baseline API integrations stood up on day one
A decided architecture and a repo that already compiles.
Flat fee — quoted on scope
The 2-Day Prototype Sprint
0-to-1 greenfield builds & core feature engines
- Day 1 — architecture alignment, schema design, auth and DB setup
- Day 2 — live hacking session, then a functional POC demo for stakeholders
- A live, clickable system baseline before I step out the door
A working product spine your team can keep building on.
Flat fee — quoted on scope
The 3-Day Consolidation Sprint
Legacy collapse & complex multi-system integrations
- Day 1 — legacy code and data audit: which tools, which data, and what each one is the source of
- Day 2 — unified data model migration and core business logic
- Day 3 — integration testing, stakeholder demo, remote roadmap setup
A unified data model and a tested migration path toward one system.
Flat fee — quoted on scope
Ideal for
Situations where alignment is the bottleneck and a working artefact settles the argument.
- 0-to-1 product launches
- Tool consolidation — collapsing legacy sprawl into one system
- Complex API and partner data integrations
- Post-funding technical jumpstarts
- Stalled projects that need a decision, not another workshop
What makes the days on-site count
Three things I need before arrival. When they are met, the days on-site go into building, not waiting.
Decision-makers in the room
Direct access to the CEO, CTO, or lead product owner for the duration. Not a proxy who has to check.
Credentials provisioned 48h prior
Repo access, API keys, and staging environments ready before I land — so day one is building, not onboarding.
No filler meetings
Zero scheduled non-technical meetings inside the sprint window. The clock is short by design.
What you are actually buying
Lower risk
No full-time hire and no six-month agency contract just to find out whether the idea holds up.
Speed to alignment
Key people in one room with a product engineer for a few days settles questions that otherwise drag on through months of meetings.
An expert, not an employee
I arrive, solve the thing, and depart. The engagement has an end date from the first email.
Tell me what is stuck.
A short mail with the problem and the constraint is enough. If it fits one of the three sprints, you get a scope and a flat fee back — not a discovery invoice.