I do not publish prices. Here is everything else.
I have never seen two businesses with the same problem. The same job, invoice chasing, can be a two-week build in one company and a long integration project in another with an older system and four approval steps. A published figure would be either wrong often enough to be useless, or so hedged it tells you nothing. What I can commit to is the structure, and every item below is in the contract.
What is fixed
- The Blueprint fee is quoted before you commit, as one number, on the triage call.
- It is credited in full against the build, so if you build with me it costs you nothing.
- The build is one fixed price against a written scope. Not a range, not an hourly rate, and it does not move unless you change the scope. If I underestimate, that is mine to carry.
- The monthly plan is a flat fee, cancellable on thirty days' notice, with no annual lock.
What is not fixed, and why
Model and platform running costs. They depend on volume, they are billed to your own accounts, and I do not mark them up. The Blueprint gives you the expected figure and the cap before you commit, and the automation refuses to run a model it has no price for, so the bill cannot run away quietly.
What you own, and when
It is yours as it is built, and you hold the code, the prompts, the credentials and the runbook from the day each automation goes live. If you end the monthly plan, the automations keep running until something upstream changes: a model is retired, an API moves, a login expires. Nobody will be watching for that, so the runbook tells your team, or the next developer, exactly what to check.
What I will not do
Day rates. Change requests for work that was always in scope. A discovery invoice after the project has started. A support tier that turns out to exclude the thing that broke.
And if you just want a ballpark, ask on the triage call. The policy is about the website, not about being cagey with somebody who is genuinely deciding.