Nothing starts from zero
The hypothesis, the authority, the harness and the Map stay recorded where the machine looks them up. The next project starts with the agreement in place, whatever the service, and so does the next vendor, if you switch.
Services
Five services. One platform underneath all of them.
Each service solves a different problem your company has with AI: where to invest, what remains a human decision, how to roll out, how to build and how to keep it under control. There is no order between them: each one is hired on its own. What the five share is the h|ve Platform underneath, which is why what one project records, the next one already finds ready.
Each one can be hired on its own, in any order. None requires the platform to work. All of them get better with it underneath, and all of them leave artifacts with the company in an open format.
The driving force
The product installs the capacity. The services redesign the work. The platform connects the two.
Most vendors have no platform underneath the service, which is why every project of theirs starts over. Here, the five services read and write on the same layer: what one project decides becomes recorded context, what it installs becomes a rule the tool reads, and the next project, with any of the five, finds that ready.
- Where to investAI Value Discovery
Value hypothesis, baseline and acceptance criteria before approving the investment.
Leaves on the platformThe hypothesis, the decision owners and the acceptance criteria, as executable context.
- What stays with peopleAI Leadership Lab
One day for leadership to decide where AI goes in and what remains a human decision.
Leaves on the platformThe authority matrix with real names and the usage rules, as authority and policy.
- How to roll outScan & Go
The engineering diagnosis and the first governed flow in production, with a gate in every phase.
Leaves on the platformThe configured harness: context, flow, guard, deviation and record, measured in the pilot.
- How to buildFDE Velocity
An engineer inside the team puts one capability into production in six weeks, on top of the platform.
Leaves on the platformThe operation Map, the authority matrix, the decision trail and the measurement.
- How to maintainGoverned Method Packs
The method becomes a rule the tool reads on every session, measured monthly and reviewed quarterly.
Leaves on the platformThe versioned pack, the signed baseline and the monthly reading of the six metrics.
The common layer
h|ve Platform
A layer between people and the technology they use. Context, authority, policy and evidence travel with every execution, whatever the agent, the model or the tool. The five services read and write here.
- Mapcontext
- Floworchestration
- Guardguardrail
- Judgedeviation
- Ledgerrecord
On top of the stack you already have
- LLMs
- Agents
- RAGs
- Cloud and services
- Repositories
- CI/CD
- Boards
- Tests
Why the result grows
Each project starts where the previous one stopped.
A service without a platform leaves a document. A service on top of the platform leaves executable context: the rule where the tool reads it, the authority with a name, the record of who decided what. Whatever the service, the next project finds that in place. That is what makes the result accumulate instead of starting over: the context stays in your house, each project starts from a larger base, and the presence of h|ve shrinks while your company capacity grows.
The scheme
Where the effort goes, project by project
With a vendor without a platform, most of every project goes into learning the business again, and the second one costs almost as much as the first. With the h|ve approach and platform, the learning part shrinks with every project, because what was learned stayed on record, and the part that produces new results grows on top of that base. It holds for any service and any order: what one project decides is not rediscovered in the next, and what it installs is not rebuilt.
A positioning scheme, not a measurement. The number that counts is yours, measured in your company during each project: baseline declared before, result measured after.
The second-project math holds for all five
The second project costs less than the first because the context did not leave with whoever learned it. That holds with any of the five services, in any order, because all of them record on the same layer.
The presence of h|ve shrinks
In every service someone on your team signs the gate and operates afterwards. That is product design: the service ends, the platform stays, and it is yours to operate.
The thesis
The service ends. What it installed keeps running.
Each service solves the problem it came to solve and leaves: one assessment, one day, one rollout, one capability, one pack. What stays is the h|ve Platform configured with the context, the authority, the rules and the record of your operation, run by people in your house. No service exists to create dependence on whoever delivered it.
The five services
One for each problem, side by side.
No order between them: each one solves a different problem and is hired on its own. Each page says, in one sentence, when it does not fit and where we point instead.
Investment decision
AI Value DiscoveryDecide where to invest in AI and how to measure the result, before spending the quarter.
- The decision
- Build, test or stop, with the criterion on record. Stopping is a legitimate result.
- Leaves on the platform
- Value hypothesis, baseline, acceptance criteria and the decision record.
- Process counted
- Numbers as ranges
- Three possible outcomes
Authority decision
AI Leadership LabOne day for leadership to decide where AI goes in, and what remains a human decision.
- The decision
- Where to invest in the next ninety days, which decisions still require a human signature, and what each area does in thirty days.
- Leaves on the platform
- The authority matrix with real names and the AI usage rules, as authority and policy.
- One day, eight hours
- Six to twelve people
- Four artifacts
Platform rollout
Scan & GoThe diagnosis of your engineering and the first governed flow running in production, with a gate in every phase.
- The decision
- How the engineering you already have starts producing better, with traceability of what AI did and who approved it.
- Leaves on the platform
- The configured harness, the person-by-AI matrix, the usage policies and the pilot report.
- Scan, 3 to 4 weeks
- Go, 4 to 6 weeks
- A gate in every phase
Where product and service meet
FDE VelocityAn engineer inside your team puts one capability into production in six weeks, and the context stays with the company.
- The decision
- How to put one business capability into production without the next project starting from zero.
- Leaves on the platform
- The operation Map, the authority matrix, the harness, the decision trail and the measurement.
- Six weeks with gates
- Context on record
- Handover to the team
Continuous governance
Governed Method PacksYour company method becomes a rule the AI reads on every session, measured monthly and reviewed quarterly.
- The decision
- How to keep cost explained, rules valid and proof ready while tools change every few weeks.
- Leaves on the platform
- The pack versioned in six layers, the signed baseline and the monthly reading.
- Installed once
- Kept valid every month
- Six readings
With or without the platform underneath
The difference is not a better consultant. It is having somewhere for the work to stay.
Training ends in a plan. Consulting ends in a report. Rollout ends in a system. In all three cases, what was learned about your business leaves with whoever learned it. Here, it ends with the work running, with an owner and a record, and with the company able to carry on alone.
Service without a platformComes in, learns, delivers a document, leaves.
Every project restarts the learning curve. The rule becomes a PDF, the decision becomes minutes, and when the external question arrives, someone rebuilds the history by hand.
h|ve service, on the h|ve PlatformComes in, records while working, delivers capacity, leaves.
The rule is read by the tool on every session. The decision stays with author, authority and basis. The next project, with h|ve or with another vendor, starts where this one stopped.
ResultEvery project grows the base. None creates dependence.
You can answer who decided what, months later. The knowledge of your business stays in your house. And if you switch vendors, it all remains yours, in an open format.
Where to start
Which problem with AI does your company need to solve now?
One sentence per service. None comes before another: your situation is what chooses. If it is not here, the forty-minute conversation says which way to go, and if no service makes sense right now, we say so.
- You do not know where AI creates value and need to decide where to invest.AI Value Discovery
- Leadership still needs to decide where AI goes in and what remains a human decision.AI Leadership Lab
- You have your own engineering team, AI use exists, and there is no governed flow in production.Scan & Go
- You have no team, or a small one, and need a business capability working.FDE Velocity
- The flow exists and what is missing is control, explained cost and proof.Governed Method Packs
Proof from our own operation
h|ve builds its own platform this way, every day.
Numbers from the h|ve operation measured on 2026-10-30. They are ours, not a client’s, and they prove method discipline, not service results.
605specs approved before code
659pull requests through the gated flow
12,150automated tests
952,320conformance cases