No fixed-scope projects and no per-hour billing. You pay a time-boxed rate to build, then a monthly fee to keep the system working and improving. The number is scoped to how critical the system is, how big your operation is, and what the system is worth to you. Here is exactly how it's worked out.
Your business isn't software, but it runs on it. Technology is a support function, the ground the business stands on, not the business itself. Most owners know they need an IT strategy and never get to it. I am that function for you: a tailored technology strategy you can see, control, and trust, so your attention stays on the business, not on the systems underneath it.
Build is intense and time-boxed: I ship into your production, in any direction, and own the outcome. When it's live and stable it steps down to Run, an ongoing fee to keep it healthy and improving. A new push later just steps the rate back up for a while, so you are never capped, and never paying build intensity for a system that's just running.
Start high while I build, settle into a low ongoing fee, step up again only when you want new work. You get a budget envelope, not a scope document.
Not how many features it has, how much it would hurt if it broke. A system that holds sensitive data, takes payments, or stops your business when it's down is priced differently from an internal tool where a day of downtime is fine. That single call sets both the build rate and the monthly Run fee. There is one question I'll ask that settles most of it: what happens if this is down for three days?
Each system you have with me is one line on one monthly invoice: a base coverage line, plus a line per system at its tier. Add a system, add a line. Nothing hidden.
A one-person business and a fifty-person one don't pay the same for the same system, and pretending otherwise is how quotes die. What I price against is always what you'd otherwise do: for a solo that's usually nothing at all, for a growing company it's the developer you'd hire, and those are different worlds. So a solo doesn't carry the account-management line a larger client does, and gets a plainer service for it. I'll say that out loud rather than hide it in a discount.
Not maintenance. The running is nearly automatic, that's the point. You're buying three things a single in-house hire rarely delivers:
GDPR, uptime, a vendor API breaking, the law changing. When it goes wrong, it's on me, not on you.
Decision-systems and process expertise on call, without hiring and running a technical team of your own.
You stay on your business. I run the systems it depends on, and keep improving them.
I don't publish a bespoke implementation price list, because a number without your operation attached to it is a guess with a euro sign on it. The decision session is the place to assess what should be built, what can wait, and whether implementation is the right next step.
Bring one decision, project, or bottleneck to a paid session. You receive an external assessment and a written recommendation; any implementation work is scoped separately.
View the decision session →