PROCESS
Five steps.
No surprises.
Every project runs the same five steps. You always know what's happening now, what comes next and what it costs — and you can stop after any step and still keep something useful.
-
STEP 01
Map
We learn how you work before we suggest anything.
We sit with the people doing the job and follow one record all the way through — an order, a delivery, a new product. We count the systems it touches, the steps a person does by hand, and the minutes each one takes. Most projects change shape right here, because the expensive problem is rarely the one that got us called.
What you get
- A written map of how the work flows today
- What the current workaround costs you, in real minutes
- A scoped recommendation — including the honest answer, if the right move is to buy something instead of build
-
STEP 02
Prototype
You use a working screen before we build the real one.
We build the smallest version that proves the idea works — usually one workflow, running on real data, on our servers. Your team clicks around in it. Anything we got wrong becomes obvious in a week instead of in month four, which is the whole reason we do it.
What you get
- A live prototype you can log into and try
- An updated scope with a fixed price
- A written list of what we got wrong in Map
-
STEP 03
Build
Short cycles, working software, no quiet months.
We build in one to two week cycles against the agreed scope, and you see the running system at the end of each one. We write against your real systems from day one, in a sandbox where the vendor gives us one, because integration surprises found late are the main reason software projects run over.
What you get
- A running system that grows every cycle
- A short written update after each cycle
- Access to the code from day one
-
STEP 04
Deploy
One command to install, on your servers or ours.
The system ships as a Docker stack with health checks, database updates that apply themselves on start-up, and a one-line installer for install, update and remove. We run it next to your current process until the numbers agree, then switch over. Then we train your team on the screens they'll actually use.
What you get
- Live deployment, with the installer and backups set up
- A short guide for whoever runs it day to day
- A training session, recorded for the next hire
-
STEP 05
Support
The people who built it are the people who look after it.
Software that talks to other companies' systems needs someone watching it. We keep an eye on what we run, fix what breaks, and stay on top of the platform changes that show up whether you asked for them or not. Most clients keep a small monthly retainer. Some take the code and run it themselves.
What you get
- Monitoring, and a response time we agree up front
- A monthly note on what changed
- The option to walk away with everything, any time
PRICING & SHAPE
What it costs and how long it takes
$99
Covers Map and Prototype. We credit it against the build if you go ahead.
A fixed price per phase
We quote the build once the prototype has settled what it actually is. The number you approve is the number you pay.
Two to four weeks
A working prototype in the first week or two, and a system your team is using a week or two after that. Bigger builds that touch several outside systems take longer — the case studies give their real timelines.
Support you can cancel
A small monthly retainer, and you keep the code and the data whether you keep us or not.
NEXT STEP
Start at step one.
Map is a small fixed fee. You end up with a written process map and an honest recommendation — including the one where you buy something instead of building it.
A 30-minute call. No slide deck, no obligation.
We reply within one business day.