Two ways to buy us. A monthly plan, where we build the thing and then keep running it, or a fixed project with a defined end, for when you need an answer rather than a partner. Both are published here in full.
Every plan includes building the thing, hosting it, fixing it, and owning it. What changes between them is how much of us you get each month, and the effective rate falls as the plan rises.
One system, built properly and kept running.
$500per month
The plan most organizations start on. We build the thing in month one, then it is live, watched, and improving a few hours at a time.
For an organization whose week already runs on it.
$1,000per month
Twice the build time and a standing monthly meeting, for the point where staff have stopped using the old spreadsheet and the app is the system of record.
For software that has become how the work gets done.
$2,500per month
Enough hours to keep a real roadmap moving, on infrastructure that is only yours, with one engineer who knows your operation without being briefed.
For multi-site operations and anything carrying a compliance obligation.
$7,500per month
Half of the studio, pointed at you. A written service level, an on-call rotation, and the documentation an auditor or an insurer is going to ask for.
On every plan, including the $500 one
A board wants a number before it votes. A grant application needs a specification. A lender wants to see that somebody did the arithmetic. Discovery is a fixed project with a defined end, billed flat at $150 an hour, and every deliverable is a document you own outright and can hand to any developer alive.
You know something is broken. You do not yet know what to build.
$3,00020 hours at $150
We sit with the people doing the work, map how it actually happens today, and come back with a written recommendation and an estimate that has arithmetic behind it.
You know roughly what to build and need to see it before you commit.
$6,00040 hours at $150
Everything in Scoping, plus a look at the records you already have and a clickable prototype real enough to put in front of the people who would use it.
The system touches other systems, or it touches money.
$9,00060 hours at $150
Everything in Blueprint, plus the assessments that decide whether a build is actually feasible: the integrations, the migration, and who is allowed to see what.
Somebody who is not in the room has to approve the spend.
$15,000100 hours at $150
Everything in Specification, written up so a board, a grant committee, or a lender can act on it without you translating. Including the part where you take it to other vendors.
How discovery works, on any of the four
It works on your screen. You already suspect it will not work on anyone else's.
The tools are genuinely good now, and people with no engineering background are building real things with them. Then comes the wall: the login is decorative, the API keys are sitting in the browser where anyone can read them, the database will hand a stranger every row, nothing is backed up, and the deploy has failed nine times for a reason nobody can explain.
Bring us what you have. Twenty hours is the floor because below that we can read your code or we can fix your code, but not both, and an assessment you cannot act on is worse than none.
Sometimes the honest answer is that what you built is fine and it needs a week of hardening rather than a rebuild. That answer comes out in the first few hours, and we would rather give it to you than sell you a rewrite you did not need.
Every route, every query, every dependency, and the deploy. We try to break it the way a stranger would, and we look specifically at the things AI-assisted builds get wrong: authorization that only exists in the interface, secrets shipped to the browser, and a database that trusts whoever is asking.
What is solid, what is a security problem, what has to be rebuilt before it can hold real customers or real money, and what it would cost. Plain English, ranked by what would actually hurt you, and yours to take to any developer if you would rather not use us.
Starting with anything that exposes data, then whatever stands between you and a real user. If the list is longer than the hours, we tell you what is left and quote it before we touch it.
The repository, the hosting, the domain, the database, and every third-party account, transferred to you. We rotate every credential that was ever in the code, and hand you the list of what changed.
Your first month. That is the whole answer. Foundation is $500, month one is when we build the first working version, and there is no separate invoice for it.
This is unusual and it is on purpose. A studio that charges $8,000 up front and $200 a month has to sell you a big project whether you need one or not. We would rather be cheap to start and worth keeping.
It is nothing, if the software is wrong. It is a lot, if the software is right and you are polishing it. Most organizations spend the first two or three months on Operations while we build the thing, then settle back down to Foundation once it is doing its job.
Moving between plans takes an email and thirty days. Nobody is stuck on the wrong one.
New behavior. A new screen, a new report, a new field, a new integration, a change to how something works.
What never counts: fixing a bug, hosting, backups, patching, monitoring, responding to you, or the meeting where we decide what to build. If it stops doing what it was built to do, that is on us and it is free.
We quote the overage before we start it, at your plan's effective rate, and you say yes or no in writing. It never lands on an invoice you have not already seen.
Unused hours roll forward one month on every plan, so a quiet month is not a wasted one.
There is an agreement, and you sign it, because you should know what you are buying. What it does not contain is a minimum term, an auto-renewing term, an early termination fee, or a notice window you can miss.
Thirty days notice on any plan. We hand over the code, the data, and the accounts, and we help your next developer get oriented. That is in writing too.
Buy a plan if you already know roughly what needs to exist and you want somebody running it afterwards. Month one is the build, so a plan is usually both faster and cheaper than paying for discovery first.
Buy discovery if somebody who is not in the room has to approve the spend, or if you genuinely do not know what the answer is yet. Buy code rescue if the thing already exists and the question is whether it is safe.
Projects are $150 an hour flat. The plans work out between $94 and $125 an hour. That gap is not a trick, it is what committing to each other is worth.
On giving, yes: 3.5 percent instead of 5 on donations processed through what we build, with card processing paid out of that number.
On the plans, no, and we would rather explain why than pretend. The work costs the same to do. What we can do is be honest about which plan you actually need, which for most congregations under a thousand is Foundation.
Tell us what you are trying to fix and we will tell you which plan it needs, including when the answer is the cheapest one. Nothing on this site costs anything until you decide it is worth it.