Signal Strength
Dimension 10
Improving Offering Architecture
Can people and machines clearly understand what the organization offers and how offerings relate?
What this dimension measures
Offering Architecture evaluates how products and services are named, grouped, described and priced — whether the offer set forms a coherent taxonomy that a buyer can navigate and a retrieval system can parse into distinct, recommendable items.
Why it matters
- An assistant can only recommend an offer it can isolate. Undifferentiated service prose resolves to a category, not a product.
- Buyers compare before they contact. An offer described only in a conversation is absent from the comparison.
- Structured offers are the difference between being listed among options and being summarised as one more supplier.
What strong looks like
- Each offer has its own page, its own name and a one-sentence definition that stands alone.
- Scope, inclusions, and either price or a stated pricing basis are visible without contact.
- The offer set forms a visible hierarchy — tiers, packages or lines — with the differences stated.
- Product, Service or Offer schema matches the visible content on the page.
Common failures
- A single services page listing capabilities in prose, with no individual offer pages.
- Names that mean nothing outside the organization, with no plain-language equivalent.
- No price, no range and no basis — leaving the buyer unable to qualify themselves.
- Overlapping offers with no stated difference between them.
Relevant professional practices
Product marketing and information architecture. These are reference disciplines and evidence inputs — they are not separate scores.
- Offer taxonomy practice
- Pricing page conventions
- schema.org Product, Service and Offer
Practice lens: Product & Journeys
Who typically owns it
How Brand & Signal evaluates it
- Whether each offer is separately addressable at its own URL.
- Clarity and consistency of offer naming across the site and external profiles.
- Presence of scope, inclusions, outcomes and pricing basis.
- Structured data describing offers, and whether it matches the visible page.
- How accurately AI assistants can list and differentiate the offer set.
- Score 3
- One prose services page; offers cannot be told apart or addressed individually.
- Score 5
- Offer pages exist, but naming overlaps and scope or pricing basis is missing.
- Score 7
- Each offer has its own page with scope and pricing basis, in a clear hierarchy.
- Score 9
- The offer set is a clean taxonomy, marked up and reproducible by an assistant on request.
How to improve it
- Give every distinct offer its own page with a standalone definition sentence.
- State scope, what is included, what is not, and the pricing basis.
- Apply Offer, Service or Product schema that matches the visible content.
- Retire or merge offers that cannot be told apart in a sentence.
Test it yourself
- Ask an assistant to list your services and compare the answer with your own list.
- Check whether each offer has a URL you could send on its own.
- Look for scope, inclusions and pricing basis on each offer page.
- Validate your Offer or Service structured data against the visible content.
Evidence and sources
- Service, product and pricing pages
- Navigation and offer taxonomy
- Offer, Service and Product structured data
- AI assistant descriptions of the offer set