Who runs on this
Businesses already own what we built them. Paid once, and the code and data went with them.
The problem
One customer. Five apps. Nobody knew it was the same person.
Every card below is the same person, on the same Tuesday. Your team answered her five times, and by closing time no two systems agreed on who she was.
- Dana Whitfield“Do you have the navy one in medium?”Messenger
10:12 - Dana Whitfield“Do you have the navy one in medium?”WhatsApp
10:40TYPED AGAIN - Unknown number“Navy jacket, medium. Do you have it?”Phone
12:05TYPED AGAIN - dana.w@gmail.com“Following up on the navy jacket”Email
14:30TYPED AGAIN - Walk-in“I messaged you this morning?”Counter
16:15TYPED AGAIN
5×
one customer entered by hand, into five systems that will never agree with each other.
- You pay per person, per app
- Five inboxes, none joined up
- No two reports agree
- The same order, typed three times
- Three different stock counts
- Your data on someone else’s server
What changes
Follow one order through the whole system.
One message on WhatsApp at 10:40, paid at the counter at 16:15. Same customer as above. Nobody re-types anything.
10:40InboxWhatsApp
One thread
- “Do you have the navy one in medium?”
- Agent · “Yes, hold it for you?”
- auto
- “Please, I’ll come today”
10:41CRMcreated itself
Dana Whitfield
- Lead score
- 78
- Estimated value
- $ 128.00
- Navy jacket · M
- reserved
16:15Counteroffline-safe
Basket
- Navy jacket · M
- $ 128.00
- Scarf
- $ 24.00
- Total
- $ 152.00
16:16Everywhereone row
History, written by the system
- WhatsApp enquiry
- 10:40
- Stock reserved
- 10:41
- Paid at counter 2
- 16:15
- Online stock reduced
- 16:16
What you actually get
One system, and it already knows the customer.
Not four tools that sync overnight. The inbox, the counter and the calendar are reading the same row.
Illustration of Northwind Inbox, using sample data. Nothing here connects to a real account.
- WhatsApp, Messenger and phone in one thread
- The agent already replied, at 3am
- Same record the counter writes to
The AI layer
The AI runs between the ten, not on top of them.
It scores, drafts, routes and escalates, on your data, inside the system you own. Every screen below is the real thing with sample data, so you can check the work rather than take our word for it.
Scores
CRM · KPI scoring
Ranks tomorrow's calls by who is likeliest to buy, and shows its reasoning next to the number.
Drafts
Chatbot · Agents
Writes the follow-up and answers from your real catalogue, prices and policies, at 3am.
Routes
Inbox · Automation
Sends the order, the booking and the message to whoever owns it, without anyone re-typing it.
Escalates
Every system
Stops at refunds, price overrides and anything it was not trained for, and says so.
The same four behaviours, and where they land across the ten systems we build.
CRM
Scores · Drafts
KPI scoring
Scores
Automation
Routes · Escalates
One inbox
Routes
Agents
Drafts · Routes
Chatbot
Drafts · Escalates
E-commerce
Routes
POS
Routes
Bookings
Routes
Schools
Scores · Routes
Proof of delivery
Four systems. Four businesses that own them.
A meeting intelligence platform, a commerce back office, a sales-call coach and an NGO's donation site. Different problems, with the same team and the same standard underneath each one.
GetLevrg Meeting Intelligence
AI · RAG2026Every client meeting scored, searchable, and answerable in plain English.
Aevian
E-commerce2026The commerce back office: products, variants, stock, shipping and media in one place.
AI Sales Coaching
Data & AI2026Every call scored against the same rubric, not the tenth of them someone had time to review.
SALES
Non-profit · Web2025A donation site for a Barishal charity working in stroke, paralysis and disability.
Every build ends the same way
The last thing we ship is the keys.
Security is part of how the thing is built, not a layer added at the end. It runs on infrastructure you own, under accounts in your name, so when the build is finished there is no back door left to close.
Then the code, the data and the servers change hands, and the invoices stop.
See a finished oneWhat moves to you
- The code
- Your repository, full history
- The data
- Exported and verified with you
- Servers and domains
- Your accounts, your billing
- The access log
- Handed over with everything else
- The admin account
- Yours, and only yours
What we keep
- Standing access
- None
- Our credentials
- Revoked
- Copies of your data
- None
- Third-party trackers
- None
What it costs from here
- Monthly licence
- $ 0
- Per-seat fee
- $ 0
- Fee to add a user
- $ 0
Why own it
Work out your own per-seat bill.
We are not quoting you. Put in your own headcount and your own subscription, and read what the next five years cost.
24 staff
$ 60
Defaults are a mid-market SaaS seat, not our price. Change both, because the point is the shape, and the shape does not change.
Rented, 5 years
$ 86,400
Owned, once
one build
At 24 staff you hand over $ 17,280 a year and own nothing at the end of it. Hire ten more people and it goes up again.
- No per-seat tax
- One system, not ten tools
- AI that does the work
How it works
From your process to your system.
Walk your process
We sit with how you actually work.
Shape the build
We agree what finished looks like before anyone writes code.
Build and migrate
Your team sees it running on real data, not a demo account.
Hand over the keys
You get the running system, the code and the data.
Our own products
Two things we're building for ourselves.
Most of what we build belongs to a client. These two belong to us, and neither is finished. We'd rather show you what they are now than announce them when it's too late for your opinion to matter.
The mark
Our logo, assembling itself.
The same idea as every system on this page. Separate parts, wired together, until they behave like one thing.
Next step






