Two Engines,
One Book of Business
Three sentences
It is what they sign, what they renew, and what they call about.
Their front door, their leads, their reputation — running on our engine.
A small team delivering both, without hiring in proportion.
The bundle we thought was our moat
is now table stakes.
That does not break the strategy. It narrows where we compete — and it changes what we should spend the next two quarters doing.
The Company
How EdgePointe is structured, and what the second engine adds.
One relationship. Two engines.
CLIENT
Managed Service Provider
Keep it running, keep it safe, keep it planned.
Managed Intelligence Provider
Own the digital front door and the work behind it.
The shared substrate
Method written down, not headcount hired
The same worker serves every client
Every change ships the same way
Both engines read the same account
What the second engine changes
The Operating Model
How AI, agents and codified skills become leverage.
Four layers
Reasoning — in the surfaces the team already works in, and inside the product itself
Method — a senior practitioner's approach, written down so it runs the same way every time
Judgment — expertise with a point of view, credentialed by framework
Permission — what is allowed to ship, and what is not
23 skills, installed today
Each one a method written down. Versioned like code — improve it once, and everyone has it.
Managed IT, security, cloud, network, backup, AV, vCIO, compliance
Proposals, onboarding, QBRs, marketing, satisfaction
Clone, web design, publish, billing, roles
Billing, profitability, vendors, hiring, acquisitions
Credential by framework,
never by biography
Twelve roles. Each carries a seniority, the named standards it works from, a safety assumption it never relaxes, and a definition of done.
Every gate fails closed
Zero failures, or no deploy. There is no override.
Wrong assets, cross-tenant references, banned defaults — all hard stops.
A separate reviewer with no memory of the build grades it.
The owner approves before anything goes live.
The line
What it means. What it doesn't.
- Tier one stops scaling with headcount
- Delivery artefacts are generated, not assembled
- A client site is a bundle, not a project
- One deploy improves the whole book
- That the business runs unattended
- That we can take unlimited clients
- That maturity is uniform across service lines
- That quality is automatic — the gates do that
The Platform
Vantage end to end — and the engineering standards behind it.
One worker. Every client.
No per-client code anywhere in the system.
Described, then rendered
A seven-step wizard. Gated, quarantined, preview-fenced.
Identity, theme tokens, content, assets. A description of a site — not a site.
Generic by construction. 33 section modules. It knows no client by name.
Generic by construction
is the whole business model.
Improve it once, and the entire book improves at the next deploy. Build a client site, and it costs a bundle to author — not a project to scope, staff and negotiate.
Clone to Elite
Read in a real browser. Copy verbatim, colour from the logo, every asset checked.
Numbers before eyes. Tolerances stated, cheapest correction first.
Better than the original, using their own proof. Never invent what is not there.
Completeness, parity, quality — graded by a reviewer that did not build it.
Through the same pipeline. Then the reach tools switch on.
Nobody deploys by hand
Four layers of recovery
One database, one cache, one asset store — separated at every layer that touches them.
Every section snapshotted before it changes
A re-seed never silently overwrites an owner's work
Any moment in the last thirty days
The previous version, one command away
Layered, and fail-closed
The Honest Read
Where the moat closed, and where it holds.
What we can stop claiming
Narrower. Harder to copy.
Every competitor has to buy the customer. We are already in the building.
No reseller margin. Nobody can reprice us out of our own product.
Arrive with their site already rebuilt. A demonstration, not a pitch.
A client running their front door on our platform is not shopping their IT contract.
Four decisions
The next ninety days
The MSP earns the client.Vantage makes them ours to keep.AI is how a small team does both.
Every architecture in this film corresponds to code running in production today, behind a gate that has to pass before anything ships. The constraint is not engineering — it is going to market.