How it works
We map it. You sign it.
We build it. Your team runs it.
Twelve weeks on a clock you can audit, a blueprint you sign before a single screen gets configured, and two guarantees in writing. This page is the whole method, including the parts that protect you from us.
Blueprint · W1 to 4
System Build · W5 to 12
First automation · target W8
Two guarantees · verbatim below
The method, drawn
Twelve weeks. Five verbs.
One line runs through the whole engagement. It starts the way your operation actually is, tangled, and it is straight by the end. That is the job, drawn to scale. Follow it down.
Diagnose
Weeks 1 to 2
We sit inside your operation and map every handoff the way it actually happens. Not the org chart. The version with the leaks in it.
You keep: the AS-IS maps, corrected by your own team
Design
Weeks 3 to 4
The future state, written down and priced. Every tool you own gets a keep, connect, or replace verdict. You sign before we build anything. Hard gate.
You keep: the signed blueprint, either way
Install
Weeks 5 to 10
Configuration, data migration, integrations, and training role by role on your real jobs. Scope stays locked to the signed blueprint.
You keep: one operating layer your data already lives in
Automate
Weeks 8 to 12W8 · first automation target
The first approved automation is targeted for around Week 8. Your team validates its output before it expands.
You keep: agents drafting, your office approving
Operate
Ongoing
After go-live, usage and workflow completion are tracked by role during support. New automations are added only after the system is stable, measured monthly.
You keep: one weekly operating view you trust
In our contracts, W1 to 4 is Phase 1, the Clarity Phase. The verbs are the story; the phases are the paper.
What we install
Three layers, installed in this order.
Layer 1 · Foundation
One system of record.
Leads, jobs, crews, invoices, and cash in one place. Odoo and HubSpot, infrastructure thousands of companies already run, configured around how your company actually works. Not eleven tools held together by the office manager.
Layer 2 · Translation
Process before configuration.
We map how the work really happens before a single screen gets configured. The design is written down, priced, and signed before the build starts. That document is the contract.
Layer 3 · Execution
Agents inside the system.
Governed AI agents work where your data lives. They recover missed calls, push finished jobs to invoice, and chase receivables. Narrow scope, real permissions, full audit trail, and a person approving anything that touches money or a customer.
The clock
Week by week, the way the contract reads it.
W1 to 2
Discovery
Every handoff mapped, department by department.
W3
AS-IS on paper
You review and correct the maps of how work runs today.
W4
Blueprint signed
Build starts only after sign-offThe future state, tool verdicts, and roadmap, signed before we build.
W5 to 6
Configuration
Sales, field, and finance workflows wired to the blueprint.
W7 to 8
Data + automation
Data migrated, integrations connected, first approved automation targeted.
W9 to 10
Testing
Your team validates the system on real jobs and real data.
W11 to 12
Go-live
Launch, then a minimum 30 days of go-live support.
Scope is locked at the signed blueprint. That discipline is why the 12-week promise holds.
What can move the date
- Key people unavailable during the mapping weeks.
- Migration data late or incomplete.
- Blueprint approval delayed. The build cannot start without it.
- New scope added after sign-off.
- The decision owner changing mid-project.
When one appears, Arkode records the impact and agrees a revised date before continuing
The dip we warn you about
Two weeks after go-live, productivity dips. Old habits fight new workflows. It is predictable, it is temporary, and pretending otherwise is how systems die. We stay through the dip with role-by-role check-ins, SOPs written per role, and usage tracked in an adoption report, until every required role reaches the adoption target written in the blueprint.
The platform
We don't write you an app.
We configure infrastructure thousands of companies already run on, around how your company works. The operating foundation is Odoo, where Arkode is a partner; the CRM layer is HubSpot or Odoo's own, whichever fits your sales motion; the agents are custom-built on Anthropic's Claude. You are not betting on custom code with one author. The platform is not the point. The blueprint is.
Every tool you own gets one verdict in the blueprint
Keep
It works. It stays. Sometimes the answer is keeping what you have and fixing the handoffs.
Connect
It holds data the system needs. We wire it in instead of replacing it.
Replace
It is the leak. It goes, and the blueprint says exactly what takes its place.
Odoo is the operating foundation. Arkode is the translation layer. The agents, running on Anthropic's Claude models, are the execution layer, and they come after the workflows are clean, not before. We hold both relationships in writing: Odoo Silver Partner, Anthropic partner.
Measure first. Configure second.
The engagements
The path, priced as a path.
Three engagements, in sequence. Each one earns the next; none of them locks you into the one after. Exact scope and figures are set in a proposal against your blueprint, never from a web page.
The Operations Blueprint
Standalone. The entry point for everyone.
We sit in your operation, map every handoff from first call to paid invoice, find the leaks, and design the system. Every tool you own gets a keep, connect, or replace verdict.
In our contracts this is Phase 1, the Clarity Phase. It carries the Clarity Guarantee either way.
You keep: AS-IS maps, the future-state design, tool verdicts, a data plan, the 12-week roadmap, and a signed blueprint.
The System Build
For operators with a signed blueprint.
We build exactly what you signed: one operating layer connecting sales, field, and finance, configured on Odoo and HubSpot, your data migrated, your team trained role by role on your real jobs. The first approved automation is targeted for around Week 8. Your team validates its output before it expands.
Not sold separately, and that is the point.
You keep: the live system, migrated data, a role-trained team, SOPs, and go-live with 30 or more days of support.
Managed AI Operations
For companies with a live system.
We install and operate the named agents inside your system, with the autonomy ladder and human approval gates, and we expand one workflow at a time. We operate your automations the way IT manages your systems.
Now installing with early clients.
You keep: a monthly operations report with measured outcomes, and a quarterly expansion plan.
Free vs paid, in plain words
The operations review
Free. Thirty minutes. You leave with a straight answer on fit and the first thing we would fix. It does not produce a blueprint.
The blueprint
The product of Phase 1, the paid four-week mapping. Nothing on this site or that call replaces it.
When you pay
You pay for Phase 1 when you engage it. The build is quoted only against the blueprint you signed, never before.
If Phase 1 disappoints
The Clarity Guarantee below covers it, word for word: your full Phase 1 investment back, no questions asked.
Who keeps the blueprint
You do. The maps, verdicts, and roadmap are yours whether we build the system or someone else does.
Nothing gets built until this moment happens.
"If at the end of Phase 1 you are not fully confident in the foundation we've built together, Arkode will return your full Phase 1 investment. No questions asked."
"Arkode does not leave until the system runs per the agreed blueprint."
Both guarantees appear in the contract exactly as quoted here.
30 minutes · no deck
The method survives a hard look. Bring one.
Bring your current tools, your team size, and one workflow that keeps breaking. In 30 minutes, we will tell you whether the method fits, what the blueprint would examine, and where we would not start. The agents the build makes possible are here.