platform Case study
Freshca Canada
A Canadian retail and service business needed a site that explains what it offers quickly and makes the next step obvious. The work was presentation and structure, not platform engineering. Scoping it that way was the right call.
The business problem
The business needed a credible online presence: its services clearly presented, and a path toward enquiry. The risk on a project this size is over-building. You hand the client a system they cannot maintain and do not need, at a cost that never pays back.
What I delivered
- A service-led site structure that shows what the business offers before it asks for anything.
- Pages built toward enquiry, with the next step available at every point rather than only at the end.
- A responsive build, since most of this audience arrives on a phone.
- A structure the client's own team can extend without development work.
Technical approach
- I agreed the scope against what the business actually needed, instead of pitching a platform build for a site that did not require one.
- I kept the build close to standard, well-understood patterns, because the client's team maintains it after handover.
- I treated content structure as the main design problem. Navigation decides whether a visitor finds what brought them.
- I added nothing the owner would need a developer to change later.
Result and evidence
The business now has a site that presents its services clearly, points visitors toward contact, and stays maintainable by its own team.
Commercial value
For a business this size, a site succeeds if it still reflects the business a year later without a developer touching it.
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
Clients judge site work on whether they can still operate the site after handover. That constraint shapes more decisions than any visual one.
Scoping a project down to what it actually needs is worth more to a client than selling the largest version of it.