Skip to content

Blog

Field notes

Practical writing on AI-native development — what actually works, what breaks, and what we'd do differently.

A queue of waiting review cards on the left, and a phone receiving a direct download on the right, connected by a dotted line.

October 28, 2026 · 5 min read

The App Store Can Wait: Shipping a Mobile Beta as a Direct Download

Your first mobile users don't come from a store search — they come from a conversation. Why a private beta distributed as a direct download beats fighting the review queue on day one, what you give up by skipping the store, and the four things to get right before you send anyone the link.

mobileprivate betadistributionfounders
A cloud of amber question marks and a fuzzy dollar figure passes through two document gates labeled Discovery and Planning, emerging as a green-checked price tag: a number you can sign

August 17, 2026 · 7 min read

Where Budgets Die: The Gap Between a Definition and a Plan

Every build starts with “how much will it cost?” asked while the product is still a conversation — and the answer comes back either padded or lowballed, because fog gets billed either way. Why top-down quotes can’t be honest, what a bottom-up estimate actually requires, and the founder-side checks that tell a real number from a bet wearing a suit.

planningbuild estimatesfoundersproduct strategy
Six asset keys — code, cloud, domain, data, services, credentials — move from a dim stalled agency card to a bright verified founder card, over a delivery cadence line that continues unbroken

July 20, 2026 · 7 min read

Switching Development Agencies Mid-Build: How to Leave Without Losing Your Product

Founders stay in stalled engagements because leaving feels like losing the product — the code, cloud, domain, and credentials all sit on the agency's side of the table. The six assets to verify before you give notice, why the notice period is not a handover, and the order of operations that keeps your timeline from resetting to zero.

agency transitionstalled buildsfoundersbuild audit
A rising dashed 'reported progress' line pulling away from a row of six weekly demo checkpoints — small window cards each with a green check, labeled 'what actually runs, demoed every seven days' — with the shaded space between them marked 'the gap a build drifts in'.

July 9, 2026 · 5 min read

The Weekly Demo: The Cheapest Insurance Against a Build That Drifts

A build rarely fails on a single bad day — it drifts, in the gap between what gets reported and what actually runs. Why a weekly demo of clickable software is the cheapest instrument for closing that gap, what separates a real demo from status theater, and the founder discipline that makes it work.

weekly demosdeliveryfoundersproduct strategy
Illustration: a half-built structure of blocks — some solid, some fragile, some missing — passes through a Build Audit and comes out the other side kept, fixed, and finished

July 8, 2026 · 7 min read

Salvage or Rebuild? What to Do When Your Software Build Stalls

A stalled build presents itself as three bad options — keep paying, start over, walk away — each framed by someone with a stake in the answer. Why the rebuild reflex is usually the second mistake, and how a component-by-component audit turns the worst decision on your calendar into an informed one.

build auditstalled buildsfoundersproduct strategy
Two misaligned product sketches pass through a discovery lens and emerge as one clear, written product definition

July 7, 2026 · 6 min read

Why Product Discovery Matters: The Two Weeks That Decide Your Whole Build

Most software builds fail before the first line of code — signed on top of two different mental models of the same product. Why a short, structured discovery phase is the highest-leverage money in your build, what it should produce, and how to tell real discovery from a sales pitch in disguise.

product discoveryfoundersmvpproduct strategy

Newsletter

Field notes, straight to your inbox

Occasional, practical writing on AI-native development. No spam, unsubscribe anytime.