Structuring company services starts with the situation that brings a customer to you, then groups related work into understandable routes. Explain what needs deciding, building or improving, with scope and outputs under each route rather than giving every capability equal prominence.
Start with the business situation
Why does the customer approach you? To launch a company, rebuild an existing presence or improve growth after launch? These situations create understandable routes even when some deliverables overlap.
Identity, a website and photography could support either a new launch or an established company’s rebuild. The starting point and decisions differ, even if some final assets are similar.
Group capabilities around clear responsibility
A direction stage might cover the offer, positioning and messaging. Building can include identity, corporate content, a profile, website and launch materials. Improvement can cover content, marketing, customer experience and systems when needed.
Grouping is useful when it explains the relationship between the work. Avoid broad labels that leave buyers guessing. Describe who each route serves, the problem, likely outputs and how scope is agreed.
Separate capability from agreed scope
A capability listed on the site is not automatically included in every project. Explain that deliverables depend on the need, timing and available inputs. This communicates breadth without promising everything in one engagement.
Do not lead with technology when the customer first needs a clear company offer and website. CRM and automation can follow when there is a defined operational problem to address.
Test the structure with a buyer
Ask someone from the intended audience to choose a starting route and describe what they expect. If the titles require a lengthy explanation, simplify them or reconsider the grouping.
Should individual services disappear? No. Explain them within the relevant route and detail page. The aim is to show their relationship to the customer’s need before presenting production detail.
Three levels that clarify the offer
| Level | What it explains | Illustrative example |
|---|---|---|
| Engagement route | The wider reason for working together | Building a company presence before launch |
| Capability | The kind of work used to support it | Writing content or developing a website |
| Deliverable | What the client receives under the agreement | Approved page copy or a defined website |
Mixing these levels places “writing a paragraph” alongside “launching a company presence” as equivalent services. A paragraph can be one output within a larger engagement or a separate assignment if that fits the offer. Explain the relationship and responsibility so buyers understand the discussion.
What if a capability belongs in several routes?
Describe it where it is relevant, while maintaining a consistent definition and scope. Photography might support a new launch or an existing presence update. The production goal, shot list and inputs can differ while the description of the capability remains accurate.
Test the structure using two hypothetical buyers: a new company needing foundations and an established business updating old materials. Can each find a starting point without knowing your tools? Can they distinguish consulting from delivery?
If the choice remains unclear, review titles and descriptions before adding another route. More sections do not necessarily communicate a broader offer; detail can sit inside route pages. Use consistent names across the website, profile and proposal, and define actual deliverables in the project scope.
Review whether your offer moves from decisions, to building, to improvement. That sequence makes scope easier to discuss.
Continue with: Value proposition: explain why a buyer should choose your company · Direction and strategy
