From scattered SaaS ideas to Eastbase Studio
How a scatter of unrelated side projects — a trip planner, a freelancer tool, an AI cost monitor — became one studio with a single way of building.
Eastbase Lab · Field notes
Build notes, product decisions, and engineering lessons from the Eastbase Studio lab — written as we build, not after.
How a scatter of unrelated side projects — a trip planner, a freelancer tool, an AI cost monitor — became one studio with a single way of building.
6All notes
Long-form build logs from each product under the studio, repurposed into shorter posts across X, LinkedIn, and Reddit. Filter by what you're after.
The awkward part of chasing a late invoice was never the wording — it's deciding tone in the moment. A four-rung follow-up ladder that keeps you polite longer and gets firm only when it's earned.
A verbal "we'll pay Friday" feels like progress — and quietly drops the thread. How to record a payment promise and follow up the next Monday without sounding like you're chasing a debt.
Integration code is written by agents now, not by hand — so BurnCap ships the prompt, not a quickstart. Why a prompt can be an executable spec, not just copy-paste.
How BurnCap keeps its own API costs and latency bounded with three cheap layers — and a Redis layer built so that losing Redis changes nothing.
BurnCap's Insights feature is the smart part of an AI cost tool — and it calls zero models. Why the most AI-native decision we made was choosing not to use AI.
AI products are cheap to prototype and unpredictable in production. Provider dashboards log the burn — none of them stop it. The first note in an open build log.