Pricing software a services firm used to deliver as hours. The unit the product is sold by, the gate between advisory and product, moving an installed base of engagement clients onto product pricing, and what an acquirer credits when the method has become software.
[ The hour and the unit ]
← scroll to view full figure →
A services firm that turns its method into software has to price a product beside the labor that produced it. The instincts that built the practice are the wrong instincts for the product.
A rate card, a scoped statement of work, a blended rate that carries engagement risk. Each is sound for people and hours, and each is wrong for a tool built once and run for everyone who licenses it. Automation moved the question forward: when what the firm delivers no longer tracks the hours it bills, the firm either prices the product deliberately or keeps handing it over inside the engagement fee, priced at zero by accident.
Across the services firms in our corpus the shape is the same. The tool augments a service that is billed by the hour, so the better the tool works, the fewer hours the firm bills. The whole value proposition sits on the services side, the software has no carve-out and no way to be substantiated as a line item of its own, and the pitch slides back to doing the work better, faster and cheaper, which is fewer hours and less revenue.
The licensing model comes first. The value metric is usually what the client counts when it tells its own board the work happened, and the hour is rarely it. Packaging follows: the gate, meaning the line between what ships inside the software, what stays an engagement, and what the team still builds bespoke. The first client who received the tool free set that gate, and every later client inherits it. Pricing comes last, and its hardest part is the installed base: engagement clients move onto product pricing one account at a time, with the price attached to something new they receive.
The transition takes five shapes: the fixed-fee tool, the tool given away, the bespoke build that keeps repeating, the advisory gate, and the recurring layer nobody priced. Each puts a different question to the value metric and the gate, and none has a standard answer. The Pricing Architecture Assessment puts those questions to the product being built. The services firm page covers the five situations and how we work through them with a firm that is building a product, or preparing to sell the firm.
The full read follows the transition end to end, through to the exit, where an acquirer credits revenue that renews by default and a pricebook that explains its own realized prices. The partner piece takes the white-label case, where the software sells under another brand and the licensing decision travels with it. The value metric and the license grant belong to Licensing; the gate and what travels together belong to Packaging.
If the product is already in clients' hands and the price is still open, describe the firm through Talk to an Expert and a pricing expert who has read this transition inside services firms will reply.
A services firm that productizes a tool has to price software beside labor. The unit, the gate, the installed base, and the exit angle. Talk to an expert.
Describe the firm, the tool, and who already has it, and a pricing expert who has read this transition inside services firms will reply with where the value metric and the gate sit for you.
Talk to an Expert →
