01 / 05 Work
Selected work.
Three systems in production, each built end to end by the same small team and still running today.
02 / 05 Case 01 rigveda.live
A living edition of the Rigveda.
The brief. Publish a hymn-by-hymn edition of the Rigveda with Sanskrit, transliteration and translation, plus long-form research essays, in a form that will remain readable and fast for decades.
What we built. A static publishing platform with full-text search, a citation and diagram pipeline, and an editorial workflow that validates each new essay and publishes it without a code change.
- Every page served from Cloudflare's edge with no server to maintain
- New essays published by editors, not engineers
- Zero hosting cost beyond the domain
Scholarship this old deserves a home that will outlast the hardware it runs on. Every hymn, every citation and every diagram loads instantly, and a new essay goes from draft to published without anyone opening a code editor. They built a library, not a website.
03 / 05 Case 02 bobbycarlsen.com
Grandmaster games, lived from inside.
The brief. Turn a chess coach's way of teaching, narrating a game from inside both players' heads, into a platform that could publish a new game every week and sustain a paying membership.
What we built. A membership platform with payments and a member request queue, an engine-verification step that checks every published line, and a scheduled content pipeline that produces and validates each new game.
- Every analysis line verified against a chess engine before publication
- Members request games and are notified when they go live
- A new game ships on schedule without manual effort
I have read annotated games for thirty years. This is the first time I have felt what it is like to sit on both sides of the board at once. Because every line is engine-verified, I can put it in front of my students without checking it myself.
04 / 05 Case 03 Day Spring Associates
Inventory across every location, on one screen.
The brief. Day Spring Associates managed stock across multiple locations with spreadsheets and phone calls. Month-end took a week, stock-outs were discovered by customers, and nobody could say who had changed a figure.
What we built. An inventory management system covering stock, purchases, sales and transfers, with role-based access for owners, managers, store staff and accountants, reorder alerts, a full audit trail and one-click month-end reports. Deployed to their own cloud account with backups and a runbook.
- Month-end close reduced from a week to a morning
- Reorder alerts raised before stock runs out
- Every change attributed to a user and a time
We used to close the month with spreadsheets and phone calls. Now stock across every location is one screen, reorder alerts arrive before we run out, and the audit trail has settled more than one argument. They understood our business before they wrote a line of code.
05 / 05 Contact
Your system could be the next case study.
Tell us what it should do, who will use it and when you need it. We reply within one working day.