A productised service makes a repeatable piece of work easier to assess. It can still involve judgement. The useful discipline is to define the assignment clearly enough that both sides can recognise when it is complete.
Start with a buying situation
Choose a situation you can serve repeatedly. For example: a small software company has several versions of its customer-onboarding process and wants a practical recommendation before rewriting them.
The offer should name that situation and the decision your work supports. “Decide which onboarding steps to keep, combine or remove” is more concrete than “transform the customer journey.”
Consultative-selling guidance from Salesforce emphasises the buyer’s goals. Packaging the work should preserve that relevance rather than force every enquiry into the same box.
A completed fictional service card
Service: Customer-onboarding process review.
For: a team reviewing one existing onboarding journey.
Buyer’s decision: agree a revised sequence before commissioning new content or software work.
Included: review of one current process, up to five supplied documents, two staff interviews and a recommendation meeting.
Output: an annotated process map, a prioritised recommendation sheet and a short decision summary.
Client inputs: current documents, an accountable contact and access to the two interviewees.
Completion: the agreed outputs are delivered and discussed in one review meeting.
Separate work: writing all new onboarding content, software configuration, customer research and ongoing implementation support.
Fee and timing: confirmed in the current written proposal after the input and access check.
This card explains the purchase without claiming a fixed improvement in retention or revenue.
Decide what can be standard
Standardise the parts that recur: input request, review method, deliverable structure and review process. Leave room for client-specific evidence and recommendations.
Do not standardise a result that depends on the client’s implementation. A recommendation document can be delivered by an agreed date if the necessary inputs arrive; a promised rise in customer retention requires a different basis.
Set a clear route for exceptions. If an enquiry involves three business units and twelve interviews, issue a different scope rather than quietly absorbing the difference.
Use the card in a real sales conversation
Ask the buyer whether the stated decision matches their problem. Then check the inputs, timing and person who will use the output.
If they need ongoing implementation rather than a review, explain that difference before quoting. The card should help the buyer choose, including choosing a different service.
Test the offer against delivery
After the assignment, compare actual work with the card. Which input caused delay? Which output was useful? Which request repeatedly fell outside scope?
Revise the offer using that evidence. Do not add vague benefits simply because the page feels short. A clear service, a useful output and a credible boundary give a buyer more to assess than a long list of consultancy adjectives.