An approved shell with nothing inside it.

The brand was a software-as-a-service business selling an analytics and user-behaviour product on a freemium model. Its partner programme had been created and approved, but every substantive element a publisher would evaluate before promoting it was empty. The dashboard reported zero clicks, zero transactions, zero sales value and zero partners, and the programme health index could not yet be calculated. The programme was at the very start of its setup journey with a launch date pencilled in weeks away.

The overall verdict was that the programme was passive — not through neglect of a live operation, but because it had not yet been built. The opportunity being lost was not commission waste or fraud; it was time. Every week the profile, terms, tracking, creative and commercial offer remained unset was a week the programme could not recruit, activate or convert. The biggest single risk was that the programme launched half-built. Partners invited into an empty profile with no creative, no clear commission story and unverified tracking do not activate — and first impressions in affiliate marketing are unusually difficult to reverse, because a publisher who has evaluated a programme once rarely evaluates it again.

Three issues stood above the rest.

Commission economics. The default rate of 4% is appropriate for low-margin physical retail, not for software, where partner commissions typically run 20–30%. The freemium model made this worse rather than better, because the commissionable action — a paid subscription versus a free sign-up — had never been deliberately defined. As configured, the programme could not attract serious content, review or comparison partners, because the reward did not reflect the category and nobody could say what triggered it.

Launch readiness. Profile, terms and website tracking are the three formal setup tasks the platform itself flags. All three were incomplete. Until they were done the programme could not credibly go live at all.

Account funding. The account carried a payment level warning: credit limit exceeded, no direct debit in place. Harmless while dormant, but a live programme that is unfunded can have its tracking links taken offline, so it had to be resolved before launch rather than after it.

There were quieter but important gaps. The programme was configured to the wrong market entirely, with pricing shown in the wrong currency, while the brief described a different target market; market, currency and region settings needed reconciling before any recruitment. The sector was unset, which meant publishers browsing the platform by category could not find the programme at all — a complete invisibility that no amount of recruitment effort compensates for. There was no creative of any kind, so even a willing partner had nothing to place. There was no product or plan feed, which removes the natural route for comparison and review partners — exactly the partner types that perform well for a developer and marketing tool. And there was no communication, no welcome email and no triggered messaging, so any partner who did join would receive only the platform’s generic default note and then silence.

The programme was losing opportunity overwhelmingly through setup and activation readiness, followed by commission and partner mix. It was not losing money through leakage, fraud or over-payment, because there was no spend yet. This is the most favourable position from which to run an audit: nothing has to be unwound, and a clean, correct launch can be designed from the first day rather than retrofitted around mistakes.

The good news is structural. Because the programme was pre-launch, there was no legacy damage to repair, no mis-set commission to claw back and no partner relationships to rescue. A focused two-to-three week build — profile and sector, terms, verified tracking, a software-appropriate commission structure with a defined conversion event, a starter creative and deep-link set, a real welcome email, and resolved account funding — would take the programme from an empty shell to a credible, recruit-ready channel in time for the planned launch.

2A. Metric scorecard

A pre-launch programme scores badly on almost everything by definition. The value of the scorecard here is not the score but the checklist: it is the complete list of what has to exist before a programme can credibly invite its first partner. Benchmarks are AME Reference Library values for the software and SaaS sub-sector and are not client data.

2B. Area scorecard

For a programme at this stage, genuine strengths are necessarily foundational rather than performance-based. Several were real and worth protecting through the build.

A clean slate with no legacy damage. This is the strength that shapes the entire audit. There is no mis-set commission to claw back under notice rules, no partner relationship damaged by late payment or broken tracking, no fraudulent publisher embedded in the base, and no concentration to unwind. Every other audit in this library spends its first thirty days undoing something. This one could simply build correctly the first time, which is both cheaper and considerably faster.

Sensible attribution and validation windows already set. The thirty-day cookie is on benchmark, and the auto-validation period sits slightly longer than typical — which for a subscription product is protective rather than sloppy, since it gives refunds and immediate cancellations time to surface before commission is validated. These were correctly configured before anyone thought to configure anything else, and they should be left alone.

