platform Case study
Saboksaran
Construction businesses accumulate content: projects, services, capabilities, references. A site designed only for what exists at launch is one that becomes disorganised within a year, which is exactly when it starts mattering.
The business problem
The immediate need was a clear presentation of services, but the real constraint was growth. Completed projects and new capabilities arrive continuously, and a structure that only fits the launch content forces either a rebuild or a site that gets steadily messier.
What I delivered
- A page architecture designed for content that accumulates, particularly project and service records.
- Clear service presentation aimed at the client type the business actually works with.
- A scalable content structure so new projects fit into the existing organisation rather than being appended.
- A build the business 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 structure that stays organised as projects and services are added, rather than one that degrades with use.
Commercial value
A construction firm's completed work is its strongest sales asset. The site has to be able to absorb it as it arrives.
Readable implementation brief
implementation_brief {
project: "Saboksaran"
type: "construction business platform"
design_target: "the content that has NOT arrived yet"
grows_with: "completed projects, services, capabilities"
structure: "new work slots into the organisation, not
appended to the end"
constraint: "extendable without development work"
}What this project shows
Designing for the content that has not arrived yet is the difference between a site that lasts and one that needs redoing in eighteen months.
It is also the thing a client cannot evaluate at handover, which makes it the developer's responsibility to get right unasked.