Why revenue share aligns incentives the way classic SaaS can't

Fast answer

Classic SaaS pricing decouples the vendor's revenue from the customer's outcome. Once the customer signs the annual contract, the vendor's incentive is to minimise support cost and maximise retention — not to make the customer succeed. Revenue share inverts this: CommonWealth Ops earns the EUR 49 floor regardless of the customer's results, but the 20% of net profit means we earn more when the customer earns more and nothing extra in a month they don't profit. The model is a structural commitment, not a marketing claim.

What the classic SaaS incentive actually optimises for

A flat-fee SaaS company sells access for a fixed monthly or annual price. Once the customer is signed and onboarded, the vendor's economic objective function looks like this:

• Maximise retention: a customer who cancels is a permanent revenue loss. The vendor wants the customer to stay subscribed even if the product is not currently producing value.
• Minimise support cost: every minute of human time spent on a customer is margin destruction. The vendor wants the product to feel "self-serve" so that customer questions are not the vendor's problem.
• Upsell at renewal: the most reliable revenue growth comes from existing customers, not from new ones. The vendor wants to expand the surface area of the contract, not necessarily to make the contract more valuable per dollar.

Notice what is NOT in this list: making the customer's business more profitable. That outcome is a NICE-TO-HAVE for the vendor because a profitable customer is more likely to renew. But it is not the FIRST-ORDER objective. The first-order objective is renewal, regardless of whether the customer is profitable.

For most software categories, this misalignment is mild. A CRM, an accounting tool, a project tracker — these are utilities. Their value to the customer compounds slowly, the cost of switching is high, and the vendor's incentive to "just keep the customer signed up" is mostly aligned with the customer's interest in not having to migrate.

For an operator that runs your commerce, the misalignment would be severe.

Why operating commerce breaks the flat-fee model

Operating a commerce business has a feature that most SaaS categories do not have: the value is HIGHLY VARIABLE month to month. A skincare operator whose store, creative, and campaigns are run on the dominant hook of week 12 might 5x their ad-spend efficiency that month. The same operator three months later might find the niche has gone sideways and no actionable signal emerges for 4 weeks.

A flat-fee tool charges the same price during the 5x month and the sideways month. The operator pays even when nothing is being produced. The vendor's incentive is to KEEP the operator subscribed during the sideways months — typically through dashboard gamification, vanity metrics, and "your data this week" emails that imply utility without delivering it.

The operator's correct move during a dead stretch is to stop paying for what isn't working. The flat-fee vendor's correct move is to prevent that. The interests are NOT aligned.

How the revenue share model inverts it

CommonWealth Ops charges EUR 49 per month as a base — covering the intelligence layer (the KobiiSpy pipeline, continuous Meta + TikTok surveillance) and minimal product support. The base is small enough that the operator does not feel they are paying for nothing during a sideways month.

The 20% of net profit kicks in only when the operator's business is producing real returns. During the 5x month, the operator owes more. During the sideways month — and any month with no net profit — they owe only the EUR 49.

The vendor's incentive shape changes:

• During growth months: vendor revenue grows with the customer. The vendor's interest is in making the growth larger. The roadmap will prioritise what ACTUALLY increases customer profit, because it shows up in our revenue.
• During sideways months: vendor revenue is the EUR 49 floor. The vendor would prefer the customer have a growth month next month — and the only path to that is operating better. Sideways months are a feedback loop into priority.
• During disaster months: vendor still earns EUR 49. Operator owes nothing extra. The model carries some of the volatility on the vendor's side, which is the whole point.

This is not philanthropy. The vendor still earns the EUR 49 floor across all customers regardless of their state, which covers the base cost of running the service. The 20% upside is what makes the model SCALE attractively for the vendor — when our top decile of customers grows, our revenue concentrates among the customers we are operating most successfully. That is the correct concentration. A flat-fee vendor's revenue is uncorrelated with which customers actually succeeded.

What this means for product decisions

Concrete examples of decisions the revenue share model has already shaped:

• One rate, no price tiers. Every operator pays the same 20%; the tier (Creator, Emerging, Established, Advanced) changes how much CW Ops operates, never the percentage. A flat-fee competitor would add price tiers ("Pro", "Enterprise") because tier expansion is the cleanest way to grow revenue per customer. We do not, because the 20% of net profit already grows revenue per customer when the customer grows.
• No "annual contract discount" locking the customer in for 12 months. A flat-fee vendor benefits from annual locks because it caps churn variance. We do not need to cap churn variance because our exposure to a low-quality customer is asymmetric: they pay only EUR 49 if they are not profitable.
• The 30-day money-back guarantee. A flat-fee vendor cannot afford this generously because their margin per customer is too thin. We can afford it because the customers who would abuse a money-back guarantee are the same customers who would have been EUR 49-only under our model anyway.

These are not marketing decisions. They are structural decisions that the revenue share model makes economically rational. A flat-fee vendor trying to copy these features would lose money. We do not lose money, because the 20% from our profitable customers covers the floor of our struggling customers.

What this does NOT solve

The model is honest, not magical. Three things it does not fix:

• Selection difficulty: we still have to acquire customers who CAN become profitable. Acquiring customers who never profit leaves us with the EUR 49 floor only, which does not cover acquisition cost for low-fit customers. Targeting matters.
• Volatility for the vendor: our revenue is more variable month to month than a flat-fee competitor's. We accept this because the EXPECTED revenue is higher for the customers we are aligned with.
• The trust requirement: product and shipping costs are operator-declared. If operators systematically misrepresent the numbers, the model breaks. We mitigate this by reading gross revenue directly from Shopify and by selecting for operators who can read their own P&L; for those operators, the cost of misrepresentation (broken trust, cancelled account) is higher than the upside of underpaying by a small amount.

The honest framing

Classic SaaS earned its dominance because it produced predictable revenue for vendors and predictable cost for customers. That predictability is valuable. It is also, when the vendor is actually operating your commerce, the source of the misalignment.

Revenue share is not better in every category. For a CRM or an accounting tool, it would be worse — the value is too steady to warrant a variable share. For an operator that runs the commerce — where the value compounds in spikes and disappears for weeks at a time — a share of net profit is the structural match.

If your business is profitable, our pricing page walks the maths: EUR 49 base plus 20% of net profit, EUR 0 share in any month you don't profit. If you are not yet profitable, the model still works for you — you pay only EUR 49 — and the 10-minute Meta Ad Library workflow is enough for your stage. The 20% is an operating-partner share, not a tool fee: it is the price of having CW Ops run the commerce, and it stops the moment you cancel.