A strategist, funnel builder, or operations partner can be paid by the project, by the month, by time, or partly by commercial results. None of those labels makes an arrangement fair by itself. Start by defining what the fee covers, which outcomes the operator can influence, and whether both parties can reproduce the calculation.
An expert may contribute subject knowledge and a public reputation while an operator builds or runs systems around a course, membership, or service. The work can include planning, implementation, launch, and ongoing operations, but sales also depend on factors the operator cannot control. Choose compensation that reflects each person’s responsibilities and influence; the word “alignment” does not settle the question.
Start with three questions
Before comparing fee models, describe the engagement in plain language:
- Can the work be scoped? List the deliverables, dependencies, review rounds, exclusions, and what counts as acceptance. A known build is easier to price as a project than an open-ended promise to “grow the business.”
- Who controls the outcome? Separate the operator’s work (for example, working pages, tested checkout, or delivered campaigns) from results affected by the expert, the offer, traffic, audience demand, pricing, and customer service.
- Can the result be measured and attributed? Identify the data source, baseline, time window, refunds, existing customers, discounts, and any other inputs that change the calculation. If the parties cannot reproduce the number, a result-based fee is likely to become a dispute about the number.
Use these tests to expose the trade-offs before either party commits; the answers should reflect the engagement rather than a generic rate card.
Six common ways to structure the fee
Fixed project fee
The client pays an agreed amount for a defined piece of work: a funnel build, migration, launch package, or course setup. It gives both sides a known price when scope and acceptance criteria are specific.
The operator takes on estimation and delivery risk: if the work takes longer than expected, the agreed fee does not automatically rise. The client still carries market risk because the fee is owed even if the offer does not sell. Write down assumptions, client-supplied materials, change requests, payment milestones, and what happens when a dependency is late. A fixed fee without a change process can turn scope expansion into an argument over what “finished” meant.
Time-based billing
An hourly or daily rate fits discovery, troubleshooting, or work whose scope is still uncertain. The client pays for time used; the operator does not have to guess a fixed price before the problem is understood.
This structure makes the budget less predictable for the client and can make the operator’s income depend on hours rather than the value of a faster solution. Set an estimate or cap, agree how time is recorded, and decide who can authorize work beyond it. A short paid diagnostic can sometimes create enough information to price a later project more clearly.
Monthly retainer
A retainer reserves a defined level of access, capacity, or recurring work. It can suit monitoring, campaign operations, maintenance, and agreed optimization. The word alone does not tell the client what is included: specify deliverables, response times, meeting cadence, unused capacity, and the process for urgent requests.
A monthly payment can simplify budgeting, but it does not prove that the relationship is producing value. A short review cycle should connect the fee to the work completed, decisions made, issues handled, and next priorities. Avoid an unlimited “all you need” promise unless both sides have agreed how capacity is managed.
Milestone payments
A project fee can be divided around verifiable checkpoints such as kickoff, architecture approval, build completion, and handover. Milestones reduce the amount either party has to carry at once and give the client regular checkpoints.
Use acceptance criteria the operator can actually meet. “Deliver the approved checkout flow and test the agreed payment paths” is more testable than “make the launch successful.” For each checkpoint, specify the review period, what counts as acceptance, and how revisions are handled.
Performance bonus
A bonus adds variable compensation to a base fee when a defined result is reached. It can reward a contribution beyond delivery, but the chosen metric shapes behavior. A bonus tied only to registrations, for instance, may reward volume even when the registrations are poorly matched to the offer.
Prefer a measure the operator can materially influence, pair it with a quality guardrail, and define the data source in advance. In one study of performance-based contracts for Dutch employment services, a stronger link between payment and outcomes increased placements for more readily employable participants, but did not increase job duration. That study concerns a specific public-service setting; it does not predict results for course businesses. It does illustrate why the measured target and the broader outcome should not be treated as interchangeable. (Koning and Heinrich, “Cream-Skimming, Parking and Other Intended and Unintended Effects of High-Powered, Performance-Based Contracts”)
Revenue share or a hybrid
A revenue share pays a defined portion of eligible receipts; a hybrid combines a base fee with a variable component. These can make sense when the operator remains involved in commercial execution and the parties can track the relevant sales. They also transfer more market and measurement risk to the operator.
Before agreeing, define whether the percentage applies to gross or net receipts; which products, channels, and customers count; treatment of taxes, refunds, chargebacks, discounts, and payment fees; attribution windows; reporting access; payment dates; and the end date. Specify whether the share continues on sales after termination and how existing customers or renewals are handled. “A percentage of revenue” is not a complete formula.
A hybrid can reduce the pressure of a pure revenue share by paying for a portion of the operator’s capacity while reserving a smaller share for an agreed result. It is not automatically the fairest option: the base and variable components can still be unclear, and the operator may have little influence over the factors that move sales.
Where result-based pay becomes fragile
The operator may build the pages, tracking, and follow-up sequence, while the expert controls the offer, expertise, audience relationship, pricing, and much of the customer experience. Traffic may come from several campaigns or channels. A buyer may have encountered the expert long before a tracked click. These realities make attribution a governance problem as much as a marketing problem.
A result-based arrangement becomes harder to defend when one side controls the records, the baseline is missing, or the metric can improve while customer value declines. The broader performance-contracting literature has examined unintended effects of tying compensation closely to measured outcomes, but findings from public programs should not be generalized directly to digital businesses. The practical lesson is narrower: check that the measure represents the result both partners actually care about, and look for ways it could be improved at the expense of quality.
Do not make sales the only measure if the operator is responsible for a defined system. Depending on the engagement, the parties might separately track delivery milestones, checkout completion, qualified leads, or a post-purchase quality signal. These measures are useful only when they are defined, accessible, and connected to the work. A dashboard is not proof of causation.
A short selection process
Use the following sequence during a proposal conversation:
- Describe the work. If deliverables and acceptance are clear, price the project or its milestones. If the work is recurring, define a retainer around capacity and responsibilities. If scope is unknown, begin with a time-limited discovery engagement.
- Map control. Put each key outcome beside the person who can influence it. Keep the base fee anchored to work the operator is expected to perform. Add variable pay only where the operator has a meaningful role and the parties accept the remaining uncertainty.
- Test the metric. Ask whether an outsider with access to the agreed records could reproduce the result. If not, settle the data and attribution rules before setting a percentage or bonus.
- Stress-test the deal. Calculate what each side pays or receives in a low, expected, and high scenario. Use hypothetical figures clearly as examples; do not present them as market benchmarks. Check whether either side faces an unacceptable result in any plausible scenario.
- Set a review and exit. Choose a review date, the information each side will share, notice periods, handover duties, and what happens to unpaid fees or variable compensation at termination.
Put the definitions in writing
A useful agreement records the parties, services, deliverables, exclusions, payment schedule, expenses, approval process, data access, ownership and permitted use of assets, confidentiality, term, termination, and dispute process. For variable pay, attach the calculation rules and an example calculation. If the engagement crosses jurisdictions or raises questions about worker classification, tax, consumer disclosures, or enforceability, get advice for the relevant location. A contract’s label does not settle every legal question; the actual working relationship and local rules can matter. The IRS, for example, says that for U.S. federal tax purposes a contract naming someone an independent contractor is not by itself decisive. (Internal Revenue Service, “Type of Relationship”)
If recommendations or links in a published article generate commissions, disclose the relationship clearly near the relevant recommendation. The U.S. Federal Trade Commission’s guidance explains that affiliate relationships should be disclosed so readers can weigh an endorsement; requirements vary by jurisdiction and context. (Federal Trade Commission, “The FTC’s Endorsement Guides: What People Are Asking”)
The practical rule
Choose the fee structure after the work, control, and measurement are clear. Use project fees for bounded delivery, time-based billing for uncertain discovery, retainers for defined recurring capacity, and variable compensation only when both sides can verify the result and accept the risks that remain. In every case, write down what is included, how changes are handled, and how the relationship ends.
A fee model cannot create trust or guarantee commercial success. It can make assumptions explicit—and that is a more durable starting point for a partnership than promising that one payment structure will align every incentive.
