Product — Build-in-public agent
Bippid
Your build-in-public agent — it turns the work you actually did into a daily post.
- Role
- Founder — design & product engineering
- Discipline
- Product Design
- Focus
- Brand, Product Engineering
- Status
- Live product
01The problem
Building in public works, but writing about it is a second job. The work that would make the best posts — the commits, the decisions, the fixes — rarely makes it out, because turning a day of building into a post costs time you would rather spend building.
02Key decisions
- 01
Bippid reads the tools you already use — GitHub, Linear, Figma, Slack and Notion — and only the ones you switch on. Setup is picking your sources once, not filling in a content calendar.
- 02
Nothing posts itself. Each draft is shown exactly as it will appear, and you copy it and post it yourself. Keeping a person in the loop was a product decision rather than a limitation: it is what makes the output safe to put your name on.
- 03
Every draft is built from the day's real signals and shaped as a hook, a detail and a takeaway, so it reads like something a person noticed rather than a summary of activity.
03How it’s built
- Product
- Next.jsNestJS
- Data & auth
- Supabase AuthPostgreSQL (TypeORM)Redis + BullMQ
- AI
- Gemini, fast tier for triageGemini, strong tier for the post
- Integrations
- GitHub AppLinearNotionFigmaSlackLinkedIn
- Marketing site
- ViteReact 19Tailwind CSS v4Motion
- 01
A post can't invent work. Every sentence the model writes has to cite the real activity it came from, and code drops any sentence whose citation doesn't match something that actually happened, before the draft ever reaches you.
- 02
Two model tiers, each where it earns its cost. A fast tier triages activity in batches (one call per batch, not per event) and keeps a running draft that can extend, ignore, or flag a contradiction for you to resolve. One call to a stronger tier writes the day's post.
- 03
The daily compile streams its real progress (syncing, found, selecting, writing, checking) over Server-Sent Events, with keep-alives so the hosting proxy holds the connection open, and each sentence shows up only once it has passed validation.
- 04
The seams are hardened: the API verifies Supabase sessions locally with no network round trip, and OAuth callbacks carry a signed state token, so a tool connection can't be attached to someone else's account by editing a URL.
04Outcome
Live, with a free plan: connects GitHub, Linear, Figma, Slack and Notion, and drafts a LinkedIn post and an X post every weekday.