How we work · 02From sentence to production

From a 30-minute call to software in production.

No long discovery decks, no offshore relay. Here's exactly what happens from the moment you book a call, who you talk to, what you get, and when.

It starts here, Day 0

It starts with a 30-minute call.

You book a slot and tell us, in a sentence, what you want to build. On the call you talk to a senior engineer from the team that would actually build it, never a salesperson, never an account manager.

We spend the time on your problem, not our pitch. We ask sharp questions, pressure-test the idea, and look for the smallest version worth shipping. If we're not the right team for it, we'll tell you that too, and point you somewhere better.

There's nothing to prepare. A rough idea is enough; a spec is welcome but not required.

The 30 minutes
  • 00-05'The ideaYou walk us through it in plain language. We listen.
  • 05-20'Pressure-testWe dig into users, constraints, edge cases and what "done" means.
  • 20-28'The shapeWe sketch the smallest version worth building and a rough path.
  • 28-30'Next stepHonest read on fit, and what a proposal would look like.
You leave with a sharper problem and an honest answer, whether or not we end up working together.
What happens next · 03

The path from call to live software.

01

Scope & proposal

Within two business days you get a one-page proposal: the smallest version worth building, the stack we'd use, the milestones, the timeline and a fixed price. No fluff, no padding, a plan you could hand to anyone and understand.

One-page scopeFixed priceClear milestones
≤ 2 business days
02

Kickoff & shape

We start the week we agree to. In kickoff we cut the idea to its core, agree on the one metric that defines success, and map the data model and the handful of flows that actually matter. Everything downstream points back to this.

Success metricData modelCore flows mapped
Week 1
03

Design in code

We design the real interface in code, not as throwaway mockups. What you click through is the actual product taking shape, the same components that ship, so there's no translation loss between a pretty picture and what gets built.

Real interfaceWhat you see shipsNo throwaway mocks
Week 1-2
04

Build in weekly cycles

Every week you get working software on a staging link and a short demo. You see it come together and steer as it does, reprioritise, cut, add, with no six-week black boxes and no surprises at the end. The team that demos is the team that built it.

Weekly staging buildLive demoYou steer
Ongoing
05

Ship to production

We deploy to production, tested, instrumented and documented. Then we hand it over clean, with the code, the runbook and the keys, or we keep running and maintaining it for you. Your call, not a lock-in.

Tested & instrumentedClean handoverYou own the code
Launch
06

Iterate on real usage

Once it's live, we improve on evidence, what real users do, where they stall, the metric that mattered, instead of another month of planning. Most projects keep going here, in the same tight weekly rhythm.

Real-usage dataTight loopMeasured, not guessed
Post-launch
What you can expect · 04

The same four things, every project.

01

One senior team

The people you meet on the call build the thing. No handoff, no junior swap, no telephone game.

02

Working software weekly

Progress you can click, every week, not a status doc. You always know exactly where it stands.

03

Fixed scope & price

We agree what we're building and what it costs up front. No open-ended meters running.

04

You own the code

Production-grade, documented and yours. Keep it in-house or keep us on, never a lock-in.

Ready when you are

The whole thing starts with one call.

Book 30 minutes with the team that would build it. Worst case, you leave with a sharper idea and an honest answer.

Book a 30-minute call