The AI Foundation

The AI brain. Installed.

A bespoke context layer that knows your business. The data feeds and rails for it to run on. And the first workforce automations live on day one. Everything we build for you after this compounds on top.

30 minutes with Titus. No pitch. Honest read on whether we're a fit.
Built in Auckland · Installed across New Zealand and Australia · Owned by you, forever
What it is

Not a finished system. The platform every finished system needs.

A one-off AI tool stays a one-off. You buy a voice agent. It answers the phone. It doesn't know what's in your CRM, doesn't see the quote that just went out, can't tell the receptionist what to follow up on tomorrow morning. It's a single piece, sitting on its own.

The Foundation is the layer underneath. The bespoke context that knows your business, the data feeds wiring it to your systems, the rails the workforce runs on, and the first few automations already live. Everything you and any developer build after this compounds on top, because the foundation work is already done.

Without the Foundation
With the Foundation

Same automations. Different outcome. The Foundation is the difference.

Why it's a requirement

The first build is the expensive one. Every build after gets cheaper.

Every automation you've ever bought paid for the same set-up work twice. The context-gathering. The data plumbing. The security review. The integration scaffolding. The login dance. The "what does your business actually do" interview. That work runs every time, even when you're buying the same thing from the same vendor.

With the Foundation in, that work happens once. The second automation skips it. The third skips it. The tenth pays only for what's genuinely new. You're paying for the build, not the rebuild. By the time you're three automations in, the Foundation has already paid for itself.

100%
Build 01

Full context setup, full data plumbing, full integration scaffolding.

60%
Build 02

Skips context setup. Reuses data plumbing. Half the cost.

40%
Build 03

Skips both. Plugs into existing rails. Most of the cost is the new logic.

Illustrative. Actual numbers depend on the automation. Compounding shape is consistent.

What you get on day one

On handover day, here's what's running on your accounts.

01
Brain

Bespoke context layer plus daily brief.

The brain is trained on your business. Your offers, your pricing, your team, your patterns. Every morning at seven a.m. it briefs you on the previous day's sales, today's calendar, anything that needs a decision, anything that's gone sideways. Two minutes of reading replaces an hour of stitching it together from five different tabs.

02
Rails

Data layer and connections to your key systems.

The data layer pulls from your sources. CRM, calendar, accounting, voice line, whatever scope demands. Two to three system connections live on day one. Adding the fourth, fifth, sixth happens incrementally after handover. Nothing breaks because nothing's bolted together with duct tape.

03
Starter workforce

Between one and three automations live.

Picked during the AI Strategy Intensive based on the bottlenecks costing you the most hours. Voice agent on the inbound line. Quote follow-up engine working every proposal. Cold email running per-lead research at scale. Whatever the audit says will give you the biggest week-one breathing room.

04
Ownership

Full code, IP, documentation, training.

The code lives on your accounts. The IP assignment paperwork's signed. The documentation pack tells anyone you hire later how the system runs. Your team walks out of the training session knowing where to look when something needs attention. From handover, Octavius is optional. Nothing about the install requires us to stay.

How we build

Two weeks from kickoff to handover. Here's the shape.

By the time the build starts, the AI Strategy Intensive has produced the plan. Two weeks turn that plan into a running system.

01
Day 1

Architecture lock-in

Working session with your team to confirm the data sources, lock the integrations, finalise the workforce scope, and sign off the build spec. Nothing gets built until the spec's right.

  • Signals the brain reads
  • Automations the workforce runs
  • Integration points with your stack
03
Days 6 to 9

Starter workforce

The first one to three automations build, test, and ship. The brain learns to route to each piece as it comes online. Mid-week two, your team's seeing AI handle work that used to land in your inbox.

  • Automations ship one at a time
  • Brain routing tested per automation
  • Live data through every component
04
Day 10

Production testing and handover

Production testing on live signals. Full handover pack. Team training. The system runs without us by the end of the day. From this point, we're optional.

  • End-to-end production testing
  • Full handover pack delivered
  • Team training plus 30 days on-call