A clean, functional product site. The homepage was well built and clearly communicated the product. For a technical product sold to a technical buyer, that clarity matters more than polish. The gap is not the page’s quality; it is that it was the only destination configured, with no trial-specific, plan-specific or affiliate-specific landing experience behind it.

A product category that suits affiliate distribution unusually well. Analytics and productivity software is bought by people who research it — who read comparison articles, watch walkthroughs and ask communities before they trial anything. That behaviour maps precisely onto content, review and comparison partners, which means the programme did not need to invent demand or educate a market. It needed to show up where the research was already happening, and that is a considerably easier problem than most of the programmes in this library face.

A freemium model that makes trial frictionless. Freemium is a complication for commission design, as the next sections set out at length. It is also a genuine advantage for partner recruitment: a partner recommending a free trial asks far less of their audience than one recommending a purchase, which materially raises the conversion rate on their placement. The task is to define the commissionable event properly so the model becomes an asset rather than an ambiguity.

5.1 Overview

The programme had zero partners, plus two platform default test accounts. There is no mix to assess, no concentration to measure, no device performance to analyse and no approval queue to process.

That sounds like an empty section. It is actually the most valuable one in this audit, because the programme was in the rare position of being able to choose its partner mix rather than inherit one. Every other audit in this library is trying to unwind a mix that assembled itself badly. This one could design the right mix and recruit against it deliberately.

5.2 Target type distribution

The distribution above is a recruitment specification rather than an analysis, and one point in it is worth stating plainly. In this category, coupon and deal partners are not merely low-value; they are the wrong shape entirely. Nobody buys business software from a coupon site. Buyers of an analytics or productivity tool arrive through research — they read comparisons, they watch walkthroughs, they ask a community they already trust. The partner types that matter are the ones whose opinion the buyer already pays attention to, and those partners are recruited individually rather than acquired in bulk.

The single most under-exploited type is the last two rows: consultants, agencies and existing customers. In B2B software these frequently outperform every other partner type, because they combine genuine product knowledge with an existing trusted relationship. They are also almost never found through a marketplace — they come through the product’s own website, and the website had no partner sign-up route at all.

5.3 Concentration

No concentration exists and none can yet be measured. The forward-looking discipline is to avoid recreating the standard problem: a programme that recruits opportunistically tends to end up with two or three partners carrying most of its revenue within a year. Recruiting deliberately across review, community, consultant and content types from the first month is how that is prevented, and it is far cheaper than diluting concentration later.

5.4 Device performance

Not measurable with no transactions. The relevant forward-looking note for this category is that the purchase journey routinely spans devices and sessions over weeks — a buyer discovers on mobile, evaluates on desktop, and involves colleagues before a decision. That makes the thirty-day attribution window a genuine minimum rather than a generous setting, and it makes the absence of assist logic a real constraint rather than a refinement.

5.5 Pending approvals

No applications were pending, because the programme was not discoverable. With no sector set, the programme did not appear in category browsing at all, so no publisher could have found it to apply. That is worth recording as the explanation rather than treating an empty queue as a neutral fact.

With no partners in the programme, the matrix is forward-looking. Each row is a target type with the prerequisite that must exist before that type can be approached productively — which is the point of running the audit before launch rather than after it.

There were no partners and therefore no relationship management, no contact history and no top-partner plan. What mattered at this stage was designing the model the programme would operate once partners existed, so that the first cohort is managed properly from day one rather than retrofitted into a structure invented later.

The B2B difference. Relationship management in this category looks materially different from retail. A retail programme manages dozens or hundreds of partners largely through segmentation and automation. A B2B software programme with a high average contract value and a long sales cycle is typically carried by a much smaller number of partners, each of which warrants individual attention. That changes the shape of the plan: fewer partners, deeper relationships, more direct contact, and materially more support per partner.

What each partner needs. A review or comparison partner needs current plan and feature data, screenshots, and early notice of product changes so their article does not go stale. A consultant or agency partner needs enablement — a technical overview, a demo environment, and a route to ask questions. A community partner needs a trial mechanic they can point at without it feeling like an advertisement. None of these are newsletter recipients; all of them are relationships.

