Packaging a service for sale

A service that can only be bought through a long conversation is a service that most foreign buyers will not buy. Cross-border buyers compare vendors quickly, often across multiple time zones and languages, and they cannot easily call you for an exploratory chat at 2:00 a.m. their time. They need to be able to read a one-page description of what you do, see what is and is not included, know the price or price range, and decide whether to ask for a proposal.

Most service businesses resist packaging because it feels like it constrains them. In practice, the opposite is true: a clearly packaged service sells more often, at higher prices, with fewer revisions, because the buyer's expectations are set before the first call. Packaging is not a limitation on what you can offer; it is a foundation that makes the offer legible to someone who has never met you.

This guide assumes you are selling a service — design, software development, advisory, engineering, content production, or similar — to buyers who may be in another province or another country. The same principles apply to productized services, retainers, and fixed-scope engagements.

The name of your service should describe the outcome the buyer gets, not the activity you perform. "Quarterly compliance audit" is better than "audit services." "Brand identity system" is better than "design work." "Software localization sprint" is better than "translation."

Avoid internal jargon, clever acronyms, and names that only make sense to people in your sector. A buyer in another country who has never heard of you should be able to read the name and know roughly what they would be buying. If the name requires a sentence of explanation, the name is not finished.

Test the name by reading it aloud to someone outside your industry. If they can guess the general shape of the service, the name works. If they ask "what does that mean?", rewrite it.

Each packaged service should answer five questions in plain language:

• What you get. The tangible deliverables — documents, files, access, hours, or sessions.
• What we need from you. The inputs, access, or decisions required from the buyer for the work to proceed.
• Timeline. How long the work takes from kickoff to delivery, and any assumptions that affect that timeline.
• What it costs. The price, the currency, and the payment terms.
• What is not included. Explicitly named exclusions, so the buyer is not surprised.

The "what is not included" section is the one most service businesses omit, and it is the one that prevents the most disputes. If a buyer assumes something is included and it is not, you either absorb the cost of doing the extra work or you have an uncomfortable conversation about scope. Naming exclusions up front converts that conversation into a simple upsell.

The most effective structure for a packaged service is three tiers — Good, Better, and Best. Three is enough to give the buyer a sense of choice without overwhelming them, and it creates a natural anchor: most buyers will select the middle tier, which is usually where you want them.

Each tier should differ on dimensions the buyer cares about — scope, deliverables, turnaround, support level, or number of revisions — not just on price. A common pattern is:

• Good. The minimum viable version of the service, scoped to be useful and complete on its own.
• Better. The recommended version, with the deliverables and support most buyers actually need.
• Best. The comprehensive version, for buyers who want maximum scope, faster turnaround, or ongoing support.

Set the price of the middle tier at the level you actually want to sell at. Set the low tier high enough that buying it feels like a deliberate choice for a constrained budget, not a default. Set the high tier high enough that it serves as an anchor for the middle, while still being justifiable by its additional scope.

When you sell across borders, currency, payment terms, and tax treatment become part of the package. Decide and state:

• Currency. Which currency your prices are quoted in, and whether you will invoice in the buyer's currency for an agreed conversion.
• Payment terms. Deposit, milestones, and final payment. For first-time cross-border buyers, a deposit of thirty to fifty percent is standard.
• Payment methods. Wire transfer, credit card, or other platforms. State which you accept and who bears transaction fees.
• Taxes. Whether your prices include applicable taxes, and how you handle GST/HST, VAT, or sales tax in the buyer's jurisdiction.

If your service is delivered digitally, you may need to register for VAT or GST in the buyer's jurisdiction once you cross certain revenue thresholds. This is a question for an accountant familiar with cross-border digital services; do not ignore it on the assumption that it does not apply to you.

See also: Pricing for export — from day one and Getting paid by a foreign customer.

When a buyer asks for a proposal, send a short document — one to two pages — that restates the package they have asked about and confirms the specifics for their engagement. A useful structure:

• Summary. Two sentences on what you understand they need.
• Scope. The tier and any modifications, with deliverables.
• Timeline. Start date, milestones, and completion date.
• Investment. Price, currency, payment schedule, and payment methods.
• Terms. Validity period of the proposal, cancellation, and any assumptions.
• Next steps. What you need from them to proceed, and by when.

The proposal is not the place to re-explain your service at length. The buyer has already read the package description; the proposal confirms how the package applies to them.

Once a proposal is accepted, convert it into a statement of work (SOW) that both parties sign. The SOW should be tight and operational, covering:

• Parties and effective date.
• Detailed scope and deliverables, with acceptance criteria where applicable.
• Inputs and access required from the buyer, with timing.
• Milestones, dates, and dependencies.
• Total price, payment schedule, and invoicing mechanics.
• Change order process — how scope changes are requested, priced, and approved.
• Ownership of deliverables and intellectual property, including pre-existing IP.
• Confidentiality, if applicable.
• Termination and dispute resolution.

For cross-border engagements, the SOW should also specify the governing law and jurisdiction. This is a decision for a lawyer, not a template — but having the question flagged in your template means your lawyer's review is faster and cheaper.

Before publishing a packaged service on your website or sending it to a prospective buyer, confirm:

• The name describes an outcome, not an activity.
• The description answers all five questions: what you get, what we need, timeline, cost, and exclusions.
• The price is stated in a specific currency, with payment terms.
• Tax treatment is addressed or flagged.
• The tiers differ on dimensions the buyer cares about, not just on price.
• Intellectual property ownership is stated.
• The page is readable by someone who has never met you and is in a different time zone.