Lean builds ship in 10 working days. Heavier multi-system installs run a few days longer. Additional automations after the Foundation get scoped per build.

After the Foundation

From week three, every new automation plugs in.

Once the Foundation is in, new workforce automations get added on top. Some owners add their second automation in month two. Some sit on the starter set for a year and build only when a new bottleneck shows up. Either's fine. The Foundation doesn't depreciate.

If you've got an in-house dev or a technical lead, your team can build the next piece themselves. Most owners stay on with us as their AI partner so we keep training, optimising and implementing new automations as the business grows. Either route works, because the foundation work is already done. See the example automation library →

A Foundation installed

What a real install looks like, end to end.

Ian · AVIT Properties · London
Install delivered

Ian runs AVIT Properties, a London property developer. Every reporting cycle, he was burning 80 working hours producing the financial reports for his portfolio. Pulling data from personal emails, utility accounts, and Google Drive. Then reconciling it all by hand in spreadsheets. He'd long given up on outsourcing it. The context lived in his head and his inbox, scattered across systems nobody else could read.

Two weeks after the install, his Foundation was doing the work. The brain pulled data from every source he used. The workforce ran the reconciliation. Reports drafted automatically. Anything that needed human eyes got flagged. 80 hours of solo grind compressed into a couple of hours of final review. The work he thought no one else could touch is now handled by a system trained on the way he thinks.

  • Build time2 weeks
  • Report cycle80 hours to 2 hours
  • SourcesEmail, utility accounts, Google Drive, spreadsheets
  • StatusLive

More Foundation installs in flight. The full case study library lives on the case studies page.

The next step

How to start. Three steps, in this order.

We don't quote on the Discovery Call. We do tell you whether the Foundation is the play, or whether you'd be better off starting with a single automation.

Foundation FAQ

The questions Foundation buyers ask.

The Foundation integrates with HubSpot, Pipedrive, Salesforce, ActiveCampaign, Zoho, and anything else with an API. The Strategy Intensive identifies what stays and what gets replaced.

If you don't have a CRM yet, we put Nexus in as part of the install. White-labelled, runs on your domain, owned by you. Either way the brain reads from the system you already use, not the other way around.

The Foundation is the platform. A single automation is something you install on top of it. Without the Foundation, every automation you buy is a one-off that doesn't share context with anything else in your business.

With the Foundation, every automation built after compounds, because the brain already knows your business. Buying one-off automations first usually costs more in the long run than getting the Foundation in place. The Discovery Call surfaces which one is right for where you are now.

No. The Foundation operates without anyone touching the code. Your team interacts with it through their phone (the brief), through their CRM (cleaner data, automations running in the background), through your phone line (the voice agent). Anyone who can use a phone can use the Foundation.

Technical work only comes in if you want to add new automations after handover, and even then you've got options.

The Foundation's designed to grow. The brain takes new signals. The workforce takes new automations. Adding one is a build task, not a re-architecture.

You can do it in-house if you have a dev. You can hire any competent technical team to do it. Or you can stay on with us as your AI partner and we handle the next implementation as part of the ongoing engagement. Most installs add two or three new automations in the first 12 months as the team figures out what they want next.

The Foundation extends. New product line, new market, an acquisition. The existing brain and infrastructure carry forward. We run a re-architecture session and build out the new shape. You're not starting from zero.

You do, or any competent developer you hire. Everything we build lives on your infrastructure, on your accounts, with your credentials. The code base is yours, fully documented.

If we shut tomorrow, your Foundation keeps running. Like a contractor builds a deck on your house and goes out of business. The deck's still there.

The next step

The day your business stops needing you in every conversation.

The Foundation is what an installed AI brain looks like. Built for your business, owned by you, kept training and improving by your AI partner.

Thirty minutes on the phone tells us both whether what we build and what you need line up.

Book a discovery call →
30 minutes with Titus · No deck · Honest read on whether we're a fit.