Most B2B service websites are org charts with stock photography. Practice names become nav items. Twelve tiles say the same paragraph. The homepage cannot name what you sell. Buyers trying to put work on a statement of work leave.
Offer architecture is the work of making the public page set match how the firm actually sells: which engagements you take, how they are packaged, and which URLs a salesperson would put in an email.
This is market-facing work for Accumentum Digital. It is not a course catalog. Keep training offers on the training brand if they exist.
Offers are what you will take, not what sounds complete
Brand strategy and positioning decides the allowlist. If you will not staff a type of work this year, it does not get a page. Inflating the nav to look larger creates junk pipeline and internal arguments.
An offer is something you can scope:
- A named problem you take ownership of
- Inputs you need
- Outputs you produce
- A delivery model (project, retained, embedded, hybrid)
- A first engagement that is real
A capability adjective is not an offer. “Excellence,” “transformation,” and “end-to-end” are not pages.
Navigation should follow evaluation, not reporting lines
Website strategy, UX, and development should organize around how a buying team researches:
1. Homepage: category, buyer, primary offer 2. Services hub plus one unique child URL per real offer 3. Industry or environment pages only when delivery changes 4. Approach: how you start, staff, and finish 5. Proof next to the offer 6. Insights as posts with permalinks 7. About and contact
If your internal practice leads do not map to buyer language, do not put their names in the menu. Translate.
Service pages that cannot be swapped
Duplicate Elementor sections with a new H1 are one page to a crawler and one shrug to a practitioner. Content strategy has to make each URL distinct:
- Problem statement the buyer already feels
- Scope and boundaries
- Who it is for and not for
- Proof pattern specific to that work
- The same primary CTA: request the assessment
If you can hide the titles and nobody can tell the pages apart, delete or rewrite until a service owner will defend the difference. Assign that owner before drafting.
Packaging is part of architecture
How you sell should show up in the page, not only in a proposal. If the first engagement is a diagnostic, say so. If you do not publish rates, you can still describe packaging: fixed diagnostic, scoped project, retainer. Hiding the commercial model entirely forces every visitor to book a call to learn they are in the wrong motion.
Do not invent productized names for work you still sell as custom labor. Do not pretend a consultancy is self-serve SaaS.
Search and AI need the same map
SEO, GEO, and organic growth fail when the only unique copy is the homepage and a static Insights page with unlinked cards. Unique, indexable service URLs with Rank Math titles, self-canonicals, and internal links are the ranking system.
Do not create a page for every keyword variant. Create a page for every offer a salesperson would send. Insights should deepen one argument and point back to the offer, not invent a seventh practice.
Architecture is a revenue constraint
Demand generation and revenue enablement cannot fix a site that teaches six stories. Campaigns land on the wrong tile. BD uses a deck that disagrees with the hub. The committee never converges.
Use service pages as the canonical offer text. Tag inquiries by URL. When the offer changes, update the page. When a practice is retired, redirect. Treat the architecture like a living SOW.
A practical sequence
Do not start in Figma.
1. List engagements you will take this year 2. Collapse synonyms into the fewest honest offers 3. Write unique service and proof copy 4. Wire one conversion path to /contact/ 5. Publish Insights that support those offers 6. Then design
Redesigning first usually encodes the current confusion in a nicer layout.
Checklist
- Can a new visitor name the primary offer after one screen?
- Does each service URL survive a title-swap test?
- Would sales send the page instead of a slide?
- Do Insights exist as live URLs linked into services, about, and contact?
- Are you avoiding fake metrics, training cannibalization, and review widgets?
What happens when architecture and sales disagree
The cost is not aesthetic. A champion forwards a service page. The call uses a different package name. Procurement asks which URL is canonical. You spend the first meeting translating yourselves.
Write the architecture down as a one-page map: offer, URL, owner, first engagement, CTA. If a row has no owner, it is not an offer yet. If two rows share the same paragraph, they are one row. That document is what services should implement, not a brainstorm in Figma.
Email questions to info@accumentum.net if you want a second pair of eyes on that map before you rebuild templates.
What to do next
If the firm sells one way and the website sells another, pipeline will stay noisy. Accumentum Digital can assess offer architecture, page uniqueness, and the path to a conversation.