Implementation Partner Standards

Revenue Machine does not execute implementation.

Revenue Machine does not work for implementation partners.

Revenue Machine conducts independent Executive Growth Reviews that help founders determine whether their business can responsibly carry its next growth investment. The Review produces a Verdict and a written Executive Growth Brief. That is the product.

Implementation partners do not commission Reviews, do not fund them, and do not influence them. No conclusion reached in a Review is shaped by the solution that may follow it.

This section describes the position implementation partners occupy. It is set out here because it explains why independence has value — not because Revenue Machine exists to solve it.

The expensive failures in implementation are not slow starts.

They are engagements that should not have begun. Capacity committed to founders who were never going to proceed. Work scoped against a problem that turned out not to be the constraint. Each of these costs a firm considerably more than the discovery time it spends at the outset.

There is also a structural limit that no amount of skill resolves. An implementation partner can assess a founder's readiness accurately. What an implementation partner cannot do is be believed while doing it — because the founder knows who profits from the answer.

That is not a failure of judgement. It is a condition of the position.

When the party who would perform the work also declares the work necessary, the founder discounts the conclusion. Not because it is wrong, but because it cannot be separated from the interest of the party reaching it.

Revenue Machine occupies the only position from which that separation is possible. It does not execute implementation, does not sell it, and earns nothing from any recommendation to pursue it.

This is not a capability an implementation firm can build internally. It is a position a firm that executes cannot hold, at any price.

What that produces is not a document. It is a founder who believes their own diagnosis — and who therefore proceeds, or declines to proceed, for reasons they can defend to themselves.

• —Revenue Machine does not replace a partner's qualification process. Partners qualify their own clients.
• —Revenue Machine does not generate volume. It does not exist to increase the number of founders reaching implementation.
• —Revenue Machine does not guarantee that any introduced founder is suitable. It documents evidence. The partner decides.
• —Revenue Machine does not accept partner influence over any diagnosis. No partner reviews, previews, or comments on a Verdict before the founder receives it.
• —Revenue Machine does not introduce founders whose evidence does not support implementation.
• —Revenue Machine does not disclose a founder's Executive Growth Brief to any partner without the founder's written consent.

One rule governs every recommendation.

The partner must fit the founder's diagnosis. The diagnosis is never fitted to the partner.

Recommendations follow evidence. Not relationships. Not commercial arrangements. Not the composition of the ecosystem at the time the Review is conducted.

Where the evidence identifies a constraint that no admitted partner addresses, no partner is recommended. The absence of a suitable partner is not a reason to recommend an unsuitable one.

Revenue Machine does not recruit implementation partners.

Admission is not offered in exchange for volume, fees, or reciprocal referrals. No partner has purchased entry to the Executive Growth Ecosystem, and none can.

Partners do not participate because Revenue Machine produces more founders. It does not. They participate because an independent diagnosis allows implementation to begin from a defined problem — and because that clarity reaches them only when a founder brings it with them.

A partner is admitted when their inclusion strengthens the standard by which recommendations are made. That requires:

• —demonstrated competence against a defined constraint, rather than general capability
• —a willingness to decline work that falls outside it
• —qualification standards of their own, enforced
• —accountability for outcomes, measured and reported
• —written acceptance of these terms

The requirement most firms do not meet is the second. A partner who accepts every engagement cannot be recommended against a specific constraint, because their acceptance carries no information about fit.

Selectivity here is not a matter of prestige. A standard that admits every capable firm stops being a standard, and a recommendation drawn from an unselective roster tells a founder nothing.

No introduction is made unless the founder has completed an Executive Growth Review and given written consent.

Where both conditions are met, the founder brings with them:

• —the completed Executive Growth Review
• —the Business Architecture analysis underlying it
• —the documented primary business constraint
• —the Executive Growth Verdict
• —the written Executive Growth Brief
• —their own understanding of why the recommended path fits their business

