HALO · Human-Agent Loop Operations
How we work: the HALO method.
HALO is how we lead your product every week. One rule sums it up: nothing counts as done until it produces a real, verified signal.
Principles
Three rules we don't negotiate
01
Real signals, not finished tasks
Before work starts, every ticket states what proves it works: a flow that passes in production, a metric that moves, a published release. No signal, not done.
02
Whoever builds it doesn't verify it
Verification is done by someone else, at a different time and with evidence. Separating building from verifying is what makes "done" mean something.
03
Humans decide, AI executes within limits
The important decisions (architecture, priorities, what reaches production) are made by people. AI speeds up the work within clear limits and with human approval.
Cadence
Five reviews, always the same
Four every week and one a month. Short, with a clear goal and in writing.
01
Monday
45 minWeekly planning
The week's priorities and a written signal on every ticket: what has to happen for it to count as done.
02
Tuesday to Thursday
10 min · asyncProgress check
Blockers and dependencies, in writing and without long meetings.
03
Wednesday
30 minConvergence review
Open branches, up-to-date documentation and decisions in writing.
04
Friday
60–90 minSignal reading
Only verified work gets closed. Anything without a signal goes back to the queue.
05
Monthly
2 hCapability and cost review
Cloud, SaaS and AI: what to keep, what to cut and what to optimize.
Deliverables
What you receive
Weekly report for leadership
What was closed with a signal, what is blocked and what needs deciding.
Monthly cost review
A presentation of technology costs with concrete decisions: keep, cut or optimize.
Every ticket with a defined signal
Before work starts, we write down what proves it is done.
Portal with hours and deliverables
Your hours used, invoices, reports and documentation, always at hand.
Limits and safety
Fast, but with a safety net
Automatic rules in the repository
Nothing goes to production without review: protected branches, mandatory reviews and automated checks before every release.
Switches to turn features off
New or sensitive features can be turned off without shipping a new version if something doesn't behave as expected.
AI as an assistant, with human approval
We use AI to write, review and analyze faster, but no change is accepted until a person approves it.
In a team
The same method for any team size
With one founder and one developer or with several teams, the rules don't change. What changes is who runs each review.
- One owner per area, not a committee.
- Verification is done by someone other than the builder.
- The same reviews, shared across the team.
Formats
How it fits the formats
Two-week cadence
Monthly CTO
12 h/month · €1,200/month · VAT not included
Planning and results review every two weeks, a monthly capability and cost review, architecture decisions and async availability.
Full weekly cadence
Hands-on CTO
30 h/month · €3,000/month · VAT not included
All five reviews every week, the weekly report for leadership and execution hours: development, design and releases.
The diagnosis and hour bundles apply the same principles to a specific piece of work.
See all formats and pricingFree manual
Building solo?
The HALO method manual for founders working solo with AI. Free.
Shall we apply it to your product?
Start with the diagnosis: 3 hours, €300, VAT not included. If you then book hours with us, the €300 is deducted from your first invoice.
Book your diagnosis (€300)