Digital Engineering Agency · Self-build · 2026
Neopraxis
The hardest client we've taken on is ourselves.
Digital Experience · Search & Visibility · Security & Trust
Treated as a realengagement.
The brief.
Most agency sites are built in the gaps between paid work, and they look it. We decided ours would be treated as a real engagement — same template, same standards, same scrutiny we apply to a client.
The difference is that the client and the studio are the same people. No brief to misread. No stakeholder to blame. No hiding the parts that took three attempts.
The first version went up in late April. It was honest and it worked — but it was selling the wrong story.
The starting point.
The v1 language was small-shop. “Two engineers. Real accountability. No overhead.” True, and quietly limiting.
A visitor read “two friends with a project budget” while the work in the codebase was already operating at a different tier. The whole rebuild exists to close that gap.
Before a single component of the rebuild was written, one question had to be settled — what is this, exactly?
Strategic Direction
Lock the system. Then build.
Search Foundations
Engineered from the codebase. Not stamped per page.
Structured data, sitemaps, canonicals — generated from one source, regenerated from the routes themselves. None of it glamorous. All of it the foundation the rest sits on.
Refinement
The system went up in days. The polish took the rest.
Two dozen changes in one window: the page-transition system, gradient passes, copy revisions across About and Contact. The logo alone cost a full day. The contact layer was rebuilt three times. First versions are never final.
Security
Quiet by design. Reassuring by detail.
Sensible response policies on every route. Form submissions filtered before reaching the inbox. Secrets out of the repo. The deployment pipeline treated as the security surface most sites forget it is. Security done properly is quiet — and the absence of incident is the deliverable.
The rebuilt site reads as what the work always was — an engineering practice, not two people with a project budget. The positioning and the execution finally tell the same story.
What shipped: a fully rebuilt site on a current stack, three services restructured from five with clean redirects, a six-stage process documented on the About page, four case studies on a consistent seven-section template, and search and security infrastructure built into the foundation rather than bolted on.
The most transferable lesson has nothing to do with the stack. The hard part of writing our own site wasn't writing it — it was editing it back from the version that sounded like an agency. Every copy pass fought the same instinct: cut the jargon a business owner won't decode, cut the line that dunks on competitors instead of explaining the buyer's risk, cut the clever metaphor that says less than the specific thing it replaced.
We treated ourselves as a client and held the line. That discipline is the actual deliverable — on this project and every one after it.
Treated as a client. Held the line. That discipline is the deliverable.
- Pages
- 14
- Logo iterations
- 7+
- Case study template
- 7 sections
The hardest client we've taken on is ourselves.
Digital Engineering Agency · Self-build · 2026 · Digital Experience · Search & Visibility · Security & Trust
Approach
The naming pass
Three framings were on the table, and each was rejected for a reason worth keeping on the record. “Visual Studio” — too passive, and it collides head-on with the Microsoft IDE for any technical reader. “Design boutique” — small-shop signal. “Editorial / photography studio” — described the aesthetic we like rather than the thing we sell.
What got locked instead: Digital Engineering Agency. Visual studios are everywhere. Agencies that can build the cinematic surface and the system underneath it are not. The positioning made the visual flex permissible — but only if it reads as engineered, not decorated.
The headline that came out of it survived the entire rebuild untouched: Build. Secure. Scale.
The locked system
The most important decision wasn't a design choice — it was a discipline. In a single planning pass, the entire system was locked before any UI was built: stack, typography, colour, motion staging, information architecture, and the case study template.
Each decision was small enough to make in an afternoon and load-bearing enough that revisiting it later would have cost a week. None of them got revisited. The month of build that followed was downstream of that one pass.
One display typeface
A monospaced face carries the display type and technical accents. Mono-as-display is the engineering tell — pairing it with a second display face would have diluted the one thing doing the work. So we didn't.
Colour with a job, not a mood
A five-step dark-surface ladder instead of one flat background. A single accent held throughout. A separate status tier reserved exclusively for literal security and system language.
Those colours never appear as decoration. When you see them, they mean something.
Motion in strict phases
Layout first. Smooth-scroll second. Scroll animation third. 3D held back to a single atmospheric layer that never owns the page or delays first paint.
The failure mode we were avoiding had a name: reads as someone who learned shaders last weekend, not as an engineering agency. The 3D stays on the bench until everything beneath it is stable.
Three services, not five
The earlier structure listed five disciplines. Performance and motion aren't separate products — they're part of building the site properly. Collapsing to three reads as a deeper practice, not a thinner one. Old URLs redirect, so nothing already indexed broke.
When the application work needed its own page, the easy move was to promote it to a fourth service. Instead it's nested under Digital Experience Engineering. Three services, not four. The doctrine held because we made it hold.
Foundations
The site dogfoods the search and security work we sell. A search pitch on a site that ignores its own search foundations is self-defeating. The same goes for security.
SEO
Every page carries structured data appropriate to what it is — an organisation identity site-wide, service markup on each discipline, article markup on each case study — generated from a single source in the codebase rather than hand-stamped per page, so it stays correct as the site grows.
The sitemap and crawl rules regenerate from the routes themselves. Metadata, canonicals, and social previews are defined per page, not left to defaults. None of it is glamorous. All of it is the foundation the rest of the work sits on.
Process
The rebuild scaffolded fast and then spent most of its life in refinement — which is the honest shape of this kind of work. The system went up in a few days. The polish took the rest.
Roughly two dozen changes shipped in a single window: the page-transition system, gradient and calibration passes, copy revisions across About and Contact. First versions are never final, and the distance between “working” and “right” is almost entirely here.
The logo cost a full day on its own. Seven-plus iterations. We're naming it because it's the truth of the work, and because anyone who has done this knows the small marks take the disproportionate time.
When state, animation, and form submission all meet at the same moment — a user submitting a form mid-page-transition — the seams show. The contact form, mobile navigation, and page transitions were rebuilt three times in a day to behave correctly across every route. The result is a contact layer that holds under exactly the conditions that usually break it.
Security
We hold the same standard on our own site that we put in our own service slot — partly on principle, partly because a security pitch from a site that skips its own basics is worthless.
Sensible response policies are set across every route. The form submission path is protected so automated spam is filtered before it reaches us, not after. Secrets stay out of the repository. The deployment pipeline is the security surface most sites forget — ours is treated as one.
None of this is dramatic, and that's the point. Security done properly is quiet, and the absence of incident is the entire deliverable.