smallbox

Proof in production

Two systems we built and run.

Two production platforms designed, built, and operated end to end — backend, frontends, infrastructure, data pipelines, content. Everything the offer promises already runs here.

CompanyGraph

Stock-analysis platform built around one rule: describe structure, never predict.

Hundreds of observation & interpretation definitions · ~14,000 companies daily · .NET 9 + Next.js + PostgreSQL

companygraph.me

View case →

Gamified financial-literacy platform

Gamified financial-literacy platform where complex interacting business rules are verified by simulating weeks of student activity through real production code.

~196 domain entities · 14 projects · 45-day simulated baseline

View case →

Built with a founder.

Someone else’s idea, built into a running product together with its founder, and handed over so the founder can carry on.

Knowledge assistant for work instructions

A founder's idea and prototype, turned into a running product with its business, its release pipeline and its handoff: two days of design, eleven days of building.

Hosted and self-hosted from one release · five kinds of document source · Danish and English · Python, PostgreSQL with pgvector, Next.js

View case →

Built to make films.

A production pipeline for animated films, built for our own YouTube channel: a person brings the subject, and the pipeline turns it into finished videos for YouTube and the short-video platforms.

Video production pipeline for a YouTube channel

The pipeline behind our YouTube channel, Structure & Flow: a person brings the subject and approves each step, and AI does the writing, the drawing, the animation and the voice. Its first run made a 17-minute film, eight chapter videos and four Shorts.

A 16:57 film in 4K · eight chapter videos · four Shorts · Remotion, React and TypeScript · Claude, Codex and ElevenLabs

View case →

One pattern at a time.

Narrower cases — each takes one production pattern or one decision and shows it concretely, at the scale it actually runs.

Batch service & lifecycle visibility

Background work as production engineering: every batch job has a visible lifecycle, prioritization, and idempotent semantics.

View case →

Integration testing → DB-per-test, real layers

Behaviour verified by simulating real usage, freezing the resulting database, and replaying it through the same code that runs in production.

View case →

Structured Data → Knowledge Surfaces

Turn entities, relationships, and classifications into useful pages, graphs, and explanations. AI enriches typed fields. It does not write prose.

View case →

MVC monolith → REST API + modern frontend

Migrating a long-running ASP.NET MVC application to a REST API + Next.js frontend, page by page, never big-bang.

View case →

Legacy MVC replacement: gradual extraction or controlled twin?

A synthetic case study. NaboWorks A/S, a 12-year-old ASP.NET MVC service marketplace, and the modernization decision a System Report has to answer before any code is written. Detailed reference document for the companion sample report.

View case →

A picture book of companies

Every company in CompanyGraph, rendered as a story page by the CMS and image service — a hero image bound to each, a one-line structural reading underneath.

Open the picture book →

Your product, started in this shape, is what Prototype to Product delivers.

See Prototype to Product →