Illustrative service-fit completion
Baseline: 51%
+32 percentage points
Web / Case 03
A studio website that gets to the point.
A fictional service website that connects a clear scope, evidence-rich work and an honest inquiry handoff.
Role: Content strategy, responsive design and prototype implementationFive-week fictional conceptPermission reviewed
The challenge.
The original studio concept led with abstract statements and a long gallery. A visitor could see visual quality but struggled to understand which service fit, what the studio delivered and how to start a useful conversation.
Constraints
- Service examples must preserve client permissions.
- The delivered contact form produces a local draft and sends nothing.
- The prototype must work without remote fonts, analytics or image services.
The approach.
Write the service choices and inquiry questions first. Connect each service to a complete case study, make the next step explicit and test the actual narrow layout with keyboard navigation.
Name the scope before the gallery
A visitor should understand the service decision before seeing a collection of images. The fictional walkthrough frames this content problem.
Sources: relay-study
Connect outcomes to process
Full cases describe constraints, decisions and source boundaries. They avoid implying that visual polish alone proves effectiveness.
Sources: relay-study, relay-pilot
Make inquiry behavior honest
A static prototype validates the fields and creates a contact draft. It should never claim that an email was delivered without a connected and tested backend.
Sources: relay-study
Make the change visible.
Original interface studies illustrating the reviewed decisions. They are not customer screenshots.
Before: Broad claims and project tiles leave the service choice unclear. After: Service context leads to full evidence-rich cases and a contact draft.
Results, with their boundaries.
Illustrative scope-finding time
Baseline: 3.2min
-50.00% relative change
All numbers in this fictional example are illustrative; they are not evidence of real uplift.
What I learned.
A website becomes more convincing when the visitor can trace a service promise into a concrete case and a realistic next step. Content structure did more work than decorative density.
The next question
Replace the fictional work with permitted sources, connect a reviewed inquiry backend and test completion with a real audience before reporting results.
Evidence register
- Illustrative website usability figures [fictional]
Task completion and time values are fictional examples used to validate delivery calculations. - Fictional service-page walkthrough [fictional]
An authored example of a studio visitor trying to understand service scope and a next step.