A service packages page that sells fixed-scope work
A productised service only sells itself when the buyer can see exactly what they get, how long it takes and what happens after they pay. Give each package the same shape (name, outcome, inclusions, turnaround, price, one button) and put the exclusions in writing. Anticode builds the page from a description and points its buttons at your own payment link or a contact form.
Why fixed packages need a different page
A normal services page describes what you can do and invites a conversation. A packages page does the opposite: it makes the decision possible without one. That only works if the scope is tight enough to price in advance. "Brand identity" is not a package. "Logo, two colour palettes and a one-page usage sheet, delivered in ten working days" is.
Most productised businesses settle on two to four packages. One is too few to compare; six makes people stall. If you find yourself writing a fifth, it's often an add-on to one of the others rather than a package in its own right.
The anatomy of one package
| Part | What it does | Example |
|---|---|---|
| Name | Short, describes the result, not a tier label | Website audit |
| Who it's for | One line that lets the wrong buyer leave | For sites under 30 pages that already get traffic |
| Deliverables | A list of nouns the buyer will receive | Recorded walkthrough, written report, fix list ranked by effort |
| Turnaround | Working days from the moment you have what you need | Five working days from access |
| Revisions | How many rounds, and what counts as one | One round of questions by email |
| Price | The full amount, with tax treatment stated | Shown in your currency, VAT included or not |
| Action | One button, labelled with the verb | Buy the audit |
Keep the order identical across cards so the eye can compare row by row. If one package has a line the others don't, add it to all of them with "not included" rather than leaving a gap that looks like an oversight.
Buy now or enquire first
Some packages can be bought outright; others need a quick check that the buyer fits. Decide per package, not for the whole page.
- Buy now suits work with a fixed input: an audit, a set number of edits, a session of a fixed length. The button goes straight to checkout, and the confirmation email from your payment provider tells them what to send you next.
- Enquire first suits work where the input varies: a site that might be 5 or 50 pages, a document that might need a translator. The button goes to a contact form, and you reply with a payment link once you've agreed.
- Mixed is common: the smallest package is bought directly, the largest is "talk to us". Label the difference clearly so nobody pays for a package that turns out not to fit.
What else the page has to answer
Below the packages, answer the questions that stop someone clicking the button. These are usually about process rather than price:
- What happens in the hour after paying: an intake email, a short questionnaire, a calendar invite.
- What you need from them, and that the turnaround clock starts when you have it.
- What's excluded, said plainly: "copywriting isn't included; bring your own text".
- Your refund or cancellation terms before work starts.
- One or two examples of finished work for each package, if you can share them.
The show service prices on your website guide covers how to word prices, and selling coaching packages walks through a similar setup end to end.
How Anticode builds it
Describe the business and list the packages in your request, for example "a productised design studio with three packages: logo refresh, launch kit and monthly design support, each with deliverables, turnaround and a buy button". The Architect replies with a plan before building and may ask a question or two. A separate Pricing page and a Services page are both available if you want packages on their own page rather than on the home page.
Buy buttons open your account's one payment link, created in Stripe Payment Links, PayPal, Gumroad, Lemon Squeezy, Shopify or Whop; every buy button on your sites uses the same link. With several buyable packages, point it at a product list or multi-item checkout at your provider where each package is listed, and name the packages identically on both. Enquire buttons go to the contact form (name, email and a message), and submissions are saved in your dashboard and can be emailed to you. If the price depends on numbers the buyer gives you, such as a page count, a custom form with a site function can work out a quote on the server and show it on the thank-you page. It isn't calculated live as they type.
Limits
- No checkout on the page itself. Payment happens on your provider's checkout, which also sends the receipt.
- No intake questionnaire after payment. Send it from your provider's confirmation email or your own inbox.
- No client portal for delivering files or tracking progress. Use email or a shared folder.
- No discount codes managed by Anticode. Set them up in your payment provider if it supports them.
Questions people ask
Should a productised service page show prices?
Yes. Fixed prices are the point of a productised service. Hiding them turns the page back into a sales conversation.
Can each package go to a different payment link?
No. An Anticode account has one payment link and every buy button opens it. Point it at a product list or multi-item checkout at your provider that holds all your packages, or send the larger packages to the enquiry form and reply with a payment link of your own.
What if a buyer pays for a package that doesn't fit?
Say in your terms that you'll check fit before starting and refund if it isn't right. Then refund through your payment provider.