How we work
One team works alongside yours over video, learns how the operation runs, and builds what it needs. Discovery, Build, Launch, Evolve, with the same engineer from the first day to the last.
The engagement, moment by moment
The engagement, moment by moment
We start with the real work.
An engineer and a lead join your team on video calls for one to three weeks and watch the real work: how many items come through, how long each one takes, where the errors start. You leave with a plain map of the operation, a short ranked list of what to build, and a scoped proposal for the first Build.
One tool, in your team's hands within weeks.
We build the first item on the list, on the systems you already run where that makes sense. Your team uses an early version on live work and tells us what to change.
Live on the shift, with the people who use it.
We roll it out to the desks and shifts of the people who use it, on a call with them. What breaks in the first days gets fixed in the first days. We stay until it runs without us on the call.
We stay, and the next build is faster.
We host it, watch it, fix it and make the small changes the business keeps asking for. Every quarter we look at the numbers together and propose what to build next.
Discovery
We start by watching the work.
An engineer and a lead spend one to three weeks studying your operation over video calls. They watch the people who receive, pick, invoice, schedule or chase approvals over screen share and camera, and they pull the numbers: how many items, how many minutes each one takes, where the errors come from.
At the end you have a plain map of how the operation runs today, a ranked list of what to build, and a scoped proposal for the first Build with a success measure attached. If you stop there, you still own the map.
What you get
- A map of the operation as it really runs.
- Baseline numbers: volume, minutes per item, error rate.
- A ranked list of what to build, with the reasoning.
- A scoped proposal for the first Build with a success measure.
Build
One piece of software, into daily use.
We build the first item on the list: an internal tool, an integration between two systems, a portal or an automation. Where your existing systems already do a job, we build on them rather than around them.
We ship in stages. Your team is using an early version within weeks, and what they tell us shapes the next stage. The success measure from Discovery is how we both know it worked.
What you get
- One tool, scoped in writing before work starts.
- Built on the systems you already run where that makes sense.
- Early versions in your team's hands, on live work.
- A success measure you can check.
Launch
Into real use, with your team.
Launch is the last stage of the Build. We roll the software out to the people who do the work, at their desks and on their shifts. The first days decide whether a tool sticks, so we are on a call with them through those days.
We step back when the team no longer needs us on the call. Only then does the Build count as done.
What you get
- Rollout with the people who use it, over a call.
- Fixes in the first days, by the people who built it.
- A Build that is finished when it runs on its own.
Evolve
It keeps running, and keeps getting better.
Software nobody looks after slowly stops fitting the business. We host it, monitor it, fix what breaks and make the small changes that come up as the work changes.
Each month includes reserved engineer days for the next improvement. Each quarter we review the numbers with you and suggest the next build. That is how the second project costs less than the first.
What you get
- Hosting, monitoring, fixes and small changes.
- Reserved engineer days every month.
- A quarterly review and a proposal for what comes next.
How we charge
Three parts. No surprises.
- 01
Discovery
A fixed fee for the Discovery, credited in full toward your first Build.
- 02
Build
A fixed scope at a fixed price, agreed in writing before work starts. Launch is included.
- 03
Evolve
A monthly fee on a 12-month term that you can renew or end. A buy-out option is available if you want to own the code outright and take it in-house.
We do not publish prices because every operation is different.
Forward-deployed engineering
Why watching the work beats writing specifications.
We find the problem behind the request.
The request says "we need a report." Watching the person who asks for it work, over a shared screen, usually shows a re-keying step nobody wrote down, or a check that happens in someone's head. We build for that.
The software fits because we watched the work.
Field names, the order of steps, the exception that happens every Friday afternoon: these come from the floor. Nobody has to write them into a requirements document first.
It keeps improving because we stay.
The team that built it is the team that runs it. When the business changes, the software changes with it. There is no new project to kick off and no new vendor to brief.
How we build
A small team, experienced engineers, short cycles.
Each engagement is a small team: an engineer and a lead, more only if the work needs it, and the same people from the first day of Discovery through Evolve. We work in short cycles, put a working version in front of your team early, and let what they do with it decide what comes next.
Our engineers use AI tools in their own work. It is one reason we ship in weeks. Experienced engineers make every decision and own every line.
Questions
The ones we hear first.
Who owns the code?
Ownership terms are set in writing before any Build starts. You always own your data. If you want the code outright, a buy-out option is available.
Other firms scope for free. Why is your Discovery paid?
Because it is work, and because paying for it keeps both sides honest. Experienced people spend weeks studying your operation and hand you a map, baseline numbers and a scoped proposal you can act on with or without us. Free discovery tends to produce the answer that leads to the largest project. The fee is credited in full toward your first Build.
Do we have to keep paying monthly?
Evolve is a 12-month term that you can renew or end. If you would rather take the code in-house, the buy-out option does exactly that.
How fast is a first release?
Discovery takes up to three weeks. A first working version of the Build is in your team's hands within weeks after that, and we ship in stages from there rather than waiting until everything is finished.
Do you work on site?
No. We work remotely, over Teams or video calls, with a direct line your team can call when something comes up. We watch the real work over screen share, or on a camera your team walks through the floor.
Start with a Discovery.
Up to three weeks studying your operation, and a map of how it really runs that you keep either way.