Overview
| Client | SpaceSJ Lab - this website — In-house build / in production |
|---|---|
| Industry / Technology | In-house / Web |
| Period | From Jul 2026 (10-week plan) |
| Scope | Strategy | IA | design | engineering | answer-engine work - all in-house |
| Stack | Next.js, TypeScript, Headless CMS, in-house RAG engine |
| Disclosure grade | L3 In-house |
What was the problem?
When a software firm outsources its own website, it invites the obvious question: if they cannot build their own, what will they build for us? Building it in-house turns that question into the cheapest reference we own.
Why this approach?
We designed it as an evidence dossier rather than a handsome company introduction. Evidence sits above claims in the hierarchy, the numbers appear on the second scroll, and the assistant is embedded as a working product demo rather than described in prose.
What we built
- 01Evidence-first IA - every unverifiable adjective removed
- 02First of four living demos shipped: the advisory assistant
- 03Schema.org, llms.txt and question-form H2 structure
- 04LCP 2.5s / INP 200ms / CLS 0.1 as release gates
Before to After (measured in-house)
Clicks to a conversion point
4 avg
2 max
Pages with structured data
0
all
FAQ entries per solution
0
6-7
Mobile LCP (target)
-
under 2.5s
Figures were measured on the same basis before the engagement and after go-live, and the calculation records are retained.