Pricing and packaging · Answered by Golden Section from more than 400 B2B software companies observed
Yes, when adoption depends on significant training, change management and success factors, especially if competitors normally charge for it, and price it from tracked hours rather than a guess. A paid implementation covers your cost, makes the customer commit people and time to go-live, and screens out buyers who are not serious; a free one teaches the customer that the work has no value. Price it at cost plus at least a 25% services margin, sell it as fixed-price packages rather than open hourly work, and present it apart from the subscription so the services number does not crowd the software decision. Report it on its own lines, outside ARR. Standard support belongs inside the subscription; premium response and hands-on services can be paid tiers. Next step: track implementation hours by customer for the next two quarters.
Charge for implementation when adoption needs real training, change management and success work, especially where competitors charge for it. Price it at tracked cost plus a margin of at least 25%, and sell it in fixed-price packages. Keep standard support in the subscription and charge for what goes beyond it.
| Metric | Value | What it means | Source |
|---|---|---|---|
| Implementation fee basis | tracked cost to implement, plus margin | implementation hours per customer × loaded cost per hour, plus marginthe same data supports billing overages where the contract allows and evidences cost at exit | Golden Section playbookImplementation Hours Tracking |
| Services margin | a floor to watch, not a number to maximize | services revenue minus services delivery cost, ÷ services revenuethe play prefers an engagement at 25 points of margin that lifts a customer to top quartile over one at 55 that leaves him at the median | Golden Section playbookValue Pinnacle Services |
| Services margin floor | 25% | services revenue minus services delivery cost, ÷ services revenuea floor, not a target; below it the package is usually mispriced or badly scoped | Golden Section operating viewGolden Section operating view |
| Gross margin we look for | above 65%, with a path to 75%+ | gross margin computed after implementation and support costsour equity screen; implementation labor belongs in cost of revenue | Golden Section, publishedGrowth Equity |
| Hourly not-to-exceed contracts | never agree to one | hourly billing capped at a fixed amountMistake 51; you carry the overrun and lose the upside | Golden Section, publishedThe B2B Software Mistakes List |
Implementation is where the value promised in the sale is either delivered or lost, so it deserves a price and a process. The implementation lifecycle gives it scoped phases and sign-offs; implementation hours tracking gives you the cost data to price it at cost plus margin and to bill overages where the contract allows. Payment also tests commitment. A customer who pays for go-live assigns people to it.
The form of the fee matters as much as the amount. Fixed-price packages protect you from the open-ended exposure of hourly work, and the value pinnacle services play adds two rules: sell small repeatable units at consistent prices, and keep the services number away from the subscription price, because the two side by side hand an internal IT group its argument for building instead. Separate out the design, change management and training work the customer would incur whether they built or bought.
The accounting decides what the fee is worth. Implementation and support labor belong in cost of revenue, and a lender or buyer who finds them in operating expense restates your margin. Implementation fees are not recurring revenue, and buyers discount one-time fees mixed into ARR.
The numbers are invented. A company at $2.5M in annual revenue charges a flat $5K for implementation. Tracking the last ten go-lives shows an average of 120 hours at a loaded $95 an hour, about $11.4K of cost, with multi-site customers running nearly double. It replaces the flat fee with two fixed packages, $16K for a single site and $28K for multi-site, each with a written scope and a change-order process, and shows them on a separate page at kickoff. It moves implementation staff into cost of revenue and reports services revenue and margin on their own lines, outside ARR. Win rate is unchanged over the next two quarters, and services move from a loss to a modest margin.
Products with self-serve setup and small contracts should not charge for implementation, because the friction costs more than the fee. A strategic deal can absorb the fee into a longer term, provided the cost still shows up in cost of revenue. Where competitors in the vertical do not charge for implementation and adoption needs little change management, folding setup into the subscription can be the better call.
From the Golden Section mistakes list, each paired with the play that prevents it.
An implementation without structure cannot be priced, because nobody knows what it costs.
Capped hourly work is the most common way an implementation fee turns into a loss.
Implementation and support revenue that grows faster than the product's role is the sign of a services firm, not a software company.
In the order we would run them. Each is on its own page, most with a free Excel template.
Defines the phases and sign-offs that make an implementation scopable and priceable.
Tracks hours per customer so the fee reflects real cost plus margin.
Packages services into repeatable fixed-price units and keeps them off the software sale.
Sets the standard support commitment that the subscription includes, so premium tiers have a clear baseline.
Operations plays Implementation, support and their costs are run and measured through the operations plays.
There is no single answer. Whether a platform fee fits depends on the nature of the customer's ROI and how customers in the vertical work. A base platform fee works when it maps to value every customer receives regardless of size, such as the core system of record, with usage or locations priced on top. Keep the structure simple enough for a rep to explain in a sentence. The Pricing Matrix play also favors folding higher-margin components into one line item, so customers cannot churn off individual pieces.
Standard support should sit inside the subscription, with paid premium tiers above it, defined in a standard service level agreement you bring out when asked rather than lead with. Charge for what goes beyond it: faster response tiers, named staff, training, or packaged services that move a customer's results. If customers use your people more than your product, the product needs the work, not the price list.
No. Report implementation and services revenue on their own line with their own margin. Buyers discount one-time fees mixed into ARR, and finding them there makes a buyer question every other number.
This is a pricing and accounting decision, not a funding one. Clean services lines matter later, though: our lending looks at gross margin after implementation and support costs, with a 65% minimum.
Growth capital lending →Reviewed by Dougal Cameron, CEO & Co-Founder on 2026-10-22. Golden Section observations are labeled separately from external benchmarks and illustrative arithmetic.