platform Case study
Freshca Canada
A Canadian retail and service business that needed a site which explains what it offers quickly and makes the next step obvious. The work was presentation and structure rather than platform engineering, and scoping it that way was the right call.
The business problem
The business needed a credible online presence with its services clearly presented and a path toward enquiry. The risk on a project this size is over-building: delivering a system the client cannot maintain and does not need, at a cost that never pays back.
What I delivered
- A service-led site structure that presents what the business offers before it asks for anything.
- Page architecture oriented toward enquiry, with the next step available at each point rather than only at the end.
- A responsive build, since the majority of this audience arrives on a phone.
- A structure the client's team can extend without development work.
Technical approach
- Scope was agreed against what the business actually needed, rather than proposing a platform build for a site that did not require one.
- The build stays close to standard, well-understood patterns, because the client's own team maintains it after handover.
- Content structure was treated as the primary design problem, since navigation decides whether a visitor finds what brought them.
- Nothing was added that the owner would need a developer to change later.
Result and evidence
The business has a site that presents its services clearly and leads visitors toward contact, and that its own team can maintain.
Commercial value
For a business this size, the measure of a successful site is whether it still reflects the business a year later without a developer being involved.
Readable implementation brief
implementation_brief {
project: "Freshca Canada"
type: "service and retail presentation site"
focus: "service clarity + enquiry-oriented page structure"
audience: "Canadian market, mobile-first"
constraint: "maintainable by the client without a developer"
scope_decision: "presentation and structure, not a platform"
}What this project shows
Client site work is judged on whether the client can still operate it after handover. That constraint shapes more decisions than any visual one.
Being willing to scope a project down to what it actually needs is worth more to a client than proposing the largest version of it.