Websites · Design concept
Editorial consultancy — B2B website design
A B2B technology website concept for service scope, system connections and a project enquiry, using stone surfaces, charcoal type and muted cyan.
Design concepts, not client projects. Screens are static mockups; names and data are illustrative.
The design brief
A calm service direction for conversations about connected operations.
- Designed for
- Operations managers and technology stakeholders assessing a software or integration provider.
- Constraints to consider
- The service story needs room, while system labels and a project enquiry must remain easy to find. The screens are illustrative and do not connect to live systems or submit a real project request.
The proposed journey
- 01
Service landing
A buyer-led introduction to service areas and the current operational problem.
- 02
Integration scope
A simple current-to-connected-system view makes the proposed discussion concrete.
- 03
Project enquiry
A short brief captures systems and intended change, with a visible required-field state.
Why these design choices?
Design decision 1
A single connection diagram turns an abstract service into a discussion about existing systems.
Design decision 2
Muted cyan marks the next action and system hand-off, rather than decorating the page.
A closer look at the visual system
Proposed design specimens. These are static examples, not working controls or a production specification.
Colour roles
Stone canvas
#F3F0E8
Charcoal structure
#292B2A
Connection cue
#147D96
Typography & spacing
Clear information. A considered next step.
Use measured serif headings with a neutral sans-serif for scope labels, diagrams and form fields.
Use broad margins for the service story; keep system labels and the related enquiry action close together.
Beyond the ideal state
Scope not yet defined
Not sure which service fits? Describe your current systems and the change you need.
Enquiry ready
Your project outline is ready to review. Check the contact details before sending.
Missing project context
Add a short description of the system or workflow you want to discuss.
Why put the system map beside the service story?
A buyer can relate the proposed work to existing systems before discussing scope. The spacious layout gives service explanations more room, but shows fewer details at once than the compact navigator design.
