Ascension Venture Partners
00 How it works

How AVP works.

One way of working, in three stages. First, diligence maps what still depends on you. Then the architecture writes it down where the team can use it. Then a continuity engagement keeps it working until it runs without you. Specialists and hires come in alongside, whenever the business needs them.

01
The frame

Three ways a business can hold what it knows. Only the third one is owned outright. We call that sovereign.

Traditional, rented, sovereign.

Traditional

Knowledge in people.

The standard is whatever the most senior person in the room remembers. It walks out the door with every resignation, and it cannot be handed to a buyer or a successor. It can only be re-learned, slowly, at the business’s expense.

Rented AI

Knowledge in someone else’s platform.

The business uploads what it knows into tools it subscribes to. The output is useful. The leverage sits in a vendor’s product, priced per seat, and it switches off the day the subscription lapses. The business operates the tool; it does not own the capability.

Sovereign

Knowledge the business owns.

What the business knows is written down and owned outright: the record. The team looks things up in the tools built on top of it, and keeps it current from the manuals. It survives staff turnover, vendor churn, and the owner’s absence. The final call still sits with the business, which is what decision sovereignty means.

AVP builds the third column.

02
The engagement

Diligence first, then architecture, then the retained continuity engagement, then the people it needs.

Diligence, architecture, continuity, people.

The stages run in order. Diligence decides what gets built; architecture builds it; the continuity engagement keeps it alive and embeds the support around it; specialists and hires come in alongside, whenever the business needs them. A business can stop after any stage and keep everything produced up to that point.

First

Diligence.

What still depends on you, and what it costs.

You get the read a buyer would run on the business, run first and run for you. Every place the business still routes through you, ranked by what it costs on the day you sell it or step back: the decisions only you can make, the knowledge only you hold, the relationships that would leave with you.

The deliverable is the Sovereign Audit: a written map of what depends on you and what it would take to change that, in the order to do it. Fixed scope, and the business keeps it whether or not anything follows.

Deliverables The map, the ranked dependency list, and the sequence for removing them.
Engagement shape
Fixed scope
Typical duration
Weeks, not months
Output
A map the business keeps
Next

Architecture.

Everything in your head, built into something the business owns.

You get everything in your head written down, in a form the team can actually use, and built into the systems the business runs on. Operations, standards, pricing logic, and the reasoning behind the exceptions, structured and owned outright. The tools the team uses to ask it questions and get answers sit on top, so what you know becomes what the business knows.

In AVP’s method the written record is the corpus, the tools are readers, and the manuals written alongside let the team maintain both without AVP in the room. Everything is built on the business’s own accounts and infrastructure. Nothing material to the business lives in a vendor relationship AVP controls.

Deliverables The record itself, the tools for the roles that need them, and the manuals for maintaining both.
Engagement shape
Build, then hand over
Runs on
The business’s own infrastructure
Output
Sovereign infrastructure, owned outright
Then

Continuity.

Embedded until it runs without you.

You get someone alongside you while the business learns to run on it. This is the retained engagement: AVP embedded with the team, giving commercial and technical support while the architecture becomes the way the business actually runs. The record is maintained and extended, the tools grow with the operation, the manuals stay current.

This is where the transition happens against working infrastructure rather than a plan: the exit prepared, the succession handed over, the owner stepping back while the standard holds.

The same work usually takes cost out. Duplicated tools get consolidated into systems the business owns, and work that was being done by the wrong people at the wrong rate moves to the right ones. That matters beyond the monthly saving: an owner heading toward a sale is valued on profit, so the cost that comes out is priced into what the business is worth.

Deliverables Embedded commercial and technical support, maintenance and extension of the record, operating cadence.
Engagement shape
Monthly retainer
Cadence
Embedded in the operating rhythm
Ends
When the team runs it without AVP
Alongside

Specialists and hires.

You get the people the business needs to run what has been built. Operations-heavy businesses run on specialists: chefs, surveyors, engineers, whatever the trade is. Working inside the business makes the gaps visible.

AVP sources fractional and contract specialists to fill them fast, and runs the search for permanent hires when the role is proven.

Deliverables Fractional and contract specialists in place, permanent search run when the role is proven.
Engagement shape
Scoped and priced on its own
Runs on
The business’s own contracts
Output
The right people, in place

What sits outside the monthly.

The retainer has a defined edge. Running and improving what has been built sits inside it. New building, specialist search, and anything added on top is scoped as its own piece with its own brief, so the monthly does not quietly expand. An owner always knows what the number covers.

03
What ownership means

A standard of the work, not a preference.

The infrastructure is the client’s.

Everything AVP deploys lives on the client’s accounts and infrastructure and is owned by the client outright: the record, the tools, the manuals. There is no platform to stay subscribed to and no licence that expires with the relationship.

This is a standard of the work, not a preference. The engagements exist because of transitions: an exit, a succession, an owner stepping back. A transition built on rented capability is not a transition. Decision sovereignty has to survive AVP’s departure, or the work has failed.

The manuals are the proof: they are written so the team can maintain the record and its tools without AVP in the room.

How an engagement runs

Diligence maps it, the architecture holds it, the continuity engagement runs it. One system, owned by the business it serves.

Book the first conversation →

Thirty minutes, no preparation needed. Or write to hello@ascensionvp.com