Data & process map, then build
Map the foundation first. Then build what it can support.
Most AI projects start with a tool. Ours start with your systems: what data exists, what it can support, and where the hours go.
What the map covers
Your systems, your data, and how work moves between them.
AI is only as good as what it can read. So the map starts underneath the opportunities: the systems, the data in them, and the handoffs between people.
System inventory
Every system you run, and what is actually machine-readable: structured data, scanned documents, free text.
Current-state workflow map
How work moves today. Handoffs, exceptions, re-keying, reconciliations.
Baselines
The operating numbers that matter, each labeled measured, observed or estimated. What we improve gets measured against these.
Ranked, sequenced opportunities
Decision support and automation, in the order the foundation can support them. Including what we recommend you not pursue.
Team-by-team training view
Who needs what, and how the change lands for each team.
A scoped proposal
Build and training scoped and priced separately, so you can say yes to one without the other.
Read-only throughout. Nothing is written to a live system, and nothing is built during the map.
The engagement, step by step
Map → Build → Test → Hand over.
We do the heavy engineering. Your team learns the tools as we build. When we leave, they own it and run it.
01
Map
Two to three weeks, read-only. Every system inventoried, every handoff traced, today's numbers baselined. Then the opportunities, ranked.
02
Build
Real code, real prompts, real configs. No slideware. Your team learns the tools while we ship.
03
Test
Real users, real data. We write the tests that prove it works, and keep at it until it holds.
04
Hand over
It runs in your systems, under your logins. Your team operates it. You keep the code, the prompts and the tests.
Why this method
Cost of building has collapsed.
A working AI prototype that took a team a quarter in 2023 takes a builder a week now. So we don't validate before building. We build to validate. Faster, cheaper, more honest.
You own all of it.
Code, prompts, configs and tests live in a repo you own. Plain tools, so you can swap models or vendors as the market moves.
The exit is the offer.
We don't optimize for retainer expansion. The cleanest engagement is one that ends with you running.
Where we build
Your stack. Not ours.
One client runs Microsoft 365. We indexed thousands of lease documents inside their own SharePoint. Another runs Google Workspace. We stood up the domain, the email and the shared Drive from scratch. We build where the work already lives.
SharePoint or Drive.
Your tenant, your access controls, your people’s logins. The corpus doesn’t move.
Outlook or Gmail.
Drafts land where you already work. Nothing sends without you.
No new platform.
Nothing to buy, nothing to upload somewhere else, nothing to migrate when we leave.
What the build delivers
- → The automation, running in your systems
- → The tests that prove it works, measured against the map’s baselines
- → Code, prompts and configs in a repo you own
- → Your team trained to operate it
Pricing
Data & process map
From $7,500
Fixed price. Scope set on the intro call.
Build
$5–20K+ per build
Priced after the map, against what the map found.
Build it yourself
Included
The map is yours. Your team can build from it.
All deliverables are yours to keep.
Start with the map.
Fixed price, from $7,500. You'll know what to build, what to skip, and what it costs.
Talk about a map →