Most engagements are a single monthly partnership fee covering the senior team, the builds in your queue, weekly training, executive advisory, your client portal, and the AI tooling costs we incur while building. Three-month initial term, then month to month with 30 days' notice. You own what we build.
The point of a single fee is that you stop doing arithmetic every time you want something. No hourly meter, no per-build quote, no bill for asking a question.
An operational expert, a technical engineer, and an integrator — with founder John Constantine in every engagement. No junior hand-offs.
Working tools shipped from your idea queue, prioritized with you and hardened for production — not prototypes you have to finish.
Standing sessions that get your people genuinely capable on what we deploy, so the capability stays when we step back.
A monthly review with leadership on roadmap, spend, and the decisions that need an owner or a board.
Live project tracking, the AI idea queue, and per-person training status. You always know what we are doing.
The API and tooling spend we run up while building is ours, not a line item that lands on your invoice.
Ownership, exit, and what happens after launch. We would rather you read these now than discover them in a contract later.
Deliverables built for your business belong to your business. We keep only our own pre-existing reusable code and internal frameworks — the scaffolding we bring to every project, not anything specific to you.
There is also a second path if you want it: co-own the IP in exchange for a lower build cost, with an optional route to taking the platform to market together in non-competitive territories. That is an option, never a condition. More on how that works.
A 3-month initial term, because meaningful AI work does not finish in four weeks and neither of us benefits from pretending otherwise. After that it continues month to month with 30 days' notice from either side.
The monthly fee is the monthly fee. If something falls outside the agreed scope, we discuss it and agree in writing before work starts. Nothing shows up on an invoice that was not a conversation first.
Tooling costs during development are covered. Once a tool is live, its ongoing hosting and API usage are billed at cost plus a small administrative margin — or you take it in-house and pay the vendors directly. No markup game, no lock-in.
Give 30 days' notice after the initial term and you keep everything built to that point, with documentation and access handed over. We do not hold client work hostage to a renewal conversation.
We scope to your goals rather than publish a rate card — the honest reason is that a five-employee company and a two-hundred-person operator need different things and should not pay the same. But you deserve a frame of reference before you get on a call.
Where we sit: our monthly partnership is priced like a fractional executive relationship, not like a development shop — because builds are only one of the six things in it. On the first call we will tell you what your situation actually needs, including if that is less than a full partnership.
Four things drive scope. None of them is how big your company is — they are all about how much work you want moving at once.
How many tools you want in flight at a time, and how complex each one is.
Training five people and training eighty are different engagements.
Every additional system that has to connect adds real engineering work.
Regulated data, security review, or audit requirements change what production-ready means.
The monthly model is our most common shape because it is the one that produces the most durable results. It is not the only way to work with us.
The full relationship: senior team, builds, training, advisory, portal, dev-phase AI costs. Three-month initial term, then month to month.
Sometimes you need one thing done well rather than an ongoing relationship. We scope those honestly, without trying to convert them into a retainer.
What people ask before signing, answered without hedging.
Because a rate card would either overcharge the small company or undersell the complex one. Scope is driven by build volume, team size, systems to integrate, and compliance load — and those vary enormously between two businesses with identical revenue.
What we will do is size it on the first call, in the conversation, rather than after three meetings.
You do. Deliverables built for your business belong to your business; we retain only our pre-existing reusable, non-client-specific code. If you would rather trade ownership for a lower build cost, the co-ownership path is available — with your data never exposed and any commercialization restricted to non-competitive markets.
During development, the AI tooling spend is ours. Once something is in production, its hosting and API usage are billed at cost plus a small administrative margin — or you take it in-house and pay the vendors directly. Either way you see the real numbers.
No. If a request is outside the agreed scope, we talk about it and agree in writing before anything starts. The failure mode we are avoiding is the one where an invoice becomes an argument.
After the 3-month initial term, 30 days' notice from either side. You keep the deliverables, the documentation, and the access. Our view is that if the work is good you will stay, and if it is not you should not have to negotiate your way out.
Yes — founder-run companies, businesses with established executive teams and boards, and PE-backed operators all fit. The requirement is not ownership structure, it is that someone can approve and move without a long procurement cycle.
Tell us what you are trying to fix and we will tell you what it takes — including if the answer is smaller than a partnership.