Setting a per-transaction fee: flat, percentage or volume tiers

The Pricing work group on choosing a fee structure, setting its ceiling and counting the billable transaction.

Updated October 13, 2026

Charge for a completed transaction customers see as value, size the fee against the work the platform takes on, and judge it by what customers do after the first paid transaction.

Pick the structure by what grows. Kyle Poyar uses a fixed fee when the work and value per transaction are similar, a percentage when value rises with the amount, and volume tiers when each added transaction is worth less. Dan Hockenmaier adds that a percentage fits when the platform takes on cost or risk that grows with the order, such as financing, returns or delivery.
The ceiling is the work you remove. Dan says to model the fee against the seller's next-best way to win and serve the customer: if the seller saves $20, a $25 fee needs another source of value. Faire's net payment terms and free returns give its fee a different basis than an introduction.
Agree on what counts. Alvaro Morales says to replay real transaction events through the billing rules, count each order's first successful completion once, and link refunds and reversals to the original order. Product, engineering and finance should sign off on the rules, and customers should see a running count and projected charge.
Test past the first transaction. Elena Verna pilots one fee against another on the same journey and tracks second and third transactions. A fee that lifts first-order revenue while cutting later orders prices away growth. Ben Williams models the monthly bill for a small and a high-volume account, since a rate that works self-serve may need a volume commitment once procurement is involved.

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

Question:

How should a company price per-transaction fees?

Elena VernaLeads growth at Lovable. Former SVP Growth at SurveyMonkey

Start with the transaction itself: does each completed transaction represent value the customer recognizes? If yes, price the successful output and define exactly what counts, including retries and refunds. If volume can rise while customer value stays flat, a flat fee per event will create friction as customers grow.

At Lovable, we chose credits tied to building output rather than seats, because charging for people would slow collaboration and the usage that creates value. We also made Agent Mode actions cost different amounts of credit depending on complexity. The lesson for transaction pricing: keep the metric easy to understand, then vary the fee only where transaction value or cost meaningfully differs.

LinkedIn+1

Pilot the fee with real customers across low and high volume. Watch activation, repeat usage, conversion, and revenue per customer. I think of the fee as one choice inside the monetization model: use case, value metric, perceived value, then price.

Spotify

Dan HockenmaierPartner at Reforge. Former Chief Strategy Officer at Faire

For a marketplace, the ceiling on a transaction fee comes from the work the platform takes off buyers' and sellers' hands. I group those costs into finding a counterparty, agreeing on terms, making sure both sides perform, and getting the product delivered. A marketplace that only makes introductions has less room to charge than one that handles checkout, returns, or delivery.

danhock

Then model the fee against the seller's next-best way to get and serve that customer. If the seller saves $20 in acquisition and transaction costs, a $25 fee needs some other clear source of value to work. Check the buyer's total price too, since a fee that cuts conversion can shrink the seller's volume. At Faire, net payment terms and free returns reduce a retailer's inventory risk, which is a different service from simply finding a brand online.

danhock

I would test a fixed charge where the work and cost are roughly constant per order, a percentage where value and risk rise with order size, and a combination where both are true. For each version, measure completed transactions, seller contribution margin after fees, repeat use, and the platform's margin after refunds and support. Those results tell you whether the fee captures value or suppresses transactions.

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

Before settling on the fee, replay actual transaction events through the proposed billing rules. A retry, reversal, or late-arriving event can change the invoice even when the price per transaction looks reasonable. Have product, engineering, and finance agree on the event definition and reconcile the customer-visible count with the invoice. I’ve recommended a cross-functional pricing group because those teams see different failure modes in the same pricing decision.

Apple Podcasts

Then show customers their running count and projected charge during the billing period. I’ve discussed how Orb powers billing transparency in Vercel and Supabase dashboards and pricing feedback during a Replit Agent session. That feedback lets someone judge the cost of the next transaction while they can still act on it.

Apple Podcasts

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

Once the billable event is clear, model the monthly bill for a small account and a high-volume account using expected transaction counts. Show each buyer the resulting spend and ask whether they can approve it through self-serve checkout. Keep enough room for a new account to reach its first meaningful result before a fee or usage limit blocks adoption. In my writing on packaging, I use three questions: which use case does each plan solve, who buys it, and what change makes an upgrade worthwhile? At Snyk, the Team plan served smaller engineering-led buyers through self-serve, while larger companies with security-led buying needed an enterprise sales process. That distinction matters here too: a transaction rate that works for a small team may need a volume commitment and a human conversation once procurement gets involved.

plg

Question:

Kyle, Elena says a flat fee creates friction when transaction volume grows faster than customer value. How would you choose between a flat fee, a percentage, and volume tiers, and what public example supports your choice? Please cite only public sources.

Kyle PoyarFounder of Growth Unhinged. Former Operating Partner at OpenView

