How to Sell Services That Take Customers to the Top of Their Field

A services lead put a single page in front of two customers. Three columns. What you do yourself day to day, what we do with you monthly, what we do together quarterly, with an asterisk on every line that costs money. Both customers came back and asked for three statements of work. Before that page existed, the same two had spent a year pulling her team through unpaid enhancement requests. Nothing about the product had changed. But the customer could now see what excellence looked like and what it cost.

Read mistake 155 before running this play. Services replacing product is a real failure and this play does not license it. What this play addresses is the opposite error, which is starving the services function in a company whose whole moat is what its people know.

If software gets cheap to build, three things still hold value. A network effect and integrated hardware and domain mastery. Most vertical companies have only the third. When that is your moat, the features are the vessel, and what you are selling is a customer arriving at the top of his own field.

Two consequences follow and they arent necessarily intuitive. Services are where the mastery gets delivered, and they are the one thing an internal IT group cannot copy. In every build-versus-buy fight the software argument is contestable and the domain argument is not. And you optimize services for the outcome instead of the margin. A customer delivered to top-quartile performance renews forever, expands into the division next door, and sets the price ceiling for everyone behind him. An engagement at twenty-five points of margin that produces that is worth more than one at fifty-five that leaves him at the median. Margin is a floor to watch, not a number to maximize.

The goal: A packaged services catalog tied to a published maturity rubric, sold many times over rather than negotiated one deal at a time.

Steps

1. Publish what excellence means in your vertical. Five or six dimensions, scored, with named levels. Where the trade association charges for its assessment, give yours away. The data set is worth more than the fee.
2. Assess the whole base and tell each customer where he ranks. Relative standing is the most reliable services trigger there is, and your base becomes a benchmark nobody else has.
3. Build one package against each rubric dimension. Small repeatable units at a consistent price, sold many times and many times over. Never the large bespoke transformation sold rarely, because that engagement ends and leaves you with nothing to sell next.
4. Put the catalog on one page and show it at kickoff. State plainly what the customer gets, what he must do himself, what is optional, and what costs extra. Showing it early is the whole trick; showing it during the first argument about scope reads as a bill.
5. Keep the services number off the software sale. A subscription price sitting next to a services price of similar size hands the internal IT group everything it needs. Lead with speed to stand-up. Two working sessions and a configuration map, not a two-hundred-thousand-dollar requirements catalog. Then separate out the work the customer incurs either way, which is design and change management and training. He pays for that whether he builds or buys, and your implementation partner needs to say so too.
6. Hire the bench from the practitioner base. People who did the job inside a customer organization know how to talk to a senior vice president, because that was their day job, and they arrive with credibility you cannot train into a consultant. Hold yourself to one test. Would you put any member of this team in front of any customer to deliver the promise? Until the answer is yes, the moat is a person and an acquirer cannot buy it.
7. Re-assess the base annually and split it by services engagement. Track two numbers. Median movement on the rubric, and the share of services revenue coming from packaged rather than bespoke work. The second one is what keeps a software company from waking up as a consultancy. If the engaged cohort does not outperform the rest of the base on net retention, either the services are not producing outcomes or the outcomes are not driving retention, and you should abandon the play rather than defend it.

Troubleshooting

My customers interact with my team more than with my product. Stop. You have crossed into mistake 155 and you are running a services business.

Every engagement gets scoped from scratch. Your rubric is not specific enough to generate packages. Go back to step one.

Services margin has fallen below my floor. The package is mispriced or badly scoped. Fix the package, not the outcome.