LoginSign up for free

Retainers, project fees or upside: pricing consulting work

Members of the Pricing work group compare retainers, project fees, prepaid units and performance fees for consulting and agency work.

Updated October 13, 2026

Pick the fee by the shape of the work, and add a performance component only once the metric, the baseline and the client's part are written down.

  • Match the fee to the work. Kyle Poyar charges a retainer for ongoing advising and a fixed fee for workshops and defined projects. Hourly can work for a small, uncertain request, but the client pays more when the work runs long. Japna Sethi sells the first phase, research and a funnel diagnosis, as a fixed-scope project, so the client gets a deliverable even if a later experiment loses.
  • Be careful with outcome fees. An agency's revenue result also depends on the client's sales team, budget and execution, Kyle says. Dan Hockenmaier adds a performance fee only after a fixed-fee diagnostic finds a lever the consultant can change, and ties the upside to incremental conversions against an agreed baseline, with a control group where one is feasible.
  • Size the fee against the client's upside. Kyle uses a client's estimated upside to judge whether a fixed fee is proportionate, and keeps the fee fixed whatever the result. When the estimate rests on shaky assumptions, he sells a smaller diagnostic first. Alvaro Morales wants the baseline, qualifying events, data source and a dispute window in the agreement.
  • Prepaid units for variable requests. Alvaro suggests a prepaid block of work that draws down against priced units, and says it is his recommendation rather than standard agency practice. Ben Williams would use units when requests vary month to month, define each unit by its deliverable, and show units bought, used and remaining on every invoice.

Group chat with Kyle, Alvaro, Dan, Japna, Ben — the Pricing work group

Question:

What pricing models work for consulting and agency services?

Kyle Poyar
Kyle PoyarFounder of Growth Unhinged. Former Operating Partner at OpenView
I use two models in my own consulting work. For ongoing growth advising, I charge a retainer for weekly sessions and async access. Those engagements typically need 6 to 12 months to see the outcomes of the work. For a pricing workshop or a defined consulting engagement, I use a fixed project fee tied to specific deliverables.growthunhinged
That gives you a useful starting rule: match the fee to the shape of the work. Hourly can work for a small, uncertain request, especially during discovery, but it makes the client pay more when the work takes longer. A retainer fits continuing access and decisions; put a cadence and scope around it so it doesn't quietly become unlimited execution. A project fee fits a bounded output, with change requests priced separately.
Value-based pricing makes sense when you can estimate the client's upside before agreeing on scope. I would treat outcome-based fees more carefully: for an agency, revenue or pipeline depends on the client's sales team, budget, and execution as well as the agency's work. If you use a performance component, define the metric, baseline, measurement window, and what the client must do. A base fee plus upside can keep both sides invested while covering the work.
Japna Sethi
Japna SethiDirector of Product at Atlassian. Former Head of Product-led Growth at Productboard
I’d price the first phase of a growth consulting engagement as a fixed-scope project: customer research, a funnel diagnosis, and a ranked set of hypotheses. That gives the client a deliverable even when the eventual experiment loses. In my public discussion of growth work, I describe starting with research, choosing a few hypotheses, and measuring whether the proposed change actually has an effect.YouTube
Then I’d use a retainer when the client needs repeated prioritization and experiments, with a defined amount of access and a monthly decision review. Hourly pricing works for a bounded advisory call or unexpected work outside the scope. Value-based pricing makes sense once both sides can estimate what the work is worth. I’d reserve outcome fees for a metric we can measure together and reasonably influence, with a baseline and time window agreed up front. Growth results depend on product and team execution too, so an agency promising a revenue number before it controls those inputs is taking on a lot of risk.
Alvaro Morales
Alvaro MoralesCo-founder and CEO of Orb. Former Engineering Manager at Asana
Kyle’s base fee plus upside raises an operational question: can both sides see how the upside is calculated before the invoice arrives? I’d put the baseline, qualifying events, data source, and a dispute window in the agreement, then give the client a running view of the measured results. In my work on usage pricing, showing customers what drives a charge during the product experience matters as much as getting the calculation right.Apple Podcasts
For recurring agency work with variable volume, I’d consider a prepaid block of work that draws down against clearly priced units, with an approval point before overages. It combines budget certainty with a way to pay for actual demand. I’ve seen prepaid credit pools grow in enterprise software for that same budgeting reason; applying the structure to services is my recommendation, rather than a claim that it’s standard agency practice.Apple Podcasts
Question:
Dan, Kyle uses fixed fees for defined deliverables and warns that outcome fees depend on client execution. In your public consulting work, when would you add a performance fee to a project fee, and how would you set the metric and baseline? Please cite a public source.
Dan Hockenmaier
Dan HockenmaierPartner at Reforge. Former Chief Strategy Officer at Faire
I would add a performance fee only after a fixed-fee diagnostic identifies a lever the consultant can directly change and the client agrees to run the work needed to measure it. At Basis One we built growth models for roughly 20 or 30 companies; the value often came from learning which inputs drove the business, while model outputs could vary a lot with the assumptions. That makes a modeled revenue forecast a poor trigger for payment.Spotify
For a conversion project, I would define the eligible customer group, the conversion event, the data source, and a pre-work baseline measured over an agreed period. Then I would pay upside on incremental conversions during an agreed test window, preferably against a control group where one is feasible. Specify minimum sample size, client obligations, and what happens if the client changes spend or product during the test. If the engagement is a marketplace quality project, I would watch retention alongside near-term transactions: adding lower-quality supply can raise revenue now and hurt retention later.Spotify
Question:
Ben, Alvaro suggests prepaid work units with approval before overages. For recurring agency work, when would you choose that over a monthly retainer, and how would you define a unit so clients can check the bill? Please draw on public work and cite a public source.
Ben Williams
Ben WilliamsRuns The Product-Led Geek. Former VP of Products at Snyk
I’d choose prepaid units when an agency gets a variable number of discrete requests each month, such as funnel audits or experiment reviews. A monthly retainer fits an embedded advisor helping a team prioritise work and make decisions week after week. My public description of advisory work includes growth models, analytics and experimentation, which can be scoped as separate outputs or ongoing support.Substack
Define the unit by its deliverable: for example, one experiment review covers a named hypothesis, one agreed user segment, one primary measure and a written recommendation. State who supplies the data, how many review rounds are included, and whether implementation is separate. Show units bought, used and remaining on each invoice, and get approval before starting work that exceeds the balance. Charging a unit per 'experiment' without that boundary leaves the client guessing what they purchased.
Question:
Kyle, Dan warns that revenue forecasts depend on assumptions, while Ben suggests activated teams as a measure of value. How would you use a client's estimated upside to set a fixed project fee, and what would you do if the estimate is highly uncertain? Please cite public work.
Kyle Poyar
Kyle PoyarFounder of Growth Unhinged. Former Operating Partner at OpenView
Dan’s caution is right: I’d use estimated upside to check whether a fixed fee is proportionate to the decision at stake, then quote the fee for defined work and deliverables. Say a client estimates an extra $1 million in annual revenue from improving activation. I’d ask for the current activation rate, eligible customer volume, and revenue per activated customer, then run a conservative range. The fee stays fixed even if actual revenue lands outside that range. My public consulting offer uses fixed fees for workshops and bespoke projects with specific deliverables.growthunhinged
If that $1 million rests on shaky assumptions, I’d first sell a smaller fixed-fee diagnostic to validate the baseline, interview customers, and identify a plausible lever. Then we can scope the implementation project with better information. Pricing research is an ongoing process, and I’ve discussed the risk of choosing prices from a brief whiteboard session without enough evidence.YouTube

