A large firm brings something we cannot: a name your board already trusts, a procurement process already approved, and people in more places than we will ever be.
Advisory and systems-integration programmes are the established way to buy organizational change, and for some of what you are trying to do they remain the right instrument. The difference here is narrow and specific: what arrives at the end, how often it is versioned, and who can rebuild it next year without the firm that wrote it.
The top of this market is enormous. One large integrator's earnings filing for the fiscal year ended 31 August 2025 reported generative AI new bookings of $1.8 billion in the quarter and $5.9 billion for the year (Form 8-K earnings exhibit, 25 September 2025). That scale is not marketing. It buys capabilities a founder-led practice cannot assemble, and three of them are worth naming before we say anything about ourselves. None of these firms publishes per-engagement pricing, so nothing on this page compares anyone's price with ours.
A board that has to explain a decision to an insurer, a regulator or an ownership group has an easier conversation when the name on the engagement is one everybody recognises. That is not irrational. It is a genuine form of risk transfer and it has real value.
Master agreements already signed, security reviews already on file, insurance certificates already lodged, invoicing already understood by your finance team. For a large organization that machinery can be worth more months than the build itself.
Process design, operating-model work, change management, audit, tax, systems you have run for twenty years. When the AI question is one strand of a much larger programme, a firm that can staff all the strands has an advantage that no specialist can answer.
A programme produces something shaped for you and only you, which is its appeal and its liability. A productized deployment produces something shaped like every other deployment, then configured for you, which means the thing you receive has been exercised elsewhere before it reaches your account.
| Question | A bespoke programme | A productized deployment |
|---|---|---|
| What arrives at the end | △Recommendations, then an implementation | ✓A running system in your account, from a tagged release |
| Who can rebuild it next year | △Whoever wrote it, or whoever reads their documents | ✓Anyone competent, from infrastructure as code and runbooks |
| How improvements reach you | ✕A new statement of work | ✓A release, rolled deliberately, one deployment at a time |
| Shape of the fee | △Programme fees, scoped up front | ✓$2,500 assessment, deployment from $2,500, $500 a month, cancel anytime |
| Who profits from the compute | △Depends on the arrangement | ✓Nobody. The provider bills you directly at list price |
| If the relationship ends | △Whatever the contract says | ✓You keep the platform and its source. You lose us, not it |
The "bespoke programme" column describes the shape of that arrangement, not any particular firm's contract, and a well-written programme contract can improve several of these rows. Ask for them in writing. Our figures are the published ladder on the pricing page; longer automation work is scoped per deliverable, in the range of one junior technical hire without the permanent headcount.
We do bespoke work too, and the discipline we hold ourselves to is that it should feed back into the platform rather than become the platform. When a client needs something twice, it becomes a capability every deployment can have. A practice whose revenue depends on the work staying bespoke has the opposite incentive, and that is the structural difference worth examining in any proposal, including ours.
Several jurisdictions, several data protection regimes, local entities, local staff who need to be trained in their own language and time zone. That is a logistics problem before it is a technology problem, and logistics at that scale is precisely what a large firm sells. We would be the wrong choice and would say so.
If the hard part is getting several thousand people to work differently, the technology is a small fraction of the programme. Change management, communications, training design and middle-management alignment are genuine disciplines. We do not staff them.
Some obligations, some boards and some insurers effectively require a recognised name on the engagement. If that is your situation, argue with the requirement or satisfy it, but do not pretend it is not there. A specialist cannot substitute for it.
A perfectly good arrangement is a large firm running the programme and a specialist running the deployment underneath it. We have no interest in owning your whole change agenda. We are interested in the layer that has to be governed, versioned and owned by you.
org.tech is a founder-led practice: one principal with a small bench of contractors. The capacity comes from the platform and the deployment factory, not from headcount, which is why a practice this size can ship releases at the cadence above and hand you a controls matrix at the end of it. It also means there are engagements we should not take, and we will tell you when yours is one of them.
The risk is real. Three things bound it: you own the cloud account, the credentials, the billing relationship and the data, so nothing is held hostage; the engagement produces infrastructure as code, runbooks and architecture records another provider could pick up; and the platform is deployed rather than hosted by us. Continuity sets it out in full.
We publish the posture questionnaire so you can see the questions before the call, and the controls matrix maps 17 technical control rows to SOC 2 Trust Services Criteria and ISO/IEC 27001:2022 Annex A with an enforced, partial or not-enforced verdict on each. We hold no third-party attestation, and we say so.
Yes, and it is a common shape. The boundary we hold is that we keep a direct relationship with you for the platform itself: the account is yours, the contract for the deployment is with you, and we do not become an anonymous subcontractor whose work you cannot inspect. See partners.
Releases cut and rolled deliberately, drift and diff checks before changes, acceptance scripts run against your live deployment after each deploy, the model catalogue refreshed as providers change it, access and role changes, cost watch with budget alarms, a dated operations journal, and a direct line to the person who built it. No queue, and no ticket system in front of it. Managed operations lists it.
We are not arguing that expertise is overpriced or that programmes fail. We are arguing that what you should hold at the end is a versioned system in an account you own, and that this is a different purchase from a recommendation about one.
Bring the proposal you are already holding. The assessment maps the same ground for $2,500 and you keep the deliverable either way.