Ascension Venture Partners
00 Engagement

Thirty minutes to find out whether your business can run without you.

One call with Alexander. You leave with an honest read: worth doing, not worth doing, or not yet.

I’m not technical.

You do not need to be. The manuals are written for the team you have.

We’re too small for this.

The smallest engagement is a fixed-scope audit. Most clients are five to fifty people.

I don’t have time for a big project.

The first stage takes weeks and runs alongside trading. It stops there if that is the right answer.


AVP works with.

Owners of operations-heavy businesses at a point of transition: preparing for an acquisition or exit, handing the business to a successor, or stepping back from day-to-day operations. The common thread is a business whose working knowledge sits in one or two heads and needs to sit in infrastructure the business owns. Businesses outside that shape are told so directly.

01
How the work runs

Three stages, always in this order.

Diagnosis, deployment, operating layer.

Every engagement climbs the same three stages in the same order. The order is not negotiable: building before diagnosing produces infrastructure nobody uses, and a corpus with no operating layer around it decays into a document.

Diagnosis

The audit comes first.

No engagement starts with building. It starts with an audit of where the business’s knowledge actually lives, which decisions route through the owner, and what would break in the owner’s absence. The audit produces a map: everything the business knows that needs writing down, what the team needs in order to use it, and the order to build them in. We call the first the corpus and the second its readers. The map is the business’s to keep, and an owner can stop there.

Deployment

Then the corpus is built.

Against the map, the corpus is built and the readers are deployed on top of it: the working interfaces the team queries as part of daily work. The written instructions for keeping all of it current are the manuals, and they are produced alongside, so the team can maintain and extend both without AVP present. Everything runs on the business’s own accounts and infrastructure and is owned outright.

Operating layer

Then AVP stays embedded while it becomes the way the business runs.

The retained phase. Commercial and technical support embedded alongside the team while the corpus is maintained and extended, the readers grow with the operation, and the manuals stay current. This is where the transition actually happens, against working infrastructure rather than a plan. It ends when the team runs the system without AVP.

Engagements are retained. A business can stop after any stage and keeps everything produced up to that point: the map, the corpus, the readers, the manuals. All of it is owned outright and runs on the business’s own infrastructure, so nothing switches off when the engagement ends.


02
Book a call

Take a time in the calendar, or send four fields first.

Book a time, or write first.

Roughly where the business sits. The two profiles AVP works with most are the newer business building toward an exit and the established owner-led business handing over.

The transition behind the enquiry. If there isn’t one yet, say so. It changes the conversation rather than ending it.

One line on who currently holds what the business knows, and what would be hard to replace. This is the substance of the first conversation.

Honest answers help calibrate the call. Longer horizons are welcome and are treated differently, not deprioritised.

Reviewed same day. You will hear back with a time, a referral, or a straight no. Never a sales sequence. To skip the form, write to hello@ascensionvp.com.

03
The first conversation

Thirty minutes with Alexander Rennie. One honest read. No chasing.

What the first call is.

Thirty minutes on video with Alexander Rennie. No one junior. The first ten minutes cover the business and what is driving the change. The next fifteen work through where the knowledge sits today, which decisions still go through the owner, and what a corpus built against this operation would have to hold. The last five are an honest read: worth doing, not worth doing, or not yet.

Worth doing means AVP scopes the audit and sends the shape of it within a few days. Not worth doing means the business does not need this, said plainly, with a referral where there is a better fit. Not yet means the work is right but the timing is not. AVP comes back to it when the owner says so, not on a follow-up sequence.

The call is not a pitch. No discovery sequence, no multi-stage qualification, no chasing afterwards. One conversation, one read, and the decision is yours.

Thirty minutes is enough to tell whether this fits.