# Service-package specification

Source: https://lindo.ai/guides/how-to-package-website-services
Updated: 2026-09-03
Published by: Lindo Team

Includes a buyer brief, scope comparison, acceptance tests, exclusions, and a post-project exception log.
Illustrative planning aid, not market data or a guarantee. Do not store credentials or private client data here.

## Working brief

### Buyer / situation / desired first-release outcome

- Notes:
- Owner / decision:
- Evidence / next action:

### Client inputs / due date / approver

- Notes:
- Owner / decision:
- Evidence / next action:

### Pages and functions / acceptance test for each

- Notes:
- Owner / decision:
- Evidence / next action:

### Content and revision allowance

- Notes:
- Owner / decision:
- Evidence / next action:

### Exclusions / discovery dependencies

- Notes:
- Owner / decision:
- Evidence / next action:

### One-time and recurring fees

- Notes:
- Owner / decision:
- Evidence / next action:

### Handoff and ongoing owner

- Notes:
- Owner / decision:
- Evidence / next action:

### Actual exceptions / next package revision

- Notes:
- Owner / decision:
- Evidence / next action:

## Acceptance checklist

- [ ] Each package names a buyer and a first-release outcome.
  Owner / evidence / date:

- [ ] Required client inputs are visible before purchase.
  Owner / evidence / date:

- [ ] Content, revisions, integrations, and acceptance tests have boundaries.
  Owner / evidence / date:

- [ ] Discovery is separate when feasibility is unknown.
  Owner / evidence / date:

- [ ] One-time and recurring costs are shown separately.
  Owner / evidence / date:

- [ ] A delivery review will record recurring exceptions.
  Owner / evidence / date:

## Examples and templates from the guide

### Package specification to copy

Buyer and situation:
What the first release enables:
Required client inputs and due date:
Included page types and functions:
Revision rounds and named approver:
Acceptance tests:
Excluded work and optional additions:
Delivery schedule starts when:
One-time fee / recurring fees:
Ownership, handoff, and support boundary:

### Recommendation language

I recommend the launch scope because you have one offer and approved content. The service-growth scope adds interviews and separate service pages, which you do not need yet. Booking integration is excluded until we test your provider. Here are the handoff tests and ongoing costs for the recommended option.

## Working tables

### Example scope difference

| Responsibility | Launch | Service-growth |
| --- | --- | --- |
| Copy | Edit approved client text | Interview, draft, and obtain approval |
| Page structure | One main offer | Distinct service intents on shared layouts |
| Proof | Supplied credentials | Approved project case studies |
| Measurement | Test the contact path | Define service-level enquiry reporting |

## Sources and next steps

- Use a page map that gives every page a job: https://lindo.ai/guides/how-to-make-a-website
- Write the care-plan responsibilities: https://lindo.ai/guides/how-to-create-website-maintenance-plans
- Calculate the package cost and price: https://lindo.ai/guides/how-to-price-website-design