Fifteen minutes over the phone or a coffee. We're not selling anything on this call — we're finding out what your team wastes hours on. What documents get retyped, what reports get rebuilt every week, what the person who "knows how it all works" would do if they had a day back. If there's a build here, we'll say so. If there isn't, we'll say that too.
A written scope: what we'll build, what it does, what it doesn't do, what it costs, and roughly when it'll be done. Fixed-price where we can. No open-ended engagements, no discovery phases that run for months, no scope that expands quietly. If we hit a wall mid-build, we'll come back with new numbers before we keep going.
We build it. You see it as it comes together, not at the end. What doesn't fit changes shape while we still have the panels in place. The people who'll actually use it get their hands on it early — not at "user acceptance testing" three days before go-live.
The code, the data, the runbook — yours. We stay on for whatever ongoing support makes sense for your business. Most people keep us on for changes as things shift; some take it in-house and run it themselves. Both are fine.
Most builds are fixed-price against a written scope. The scope names what you're getting, what it costs, and what happens if things change mid-build.
Ongoing support — hosting, changes as your business shifts, occasional new features — is monthly, and it's a choice, not a condition. Cancel any time, take the code with you.
Every quote sits inside three ranges depending on how much needs to be built: