Start a project

// how we start

The first 30 days, week by week.

What happens, who's in the room, and what you own at each step — before you commit to anything past a discovery sprint.

// the timeline

Discovery, architecture, working software

Week 1

Discovery and access

A senior engineer and, where the engagement needs it, a domain specialist join calls with the people on your side who actually know the system: an engineering lead, a product owner, and whoever owns the constraint that matters most — compliance, payments, data. You get read access to what exists today: repositories, architecture docs, and whatever passes for documentation. We sign the NDA before any of this starts.

You own: the access grants, the NDA, and every note taken about your system so far — nothing leaves this call in anyone's memory alone.

Week 2

Architecture and a plan

We turn discovery into a written architecture: the modules, the data flow, the parts that are risky and why. That architecture becomes a phased plan with a real estimate attached — not a range that hides the unknowns, but the specific risks that could move the number, named. You review it with us before it's final.

You own: the architecture document, the phased plan and the estimate — yours to keep, take to another vendor, or build in-house, whether or not you continue with us.

Weeks 3–4

First working software

Implementation starts against the highest-risk part of the plan, not the easiest. You see a demo of working software at the end of week 3 and again at the end of week 4 — the same cadence every two weeks continues for the length of the engagement. Code lands in your repository from the first commit.

You own: the running code, in your repository, reviewable commit by commit — and the demo cadence that continues for as long as the engagement does.

// the sprint

What the $9,500 discovery sprint delivers

Weeks 1 and 2 above are the discovery sprint: a fixed two-week engagement, fixed price, for $9,500. At the end of it you have a written architecture, a phased implementation plan, the specific risks we found, and an estimate for what building it costs — deliverables you keep even if you don't continue with us. Weeks 3 and 4 are the start of implementation, priced as its own engagement once the plan from the sprint makes that price real rather than a guess.

30 minutes with a senior engineer.

Tell us what you're building. You'll leave with an honest opinion, even if it's "you don't need us."

Start a projectHire engineers

Reference calls with past clients are available under NDA during evaluation.