Your startup changelog,
maintained by your coding agent.

See what you shipped, what you’re trying to achieve, and what you’ve learned — without keeping another journal.Every finished unit is checked against one measurable aim. If it drifts, Founderlog tells you why and what to do next.

See how it worksFree · sign in with GitHub

Works with Claude Code · Cursor · any MCP client. Set up once per machine.

Illustrative log

Give a solo founder one screen that proves they are moving.

The aim · open

Make it something another founder can sign into

2 / 10 founders who can use it without me
Aim alignment · 7 days

4 of 5 entries assessed

58%

~40% of assessed effort does not appear necessary for this aim.

Next Ship onboarding before another infrastructure pass.

your move1
Turn on a Neon branch per previewblocking1d
next1–3 of 10
Publish the MCP to npm2d
Put lead time into the weekly review4d
Soft-delete projects2d late
Gave the log an MCP server so the agent keeps ittoday

logging should not interrupt the thing being logged

Rebuilt the MCP to talk HTTP, not Postgrestoday

it could read every account in the database

Built the next bandyesterday
Deployed to a real domainyesterday
4 quiet days
Turned off the free tier29 Jan

it was the whole problem

You shipped more than it felt like.

Founderlog turns completed work into visible progress, so you can see what moved instead of staring at another list of unfinished tasks.

It also checks whether each finished unit served your current aim. When the work drifts, it explains why and gives you one concrete correction.

Aim, work, and drift. One screen.

Open Founderlog and immediately see what you’re working toward, what shipped, and whether the two still match.

Current aim

What are we trying to achieve?

Keep one objective with a number that tells you when it is done.

The work

What actually shipped?

Your coding agent records each verified change, why it mattered, and what it taught.

Aim check

Does the work still serve the aim?

See aligned work, the main drift, and one highest-leverage next action.

Your coding agent maintains it.

When work is finished and verified, your agent logs what changed and why — without interrupting your workflow.

# illustrative agent run
$ claude
> ship the preview sign-in fix
⏺ founderlog_context
  past: 6 decisions · 3 retros · 2 settled bets
  open: Make it something another founder can sign into
  ⋯ forty minutes of work ⋯
✓ 43 tests passed✓ build clean
⏺ founderlog_log
  what: Scoped the screenshot sweep to one project
  why:  it was a delete across every account
  mark: snag
  alignment: drift · 28/100 · effort 3/5
⚠ This work does not appear necessary for the current aim.
  next: Ship onboarding before another infrastructure pass
⏺ founderlog_ask
  what:   Turn on a Neon branch per preview
  blocks: previews that can write
Illustrative · the aim is open
Moved the auth tables into their own schematoday
GitHub sign-in with Better Authyesterday

Everything it writes is tagged, so you always know which hand wrote a line. Headlines are capped at a hundred characters.

Start with the work you already shipped.

Ask your agent to read the repository’s history and turn past work into changelog entries.

›import my last 90 days

Founderlog creates one entry per shipped change, not one per commit. Imported entries are labeled and can be removed together if you want to start again.

Imported from git · illustrative412 commits → 38 entries
June
Split the log and its screenshots into two tablesimported18 Jun

they change at very different rates

Moved the auth tables into their own schemaimported11 Jun
Made a project id unguessableimported4 Jun

/p/3 invites you to try /p/4

6 quiet days
May
First commit — one table, one pageimported29 May

Connect your agent in two steps.

Add the MCP server once, then choose which Founderlog this repository should update.

01

Add it to your agent, once

$claude mcp add -s user founderlog \  -e FOUNDERLOG_URL=https://founderlog-one.vercel.app \  -e FOUNDERLOG_TOKEN=flg_… \  -- npx -y founderlog-mcp

Minted in the app and shown once. It can write your logs and read nothing else, and it never goes near the repository.

02

Tell it which log this repo is

›use FounderLog
.founderlogsafe to commit
# Which Founderlog this repository writes to.FounderLog

The whole of the configuration, and it holds no secret. After it is written the question never comes up again.

Any MCP client works with npx -y founderlog-mcp. You can revoke a token in one click, and each token is limited to 120 entries per hour.

Your log is yours · export to markdown any time

Keep the record free. Pay for the correction.

Free shows what happened. Pro tells you when the work stops serving the aim — and what to do next.

Free

€0

The complete startup record.

  • One measurable current aim
  • Automatic changelog through MCP
  • Full history and markdown export
ProAim check

€49per month

The record, analyzed against your aim.

  • Everything in Free
  • Effort alignment after every ship
  • Drift warnings with evidence
  • One decision in the weekly review

Monthly billing through Polar