2026 · Digital engineering firm · Papeete, French Polynesia Capacity: one project opened per month

Agentic architecture,
built to the standard
of your IT projects.

OpenUp designs, writes and ships AI agent systems integrated with your existing IT — audit, architecture, acceptance, run. Governance, reversibility and fixed prices, signed in writing.

Book 30 minutes → See the method ▶
4Trades under one roof
3Signed systems in production
1Project opened per month
<24hResponse time
↳ Audit · from XPF 500,000 ↳ Systems · from XPF 1,500,000 ↳ Fixed prices · written before we start
cockpit.openupagency.com · steering
in production ⤢
↳ the decision-maker asks — the system answers, sources attached answer · sourced · journaled
①
Decision-maker's question "Where does acceptance stand on the invoicing module?"
14:32
②
Sourced answer Acceptance bench: 52/52 tests conform to the specification
2.1 s
③
Prepared action Notify the lead — draft ready, nothing sent
ready
④
Human sign-off Committing action — awaiting your approval
pending
⑤
Logged decision Time-stamped, signed, written to the journal
next
committing actions: approval, every time decisions: journaled usage cost: tracked per case
⊙ bounded action scope ✓ written approval rules
dogfooding · the firm runs on its own system
↳ Built on what you already run · we plug into what works — we architect on top, and everything we write belongs to you
Odoo Sage Shopify Microsoft 365 Google Workspace PostgreSQL n8n APIs & legacy systems
01 · Typical projects /projects

Three typical projects.
One standard of engineering.

Every project starts with a written scope and ends with a system in production — never the other way round. Three typical architectures, drawn from real work: the agent reads, verifies, proposes; a human decides; every decision is journaled.

01.A case processing

The agent processes,
a human decides.

① CASE SUBMITTED documents received, time-stamped ② AGENT · ANALYSIS & CHECKS reads the file · verifies · proposes ◆ HUMAN SIGN-OFF nothing is retained without approval ④ LOGGED DECISION written to the journal YOUR IT DMS · registry · line-of-business

A case-processing agent integrated with your IT: it reads the documents, verifies, proposes. Nothing is retained without sign-off — and every decision is journaled.

Deliverables — specification · agent in production · decision journal

01.B data to decisions

From data entry
to decisions.

① INPUT / FEEDS field entry · imports · dormant exports ② STRUCTURED DATABASE written data model ③ INDICATORS thresholds specified, not guessed ◆ ARBITRATED ALERTS a human decides, informed YOUR IT Odoo · spreadsheets · line-of-business

The full chain, specified then shipped: data that used to sleep in exports becomes a decision tool, with its thresholds and its alerts.

Deliverables — chain mapping · indicator specification · system in production

01.C steering

The system that knows —
and acts.

① DECISION-MAKER'S QUESTION "where do we stand…?" · "chase…" ② SOURCED ANSWER the actual state, read from your IT ③ PREPARED ACTION draft ready — nothing sent ◆ APPROVAL the decision-maker commits — not the agent YOUR IT Odoo · CRM · operations

The decision-maker queries and commands the system: actual state, follow-ups, operations. Committing actions go through approval, every time.

Deliverables — cockpit wired to your IT · bounded action scope · written approval rules

02 · The method /method

From audit to production.
Deliverables at every stage.

Four stages, in this order, no exceptions. That's what separates an engineering project from an experiment — and every stage closes with written, checkable documents that remain yours.

stage 1 / audit

A short, paid audit

Bounded scope, immersion in your real processes, mapping of what exists. Paid because it stands on its own.

Deliverableaudit report + costed target architecture
stage 2 / architecture

Written architecture

What's in, what's out — line by line. The price is set here, not along the way.

Deliverablespecification + written scope
stage 3 / production

Shipped to production

The system is built against the specification, and accepted against it.

Deliverableaccepted system + delivered code
stage 4 / run

Run & governance

Monitoring, controlled usage cost, scale-up — and reversibility maintained.

Deliverablerun plan + reversibility file
ACCOUNTABILITY CHAIN §1 Specification §2 Written architecture §3 Acceptance bench §4 Deliverable provenance Every deliverable checks against a written document. That's our definition of IT-grade delivery.
03 · The discipline /discipline

Three questions settled in writing.
Before we start.

An agent system touches your data, consumes models, and affects your independence from your vendor. These three topics are settled in written documents — not verbal promises.

03.A data · GDPR · sovereignty

Your data:
a written boundary.