Cadence to establish at launch. Monthly individual contact with every active partner while the base is small — which it will be for some time, and that is appropriate rather than a failing. Quarterly reviews once revenue exists. Product update briefings ahead of any release that changes what a partner has written about. And a named contact, published in the profile and the welcome email, because in a considered category the ability to ask a real question is itself a reason to choose one programme over another.

What to log from the first day. Contact history, article and placement locations, and product-knowledge level per partner. This costs almost nothing to maintain from the start and is very difficult to reconstruct later.

Recruitment had not started. Partner discovery and marketplace tooling were available and entirely unused, with zero invitations issued and no recruited partners.

Two prerequisites before any invitation goes out. First, the programme has to be worth evaluating — profile complete, sector set, creative available, commission competitive and its conversion event defined. Inviting partners into an empty profile is the single most damaging thing this programme could do, because a publisher who evaluates a programme once and finds nothing rarely returns. Second, the market and currency settings must be corrected, or discovery filtering will surface partners in the wrong market entirely.

The channel that matters most. In B2B software the highest-value partners are frequently not on any marketplace. They are consultants and agencies already implementing the product for clients, existing customers with a professional audience, and community operators whose members ask for recommendations. These partners come through the product’s own website, not through a platform search — and the website carried no partner programme page and no sign-up route at all. That is the single cheapest and highest-quality recruitment channel available to this programme, and it was closed.

Outbound targeting once the gates are cleared. Identify the titles already ranking for category comparison and alternative-to searches, because those partners already have the audience at the exact evaluation moment. Identify the communities where buyers in this category ask for recommendations, and approach the operators rather than posting into them. Identify agencies and consultancies working with comparable tools. In every case the approach should be individual and should lead with the recurring commission structure, because that is the differentiator that changes a review site’s economics.

What not to recruit. Coupon, deal and sub-network partners have no place in this programme and should be excluded by policy in the terms rather than declined case by case. They will apply once the sector is set and the programme becomes visible; having the policy written first saves the argument.

9.1 Current state

The programme ran a single commission group: a flat 4% one-off percentage on sale, applied to everyone. There were no tiers, no differentiation by partner type, no bonus rules and no value-based rules. The commissionable action was never defined against the product’s freemium model.

Three separate problems sit inside that one line of configuration.

The rate is wrong for the category. Four per cent is a physical retail rate. Software partner programmes typically run 20–30%, and they can, because software margins support it. A review or comparison partner assessing programmes filters on rate first, and at 4% this programme does not survive the filter. That is not a matter of the partner being greedy; it is that the effort of writing a credible technical comparison is fixed regardless of the rate, so a rate a fifth of the category norm makes the work uneconomic.

The conversion event is undefined. The product sold on a freemium model. Nothing in the account or the terms stated whether a free sign-up, a trial start or a paid subscription triggered commission. A partner cannot assess a programme whose payout trigger nobody has decided, and a programme that has not decided cannot brief a partner, cannot forecast, and cannot defend its own commission spend internally.

The model is one-off. This is the deepest of the three and the least often noticed. A one-off bounty asks a review site to spend its credibility once, on a single placement, for a single payment. Recurring commission on subscription revenue turns that same placement into an annuity: the partner is paid for as long as the customer stays, which aligns the partner’s interest with retention rather than just acquisition, and makes the placement worth maintaining and updating rather than publishing and forgetting. For a subscription product, moving from a bounty to recurring commission is not a rate adjustment. It is a change in what the programme is asking partners to do.

9.2 Recommended architecture

9.3 Budget impact

With no revenue there is no current commission spend, so the restructure costs nothing today. Setting it correctly before launch is materially cheaper than changing it afterwards, because commission reductions require notice and damage partner trust in a way increases never repair.

The apparent cost increase — from 4% one-off to a recurring rate several times higher — is not the right comparison. The right comparison is against customer acquisition cost through the alternative channel, which in this category is paid search against competitors bidding identical terms and rising every quarter. A recurring partner commission is paid only on customers who actually convert and only for as long as they stay, which makes it a fundamentally safer acquisition cost than a paid click that may convert to nothing.

