○Working with us
Three engagements at a time. Each one ships.
A short page that answers the questions a serious buyer asks before they reply to an email. How we work. What we sign. What you own at the end. What it costs.
○ The model
Three phases. One contract per phase.
Every engagement runs the same shape. We do not start a build without first running discovery. We do not leave a build without running handoff. Each phase ends in a deliverable you can hold.
- 01
Discovery
Two to three weeks
You give
Access to the operation. The shift floor, the dispatch desk, the back office. Stakeholders for one hour each. Real numbers, not sanitised ones.
You receive
A system map of the operation as it actually runs today. A ranked list of where software pays for itself. A go / no-go recommendation, and what we would build if we proceeded.
What's signed
A fixed-fee discovery contract. Mutual NDA on day one.
- 02
Build
Eight to fourteen weeks
You give
A single internal owner with decision rights. A standing weekly demo slot. Decisions inside forty-eight hours.
You receive
Working software shipped every week, deployable from day thirty. A live operations dashboard. A short Loom every Friday with what changed and what's next.
What's signed
A fixed-fee or milestone build contract. Statement of work attached. Code committed to your repo from the first line.
- 03
Handoff
Three months, included
You give
An internal owner to receive the keys. A short handover window.
You receive
All credentials. All infrastructure access. All runbooks. Three months of named support — bug fixes, small additions, a Friday Q&A. After that, you own it; we leave clean.
What's signed
A transfer agreement. The IP is yours. The infrastructure is in your accounts.
○Communication
The tools you already use.
- Daily
A shared Slack channel; async by default. Two-business-day response on anything that isn't already moving. - Weekly
A Friday demo on a fixed time slot. A two-minute video in your inbox if the slot doesn't suit. Both, if you ask. - Decisions
Design review in shared files. Decisions logged in a single page so the trail outlives the people on the call. - Escalation
One named principal on our side. One named owner on yours. Direct line each way for the things that don't wait.
○ Ownership
You own the code. You own the repo. You own the customer data. We hand over and step back.
The code
Committed to your GitHub or GitLab from the first line. Conventional history, no squashed surprises. Linted, typed, tested where it matters.
The infrastructure
Vercel, Supabase, Resend, whatever the build needs — all provisioned in your accounts and billed to you. We hold no credentials at handoff.
The IP
Yours, on signing. No royalty, no licensing back. We retain the right to describe the engagement publicly with your approval.
○ Pricing
What it costs, in ranges.
Three engagements per quarter. We quote in fixed fees, never hours. Numbers are in USD; payable on milestone, net thirty.
- Discovery—Fixed fee. Two to three weeks. Outputs land regardless of what comes after.
- Build—Fixed fee or milestone, agreed before kickoff. Eight to fourteen weeks.
- Handoff & supportIncludedThree months of named support after launch, bundled into the build fee.
Three slots a year. Q3 2026 is open.
○ What we don't do
The work we say no to.
- Retainer engagements.Retainers reward presence over output. We charge for delivered work.
- Template builds.If your problem fits a template, you don't need us. Buy the template.
- Marketing sites without an operation behind them.Brochure work is a different craft. We'll point you to studios who do it well.
- Outsourced delivery.The principal who sold the work builds the work. No subcontractor chain.
○ FAQ
Five questions a buyer asks.
How fast can we start?
Discovery can begin two to four weeks after a signed contract. Build kicks off within a week of discovery sign-off if a slot is open.
What happens if the project goes sideways?
We pause and rescope. The contract has a defined exit at every milestone — neither side is locked in. We return any unspent fee.
Do you sign NDAs?
Yes, on day one. We have a one-page mutual NDA we'll send you, or we'll sign yours within twenty-four hours of receiving it.
Will you contract in our jurisdiction?
Default contracting jurisdiction is Delaware. We'll switch to your state on request.
What's your stack?
Defaults: TypeScript, Next.js, Postgres on Supabase, Vercel for hosting, Resend for transactional mail. We swap any of it when the engagement justifies — see the work pages for stack-by-project specifics.