Give one agent a clear operating boundary.
Founder-led. One workflow, one named owner, one testable outcome. A paid, fixed-scope engagement that ends in a boundary you can defend rather than a proof of concept nobody owns.
Ten working days from agreed kickoff · founder-led · fixed fee confirmed in the written proposal
Opens the scoped intake below, read by the founder.
A — Scope
What the engagement delivers.
- Workflow and authority map
- The workflow drawn step by step, marking where a human decides, where the agent acts, and where authority is currently contested or undefined.
- Mandate and permissions
- What the agent may do, on whose mandate, inside which limits, and which actions stay outside its reach entirely.
- Human approval and exception design
- The approval points, the thresholds that trigger them, and the escalation, reversal and revocation path when something falls outside the boundary.
- Test specifications and evidence review
- Written pass and fail lines for the workflow, plus the evidence each run should leave behind so a result can be checked rather than trusted.
- Handoff with implementation priorities
- A single handoff document: what is ready, what is blocked, what should be built first, and what should not be automated yet.
B — Sequence
How the ten days run.
- Phase 1 — Scoping and boundariesThe workflow is chosen and bounded with the named owner. Authority, limits, approval points and exceptions are written down before anything is built.
- Phase 2 — Prototype and testRun with your technical counterpart against the written test specifications. The prototype exists to test the boundary, not to enter production.
- Final handoffThe workflow map, mandate and permissions, approval and exception design, test specifications and implementation priorities, reviewed together.
Ten working days from agreed kickoff and receipt of the required access, subject to confirmed availability.
C — Outside this scope
Stated plainly, so nothing is assumed.
- Production integration and deployment
- Payment or funds-movement execution
- Formal certification or accreditation
- Security audit or penetration testing
The pilot designs and tests a boundary. Anything that changes production behaviour, moves money, certifies a system or audits its security is a separate engagement.
D — Proof
Where the method comes from.
- NIVQRA
- I.O.V Lab work on authority design: mandate before action, decision before effect, evidence after effect, revocation as a first-class control. This is the studio’s own product thesis, not client work.
- Read the NIVQRA field note →
- Signal Atlas
- Founder-built product and orchestration work: editorial systems, local signals, maps and AI-assisted discovery across selected European cities. Cited here as build evidence for product and orchestration judgement.
- signalatlas.guide ↗
Both are I.O.V-owned work. No client material, metrics or confidential detail appears on this page.
E — Start
What to send.
Use the enquiry form below and put three things in the message: the one workflow you want bounded, the named owner on your side, and the date the decision has to be made. A named contact and a work email are enough to start.
The fee is fixed and confirmed in a written proposal once the scope is agreed. There is no published price because the scope decides it.
Discuss an agent workflowF — Pilot intake
Put the boundary in writing.
Name the workflow, its owner, the decision date and the result that would count as proof. The fixed fee is confirmed in writing after scope review.