ON YOUR SIDE · YOUR INFRASTRUCTURE YOUR DATA database · files AGENTS run locally LOG who · when · what ◆ NAMED, WRITTEN ACCESS RIGHTS register · DPO · CISO what leaves the territory: set down in writing minimized queries, encrypted database · files: never leave AI MODEL · API outside your walls — never a custodian

Where it lives, who accesses it, what leaves the territory — in writing, in language your DPO and your CISO can both read. Sovereignty is a verifiable architecture, not a slogan.

Artifact — data annex: mapping · access rights · processing register

03.B usage cost

Usage cost:
a gauge with thresholds.

COST PER CASE PROCESSED the unit of account, in the control plan actual, tracked CEILING — written, blocking SWITCH — lighter model ALERT THRESHOLD three thresholds, written in the plan ◆ OVERRUN → HUMAN CALL a human decides what's next — never the invoice

An agent system consumes models. We hand over a cost-control plan per case processed — thresholds, switches, ceilings — not a meter that runs away.

Artifact — cost-control plan: thresholds · switches · blocking ceiling

03.C ownership · reversibility

Reversibility:
a right to leave.

THE SYSTEM · IN PRODUCTION, ON YOUR SIDE SOURCE CODE in your repositories DOCUMENTATION kept current at run DATA exportable, open formats WORKFLOWS & AGENTS specifications included if the engagement ends YOU LEAVE WITH THE COMPLETE SYSTEM in the contract — not promised in a meeting REVERSIBILITY FILE kept current at run

Delivered code, documentation, exportable data. If the engagement ends, you leave with the complete system — it's written in the contract.

Artifact — reversibility file: inventory · exports · takeover procedure

04 · Foundations /trades

Four trades under one roof.
That's what makes the architecture deliverable.

An agent system doesn't float in mid-air: it 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.

i / webfront

Web development

Sites, business apps, portals — the front end of the systems.

ii / erpodoo

Odoo ERP

Configuration, integration, self-hosting — the management backbone.

iii / auto.n8n

n8n automation

The flows between your tools, executed and monitored.

iv / aiagents

AI agents

The layer that reads, proposes, acts — under approval.

05 · Cases & artifacts /proof

Proof means artifacts,
not promises.

Three signed systems in production, and engineering artifacts that can be checked: public tender bids run end to end, demos built in 48 hours, dogfooding. References are added here once signed — never before.

↳ dogfooding

The firm runs on its own system.

Pipeline, follow-ups, production, market watch: OpenUp is run by the agentic architecture it designs for its clients. In meetings we don't describe it — we show it.

See it in 30 min →
05.A retail · furniture

Fenua Sofa

E-commerce and Odoo wired into a single system: orders, stock, payment — no double entry.

↳ connected system · in production

05.B distribution · equipment

Fenua Growup

200+ SKUs managed, most management operations automated on Odoo.

↳ automated management · in production

05.C events · platform

Matari'i

An event platform designed, built and shipped — v1 delivered, v2 in progress.

↳ platform delivered · v1 in production

Artifact — public tender bid: technical memorandum, annexes and forms assembled and checked item by item, with working demonstrators to back them.
Artifact — working business demo built in 48 hours for a first meeting — on the prospect's real case, not a generic dataset.
Reserved — public reference (signed only).
Reserved — public reference (signed only).
claude · /agents/production
running
Agent in production at OpenUp — supervised execution, sensitive data redacted
↳ artifact — agent in production at OpenUp (dogfooding), real capture tokens redacted · continuous monitoring
See the case studies →
06 · The journal /log

Engineering, governance,
field notes.

What we learn running projects in French Polynesia — method, governance, public procurement. Published when there's something to say. Never to sell.

upcoming—
public procurement

Digital public procurement in French Polynesia: what the thresholds really change

The thresholds, the required documents, dematerialization — what a public buyer expects from a digital bid in 2026.

articleread →
upcoming—
governance

AI agent governance: who approves what, and how it's written down

Bounded action scope, approval rules, decision journal: the governance of an agent system is something you write.

articleread →
upcoming—
architecture

Sovereignty: an architecture can be verified, a slogan cannot

Where the data lives, who accesses it, what leaves the territory — sovereignty as an architecture document, not a talking point.

articleread →
↳ first contact · 30 minutes · on a real case

30 minutes,
on a real case.

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.

Book 30 minutes → [email protected] ↗
< 24 h response time Fixed prices · written before we start Audit · from XPF 500,000