Pricing
Pay for the hours. Own the result.
Every project is priced by the hours of development it needs. You get an estimate before any work starts.
The three stages
Discovery
One or two weeks with the people who do the work. You get an hours estimate before any build.
Build in weekly rounds
Working software every week, so you steer as it takes shape.
Care plan
We host, watch and improve it. Same-day response when something is critical.
What each stage includes
Discovery
Billed hourly, 1 to 2 weeks. We sit with the people who do the work, map where the data lives, sketch the screens and estimate the hours the build will take. If it is not worth building, we tell you.
Build
Billed hourly, most projects 6 to 12 weeks. You approve the hours estimate before work starts. Then short rounds, with working software to try every week, connected to the tools you already use. Training for your team, and the software is yours.
Care plan
Monthly support, month to month, cancel any time. Hosting, monitoring and nightly backups, plus fixes and changes from Chris, who built your system. A set number of hours for small changes and a check-in each quarter.
Websites
Business websites, online booking and customer portals, set up for local search. Priced the same way, by the hours to design and build. Websites usually take a few weeks.
On a care plan
When something critical breaks, you hear from us the same day.
Critical issues get a response the same day. Bugs get a response within 2 days, and new feature requests within 5 days.
- Same day
- critical issues
- 2 days
- bugs
- 5 days
- new feature requests
What repetitive work may be costing you
Estimate the staff time that goes into manual work today. Bring the number to a call, and we will tell you roughly how many hours a build would take.
A rough estimate of staff time over 50 working weeks. It does not include the cost of the build, and it is not a guarantee of savings.
Talk through your numbersWho this is for
Owners who want their people's time back.
A lot of owners hear "AI" and assume it means fewer jobs. We do not build for that, and we do not believe in it. We build to give people their time back.
Costs are up. Running a business has not gotten easier.
Some of what your staff do all day is the work you hired them for. Some of it is draining: copying numbers between systems, chasing approvals, rebuilding the same report.
What if each of them got two hours a day back?
Where does that time go? What do they get curious about? What do they fix that nobody had time to fix?
Same payroll. More done.
Owners who want a smaller team are a poor fit for us. Owners who want the same team to get more done, and grow revenue because of it, are exactly who we work with.
Pricing questions
Why hourly?
Because every project is different. You pay for the work your project actually needs, with nothing padded in to cover guesswork.
How do I know what it will cost?
After the first call we estimate the hours your project needs, so you know what to expect before any work starts. If the scope changes, we update the estimate and you approve it before we do the extra work.
What makes a project take more hours?
Mostly the number of systems it connects to, how many kinds of users it has and how much of the logic is unique to your business. A dashboard on one data source takes far less time than a system that ties five together.
Do we have to buy a care plan?
No, but most clients choose one. It covers hosting, backups, fixes and changes, and the support comes from Chris, who built your system, so problems get solved quickly.
How fast do you respond on a care plan?
Critical issues get a response the same day. Bugs get a response within 2 days, and new feature requests within 5 days.
Can we start small?
Yes, and we usually recommend it. Pick the one process that hurts most, build that first, and add to it once it is working.
Want an estimate for your project?
Get in touch for a 30-minute call. You will leave with a rough idea of the hours involved, and if it makes sense, a plan for discovery.