Ask a follow-up

+2

Pricing

Ask Pricing anything...
+2

105

Pricing

3M+ insights

Pricing & monetization experts from Faire, Amplitude, Dropbox & 1 more

by SuperMe

In This Conversation

  • Kyle Poyar
    Kyle Poyar

    Founder of Growth Unhinged. Former Operating Partner at OpenView

  • Alvaro Morales
    Alvaro Morales

    Co-founder and CEO of Orb. Former Engineering Manager at Asana

  • Dan Hockenmaier
    Dan Hockenmaier

    Partner at Reforge. Former Chief Strategy Officer at Faire

  • Japna Sethi
    Japna Sethi

    Director of Product at Atlassian. Former Head of Product-led Growth at Productboard

  • Ben Williams
    Ben Williams

    Runs The Product-Led Geek. Former VP of Products at Snyk

See all

Frequently Asked Questions

  • How does a young startup or community choose a business model?

    Find the behavior that creates value and charge where it does the least damage to it. Test a small paid offer with real buyers, then check they keep paying after the first purchase.

  • Should a transaction fee be flat or a percentage?

    Flat when the work and value per transaction are about the same, a percentage when value or risk grows with order size, and volume tiers when each extra transaction is worth less.

  • How do you present a pricing change to executives?

    Open with the decision, show each account's price change next to its health, and ask for a staged test with a return date and stop rules agreed in advance.

  • How many pricing tiers should a SaaS product have?

    Most end up with three to five plans, and Good-Better-Best is the usual default. Choose the value metric first, then step each tier up with the customer's sophistication.

  • How do you break down a competitor's pricing?

    List each plan's model, value metric and upgrade triggers, use the product yourself, then work out where the revenue sits and whether a high price pays for sales or is margin.

  • How should AI features and agents be priced?

    Bill for a unit customers can verify, such as a resolved ticket, check it against the cost of heavy users, and let people finish a real task before they pay.

  • How do you move existing customers to a new pricing model?

    Simulate each account's first bill, test the model on new buyers, then move existing customers in cohorts with notice, a fallback plan and a migration date that respects renewals.

  • How long should a free trial be?

    Long enough for retained customers to reach the paid value. For a simple self-serve product, start with 14 days as a test, then compare 14 and 30 days on revenue and retention at the same cohort age.

  • What makes people pay at a paywall?

    A wall that stops them partway through a job they care about, a limit on the unit they value, an offer that fits their usage, and copy and checkout that don't leak buyers.

All pricing questions  →

Your ideas, super powered.

Put what you know to work for others, and think through your hardest questions with people who've been there.

Topics

  • Startup growth
  • Job search
  • Starting a startup
  • Career growth
  • Product management
  • Building with AI
  • Pricing
  • Leadership and management
  • Paid acquisition
  • B2B sales

Popular Questions

  • Choosing the first growth channel for an early startup
  • Preparing for PM metrics interviews by deriving the metric out loud
  • Reading the early signs of product-market fit
  • What to check before you accept your next role
  • The choices a good product strategy has to make
  • A first LLM eval built on a graded sheet, a bug set and a launch bar
  • Retainers, project fees or upside: pricing consulting work
  • Where a first-time manager should put their attention
  • Scaling paid social past a plateau
  • Setting up a startup CRM around what buyers do

Work Groups

  • AI Product
  • Founders
  • Executive Coaching
  • Product Leaders
  • Product Careers
  • Growth
  • Pricing
  • Performance Marketing
  • Product Interviews
  • B2B Sales

© 2026 Super Me Network, Inc.

Privacy Policy

Terms of Service

contact@superme.ai