Drawer 03 · Case records— the back of every sheet

Systems we built
and still run.

Most software companies publish a wall of client logos. A logo proves nothing — it survives long after the work has been replaced, and nobody can check it. This page publishes URLs instead. Open any of them, on your own phone, right now, and judge the work yourself.

How to read these

Every figure below is real and rounded. Session counts are orders of magnitude, not marketing numbers — if we could not stand behind a figure in a meeting, it is not on the page.

Each written-up record names something that went wrong: a taxonomy agreed too late, a data type chosen badly, an interface rebuilt after we watched people struggle with it. Those sections are the point. A studio that has genuinely shipped can tell you what it got wrong; a studio that has not, cannot.

What you will not find here is downtime reporting or anything a client would not want published about their own business. The record stops at engineering choices.

In production8 systems, 4 with a full engineering record

Open any one of them and check.

SMM — Superhard Material & Machinery — screenshot of the live site built by Narvyn Technologies

Manufacturing

SMM — Superhard Material & Machinery

Corporate platform for a precision tooling manufacturer — product families, technical catalogs, capabilities and quote workflows.

Built with
Next.js 14 (App Router) · TypeScript · Tailwind CSS · PostgreSQL · Nginx on a single VPS
Timeline
7 weeks, discovery to live
What it carries
9 product families, ~120 catalogue entries; 30–60 quote requests a month; roughly 2,500 sessions a month, about half from search

Related: websites for manufacturers

Narvyn International School — screenshot of the live site built by Narvyn Technologies

Education

Narvyn International School

Admissions-first school platform with academics, facilities, gallery, prospectus downloads and campus-visit booking.

Built with
Next.js 14 (App Router) · TypeScript · Tailwind CSS · PostgreSQL · Object storage for media
Timeline
5 weeks, discovery to live
What it carries
About 400 gallery images and a dozen downloadable documents; enquiries run in the low tens per day, peaking through the January–March admissions window

Related: school fee management software

Nexus Precision Tooling — screenshot of the live site built by Narvyn Technologies

Industrial B2B

Nexus Precision Tooling

Industrial catalog and enquiry platform for carbide cutting tools — 180+ SKUs, engineering enquiries and WhatsApp flows.

Built with
Next.js 14 (App Router) · TypeScript · Tailwind CSS · Typed catalogue modules · schema.org Product structured data
Timeline
4 weeks, discovery to live
What it carries
180+ SKUs across 6 tool families, each with its own page; around 1,800 sessions a month; most enquiries arrive on WhatsApp rather than the form

Related: B2B catalogue websites

Royal Events & Planners — screenshot of the live site built by Narvyn Technologies

Events & Hospitality

Royal Events & Planners

Luxury event-planning showcase with services, gallery, packages and consultation booking.

Built with
Next.js 14 (App Router) · TypeScript · Tailwind CSS · GSAP · Build-time AVIF/WebP image pipeline
Timeline
3 weeks, brief to live
What it carries
Around 220 photographs across gallery and package pages; roughly 900 sessions a month, close to 70% on mobile

Related: brand and booking websites

The patternwhat four records have in common

Small, boring, and still standing.

Read the records together and the same shape keeps appearing. None of these systems is architecturally exotic. There is no queue nobody needed, no microservice split across a two-person team, no CMS bolted onto a catalogue that changes four times a year. Most of them run on a single server behind Nginx, which is the correct answer for a business doing a few thousand sessions a month and the wrong answer only in a pitch deck.

The decisions that actually mattered were unglamorous. Write the enquiry to the database before you try to email it, so a mail outage costs a delayed notification instead of a lost lead. Give every SKU a real URL, because buyers search for a grade and a diameter rather than a category. Do the image resizing once at build time, because the person opening the gallery is on a mid-range Android over mobile data and cares about that far more than about any animation.

The mistakes rhyme too, and all of them are the same mistake: a structural question answered too late. A product taxonomy agreed in week five instead of week one touched every URL on the site. Grade and tolerance stored as free text became a migration the moment anyone wanted to filter by them. An editing interface designed for people comfortable with forms had to be rebuilt plainer after we sat with the office and watched. None of these were coding errors. They were questions we could have asked during discovery and did not.

That is why our discovery stage now looks the way it does, and why the enquiry form on this site is a scope sheet you mark up rather than a blank message box. If you want the commercial half of the same argument — what moves a quote up or down, and what sits outside it — that is on how we cost a build.

Want your system on
this page next?

Tell us what breaks in your week. We will tell you honestly whether it is a software problem, and if it is, what a fixed written quote would cover.

no commitment required · we reply within 24 hours