The recurring term is the lever that keeps this defensible. It should be long enough that a partner genuinely experiences it as an annuity worth maintaining, and bounded enough that total commission remains a sensible proportion of customer lifetime value. Setting that term requires the brand’s own lifetime value data, which is the single external input this section depends on.

The client document carries each task with fifteen columns. The fields are laid out here as a card because fifteen columns is unreadable on any screen. No field has been dropped in the transform.

Day 0–30: build and launch

For a pre-launch programme the thirty-day plan is the build. The ordering matters: configuration and funding first because they are fast and block everything, then the commercial structure, then the assets, then launch. Recruitment is deliberately last, because inviting partners into an incomplete programme is the one mistake this audit is most concerned to prevent.

Day 31–60: recruit and enable

Day 61–90: scale

On B2B seasonality. This category does not follow a retail calendar. The predictable soft periods are the December budget freeze and the spring renewal pause, and both are structural rather than signs of a failing programme. Planning for them prevents the standard mistake of reading a normal B2B trough as a partner quality problem and reacting to it.

12.1 Standing cadence

12.2 Calendar moments

This category has a calendar, but it is a budget calendar rather than a retail one. Two of the moments below are not campaigns at all — they are predictable troughs that should be anticipated rather than fought. Reading a December budget freeze as a partner performance problem, and reacting to it, is one of the more common and more expensive mistakes in B2B programme management.

No — and launching it in this state would have been worse than delaying. The programme was an approved shell. Profile empty, terms unwritten, tracking unverified, creative non-existent, commission set at a retail rate with an undefined trigger, and the account carrying a funding warning that could take its links offline. A programme that invites partners into that finds out very quickly that first impressions in this industry do not get a second attempt.

What held it back. Time, and one commercial decision. The setup gaps were all straightforward and mostly fast — a sector takes thirty seconds to set, a profile takes an afternoon, tracking takes a test transaction. The decision that actually required thought was the commission model, and it was the one nobody had made: whether to pay a one-off bounty or a recurring share, and what event triggers payment against a freemium product where a free sign-up and a paying customer are very different things.

Why the commission model is most of the answer. A one-off payment asks a review site to spend its credibility once, on one placement, for one payment. Recurring commission on subscription revenue turns that same placement into an annuity — the partner is paid for as long as the customer stays, which makes the placement worth maintaining and updating rather than publishing and forgetting, and aligns the partner with retention rather than just acquisition. In a category where the good partners are selective about what they endorse, that is not a rate adjustment. It is the difference between a programme they consider and a programme they ignore.

The first five tasks, and why that order. One: set the sector, because until it is set the programme does not exist in category browsing at all and it takes thirty seconds. Two: reconcile market, region and currency, because every recruitment decision downstream inherits the error. Three: resolve the funding warning, because a live programme with unfunded links can go dark during its launch window. Four: restructure commission to recurring with a defined conversion event, because it is the decision that determines whether recruitment can succeed at all. Five: complete profile, terms and tracking verification together, because they are the platform’s own definition of a launchable programme.

What the brand should not do yet. No partner invitations until the profile, creative and commission structure are complete — inviting partners into an empty programme is the single most damaging available action, and it is also the most tempting, because recruitment feels like progress. No coupon, deal or sub-network recruitment at any point; exclude them by policy in the terms rather than declining them individually later. And no paid marketplace placements before the programme has proven it converts.

What to review in 30 days. Are all three formal setup tasks closed? Is the sector set and the programme visible in category browsing? Are market and currency aligned? Is the funding warning cleared? Is commission recurring with a defined conversion event stated identically in the configuration and the terms? Has a test transaction passed end to end?

What requires external evidence before a final conclusion. The brand’s customer lifetime value and margin data are needed before the recurring commission term can be set defensibly — too short and it is not an annuity, too long and it is indefensible. Structured plan and feature data are needed for the feed. A partner-suitable technical overview is needed before review and comparison partners can be recruited productively. And a definitive answer on the target market is needed before the region and currency settings can be corrected.