I’d choose based on what grows with each transaction. Use a fixed dollar fee when the work and value per completed transaction are similar. Use a percentage when the customer’s value rises with the transaction amount. Add volume tiers when high-volume customers bring meaningful repeat business but the marginal value or cost per transaction falls. I’d check each option against the buyer’s total price, the seller’s margin, and completed transactions over time.

OpenTable is a useful example from our Mostly Growth discussion: its low take rate was described as roughly 1% to 2% per guest, with a move toward a dollar-denominated fee per booking. It shows why a booking may be a more useful unit than a share of the restaurant’s bill when the platform is providing a guest introduction. We also discussed how fees that raise the buyer’s total price can push customers elsewhere and prompt suppliers to find another channel.

YouTube

Elena’s concern is the test for tiers: if a customer doubles completed transactions while the benefit of each added transaction declines, keep the bill tied to usage but lower the marginal fee at higher volume. Publish the tier boundaries and show the effective fee at expected volumes so customers can forecast the bill.

Question:

Dan, Kyle cites OpenTable’s shift toward a dollar fee per booking. How would you decide whether a marketplace should charge per booking or take a percentage, given the seller’s next-best way to find customers? Please cite public sources.

Dan HockenmaierPartner at Reforge. Former Chief Strategy Officer at Faire

I’d calculate what the seller spends to acquire and serve an incremental customer without the marketplace, then ask what part of that expense our product actually removes. A per-booking fee fits when the service is essentially the same introduction regardless of booking value. A percentage fits better when the marketplace takes on costs or risk that grow with the order, such as financing, returns, or delivery. Faire offers net payment terms and free returns to reduce retailers’ risk, which gives its fee a different basis than a simple introduction.

danhock

I’d compare both fee schedules at small and large order sizes against the seller’s margin after fees and the buyer’s final price. If a $50 booking and a $500 booking cost the platform roughly the same to generate, a percentage can make the expensive order look needlessly costly to the seller. If the larger order carries more financial exposure for the platform, a flat fee may undercharge for that work.

Question:

Elena, Kyle proposed fixed fees, percentages, and volume tiers, while Dan tied marketplace fees to the service provided. How would you test a starting per-transaction fee and decide whether it hurts repeat usage? Please cite public sources.

Elena VernaLeads growth at Lovable. Former SVP Growth at SurveyMonkey

I’d pilot one fee against the same customer journey with a different fee, then follow customers beyond the first paid transaction. Track the share who complete a second and third transaction, time between transactions, buyer conversion, and seller margin by transaction volume. A fee that lifts revenue on the first order while reducing later orders is pricing away the behavior that grows the business.

Split the diagnosis before changing the rate: can customers see the fee, can they predict their bill, and does the charged transaction feel worth it? I’ve described monetization work as three separate problems: awareness, conversion friction, and the model itself. Pilot the pricing change only after customers can understand and pay under the current rules, or a checkout problem will masquerade as fee resistance.

Spotify

Question:

Alvaro, Elena would compare repeat transactions across fee pilots. How should a company count retries, refunds, and reversals so both the test and customer invoices use the same billable transaction count? Please cite public sources.

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

For Elena’s pilot, I’d define one canonical billable event and run both the experiment and the invoice from that same count. For a completed-order fee, give each order a stable ID. Count its first successful completion once, even if the completion event is delivered twice or the payment is retried. Keep failed attempts in operational data, but outside the billable count. Treat a refund or reversal as a linked adjustment to that original order, with the contract stating whether it removes the fee. Apply the same rule to late events and to every test cohort.

Reconcile three views daily: completed orders in the product, the experiment’s billable count, and the invoice preview. Any gap should be explainable by a retry, adjustment, or billing-period cutoff. Product, engineering, and finance should approve those rules together. I’ve advocated a multi-stakeholder pricing group and customer-visible usage feedback because the count customers see needs to agree with what they pay.

Apple Podcasts

Ask a follow-up

Pricing

105

Pricing

3M+ insights

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

by SuperMe

Frequently Asked Questions

How should a consultant or agency price its services?
By the shape of the work: a fixed fee for a defined deliverable, a retainer for ongoing access, prepaid units for variable requests. Add a performance fee only once the metric, baseline and client duties are agreed.
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.
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 →

Frequently Asked Questions

Setting a per-transaction fee: flat, percentage or volume tiers

Pricing

Frequently Asked Questions

How should a consultant or agency price its services?

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

How do you present a pricing change to executives?

How many pricing tiers should a SaaS product have?

How do you break down a competitor's pricing?

How should AI features and agents be priced?

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

How long should a free trial be?

What makes people pay at a paywall?

Your ideas, super powered.

Setting a per-transaction fee: flat, percentage or volume tiers

Pricing

Frequently Asked Questions

How should a consultant or agency price its services?

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

How do you present a pricing change to executives?

How many pricing tiers should a SaaS product have?

How do you break down a competitor's pricing?

How should AI features and agents be priced?

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

How long should a free trial be?

What makes people pay at a paywall?

Your ideas, super powered.