Three forms of engagement, one discipline: scope written before we start, fixed price signed, deliverables that check against a written document. From audit to run, on your existing IT.
The three engagements below aren't a catalogue: they are the stages of the method. You enter through the audit. We never build without a written architecture. We never ship without an acceptance bench.
Bounded scope, immersion in your real processes, mapping of what exists.
What's in, what's out — line by line. The price is set here, not along the way.
The system is built against the specification, and accepted against it.
Monitoring, controlled usage cost, scale-up — and reversibility maintained.
A few weeks, a bounded scope, immersion in your real processes — not a remote questionnaire. You come out with three documents that remain yours, whether or not the project continues with us.
We come on site, follow cases end to end, map what exists — tools, flows, data, breaking points. The scope is written before we start.
What the system will do, what it stands on, what it won't do. Firmly costed: the project price comes out of the audit — not out of a guess.
If the project isn't justified, the report says so — that's how you tell an audit from a disguised quote. The audit is paid because it stands on its own.
The specification first: what's in, what's out, line by line — the price is set there. Then the system is built against the specification and accepted against it: agents integrated with your IT, automated flows, a steering cockpit. Every committing action under human approval, every decision journaled.
A processing agent integrated with your IT: it reads the documents, verifies, proposes. Nothing is retained without sign-off — every decision journaled.
Input → structured database → indicators → arbitrated alerts. The full chain, specified then shipped, with its thresholds.
The decision-maker queries and commands the system: actual state, follow-ups, operations. Committing actions go through approval, every time.
A system in production is monitored: availability, output quality, usage cost held within the control plan. Evolutions ship month after month, against the same acceptance bench. Reversibility isn't a sales argument — it's a permanent state.
An agent system stands on the web, on management software, on flows. These four trades live under one roof — one counterpart from specification to run, no cascading subcontractors.
Sites, business apps, portals — the front end of the systems.
Configuration, integration, self-hosting, Polynesian tax localization — the management backbone.
The flows between your tools, executed and monitored.
The layer that reads, proposes, acts — under approval.
Visual identity, guidelines, variations — when the project starts from a blank page.
Wireframes, mock-ups, prototyping — for the critical journeys.
Live sessions, documentation — your teams become autonomous.
Technical audit, page structure — so you can be found.
↳ These skills are never sold on their own: they enter the projects that need them, under the same specification.
We look at one of your processes, we show you what a system in production changes — and we tell you what it costs, in writing, before we start. If it's not at our level of intervention, we'll tell you that too.