These belong to the founder. Revenue Machine does not transmit them independently of the founder's decision, retains no right to share them, and provides them to no partner the founder has not agreed to meet.

A founder may decline an introduction and keep all of it. The value of the Review does not depend on implementation following it.

No introduction is made where:

• —the evidence does not support the investment under consideration
• —the primary constraint lies outside the competence of any admitted partner
• —the business should be strengthened before implementation begins
• —no partner is appropriate

These founders receive the same Review, the same Verdict, and the same written Brief. What they do not receive is an introduction — because an introduction that is not warranted transfers cost to both parties: to the founder in capital and time, to the partner in capacity and outcome.

An ecosystem that introduces everyone tells a partner nothing about who is arriving.

Participation is conditional and continuing.

A partner is removed where:

• —outcomes repeatedly do not hold against the diagnosis on which introductions were made
• —any attempt is made to influence a diagnosis, before or after it is issued
• —engagements are consistently scoped away from the diagnosed constraint
• —the partner's own qualification standards lapse

Removal follows evidence, on the same basis as every other decision recorded here. Relationship duration, introduction volume, and commercial arrangement are not considerations.

A standard that cannot remove a participant is a description, not a standard.

Revenue Machine establishes what the problem is. Implementation partners determine how it is solved. The second question is not the lesser one, and Revenue Machine does not answer it.

A Review establishes a constraint and the evidence supporting it. It does not specify approach, sequence, tooling, creative, channel strategy, or execution. Those remain entirely the partner's domain.

What changes is where the conversation begins.

A founder who has completed a Review has already examined their own business, named its primary constraint, and reached a view on whether investment is warranted. They did that work for themselves, and it belongs to them. The partner benefits from it incidentally, because the founder brings it into the room.

This does not replace discovery.

Partners conduct their own, and should. It begins further in, and against a defined problem rather than an open one. The founder explains their business once rather than repeatedly. The partner begins from shared understanding rather than rediscovery.

Implementation does not begin faster. It begins with greater clarity.

Partners admitted to the Executive Growth Ecosystem accept that

• —the diagnosis is independent and not subject to their input
• —not every founder will be introduced, and no volume is implied or owed
• —the accuracy of each diagnosis will be reported back honestly, including where it proved wrong
• —where the founder's interest and the engagement's interest conflict, the founder's governs
• —these terms are accepted in writing before any introduction is made

Revenue Machine commits that

• —no founder will be introduced whom Revenue Machine would not stake its own judgement on
• —every recommendation will be accompanied by the evidence supporting it
• —partners will be told when a diagnosis proved wrong, not only when it held
• —no partner's commercial interest will influence a Verdict
• —no one at Revenue Machine is measured on the number of introductions made

The last commitment is the mechanism behind all the others. Where introductions are a target, they become something to produce. They are not a target here.

The following describes what Revenue Machine intends to build. None of it is in place today.

• —a standardized Executive Growth Brief format, consistent across every Review
• —consistent diagnostic language, so that a named constraint means the same thing in every Brief
• —a structured handoff protocol at the point of introduction
• —a record of diagnostic accuracy, measured against implementation outcomes over time
• —continuous refinement of the Business Architecture methodology from that record

These are commitments Revenue Machine makes about its own operations. None describes future partner conduct.

This section records the present position and is revised with each version of this document.

• —Admitted partners: GrowRev, Vavoza, eStage.
• —Active ecosystem branches: Customer Acquisition, Business Systems & Infrastructure, Executive Resources. A further 5 branches are in development and are not represented by admitted partners.
• —Executive Growth Reviews are beginning. No implementation outcomes have yet been measured.
• —No record of diagnostic accuracy exists.
• —The feedback loop described in section 11 is not yet operational.

All credentials, metrics and outcomes attributed to partners elsewhere on this site belong to those partners. Revenue Machine does not claim them.

This document sets out the standard that governs participation. It does not describe an operating history, because there is not yet one to describe. Where evidence exists, it will be published. Where it does not, this section will say so.