Pattern fixture

Service Offer Scope Fixture

A service page where an agent must separate buyer pain, scope, inputs, deliverables, proof, objections, and next step before writing copy or schema.

Agent Question

What is included in the offer, what inputs are required, what proof supports it, and what is the next step?

Pattern Contract

Explain a service, package, productized offer, or implementation path with scope, process, proof, and next step.

Visible Sections

Problem
Offer scope
Inputs required
Process
Deliverables
Proof
Objections
Next step
Source and claim notes

Metadata Checks

One H1 identifies the specific service fixture
Title and description are service-specific
Canonical route is the fixture route

Schema Checks

WebPage schema names service-offer-page as the pattern
Service schema requirements are visible as obligations
No pricing, guarantee, or credential claims appear without source notes

Traceability Checks

Scope, deliverables, proof, and next-step claims cite fixture evidence
Unsupported guarantees are called out as blocked

Source Evidence

src/data/agent-reference.ts: pagePatterns.service-offer-page
/source-traceability.json
/services/schema.json

Good Example

The offer states the inputs required, the work sequence, deliverables, proof link, scope caveats, and a low-friction next step.

Bad Example

The service page promises growth, lists capabilities, and asks for a call without defining outputs or evidence.

Agent Instructions

Map every offer claim to source evidence before polishing copy
Keep scope caveats near benefits
Link proof and contact routes
Run qa:fixtures after changing route structure

QA Gates

npm run qa:fixtures
npm run qa:seo
npm run qa:aeo

Completion Criteria

Inputs and deliverables are explicit
Proof and next step are visible
Schema obligations match visible facts