The lead story · Vol. II · Edition No. 012
Every artifact a business pays for is one of two things. A deliverable is finished the day it ships and worth slightly less every day after — the website that ages with its framework, the campaign that ends, the deck that gets one meeting. A system is the machine that produces deliverables: the design language that generates a decade of pages, the measurement that makes every claim honest, the decision that never has to be argued twice.
This publication documents the second kind of work. Not portfolios of endings — investigations into how digital systems get made: the business context, the evidence, the decisions, the trade-offs, and the honest record of what happened. Every claim carries its evidence level. Every project carries its nature. Nothing is deleted to flatter the timeline.
Editor's note
Why a studio publishes
2026-07-02
Most studios keep two sets of books: the polished story told to prospects, and the real one — the decisions, the dead ends, the things that didn't work — kept private. The gap between the two is where trust quietly leaks.
This publication is our decision to keep one set of books, in public. Every project enters the register when it becomes real, not when it becomes flattering. Every claim carries its evidence level. Every edition adds to a record that nothing is ever deleted from.
We publish because documentation is how we work anyway — the writing you read here is compressed from decision logs and filed research, not composed for marketing. Making it public just holds us to it.
Read it the way you'd read any publication worth twenty minutes: slowly, skeptically, and with the understanding that the argument matters more than the adjectives.
— Prithviraj
Founding editor, XConversionLab
Recently published
The complete archive →From the journal
2026-05-14 · 2 min
Mobile isn't a breakpoint. It's the room where the decision happens.
Why we design the phone experience as its own product — and what changed when we stopped shrinking desktops.
design · mobile · conversion
2026-04-02 · 2 min
Measured, observed, judgment: why every claim on this site carries a tag
A three-word vocabulary that makes never-fabricate enforceable — by humans, by tooling, and by the reader.
honesty · measurement · portfolio
2026-03-10 · 2 min
Deliverables decay. Systems compound.
The four-word thesis behind everything the studio builds — and the sorting function it gives every project decision.
philosophy · systems
Field note · 2026-06-24 · engineering
Boring is a feature
Reviewed a two-year-old single-file client build this week: zero dependency updates owed, zero framework migrations pending, still deploying in seconds. The exciting stack we almos… read in the ledger →
Field note · 2026-06-11 · method
The out-list prevents more disputes than the contract
Every scope ledger we write has two columns, and the second one — what we will *not* build — does more work than the first. "In scope" sets expectations; "out of scope, explicitly"… read in the ledger →
Studio notes
“A studio can claim systems thinking in its copy; it can only demonstrate it in its structure.”
— from the studio's operating principles · how the studio thinks
Correspondence
Bring us the problem, in your own words.
Your first message becomes the first entry in your project's permanent record. We reply within two working days. — XConversionLab
Start a conversation