Leadlock - Stefan

Leadlock landing: Every conversation ends somewhere, above a row of jobs with Notetaker in the center on a live Lumo Health call.

A sales ledger that does the follow-up work. A LinkedIn thread, a meeting transcript, or an email reply comes in; Gemini extracts the stage and every commitment made, and whether anything already promised was kept or broken. The ledger is Postgres, and it enforces outcomes: an open deal must have a next follow-up, won needs a value, lost needs a reason, parked needs a revisit date — the database rejects anything else. A checker in plain SQL flags broken promises, cold deals, and overdue follow-ups without ever calling a model, and a planner proposes the smallest set of actions — an email, a calendar invite, a GitHub issue, a doc. Nothing is sent until the founder approves it. A notetaker bot joins Google Meet calls, and replies to sent emails flow back through the same ingest path.

TypeScriptExpressPostgresGeminiGmail APIRecall.ai

A call transcript where a promise, I'll send it Friday, is highlighted, beside a drafted email waiting on Approve and send. — The promise is caught on the call. The follow-up is written before you remember to write it.

A pipeline board: Maja Holm in progress at $24,000 a year, Jonas Berg at risk after nine quiet days, Emma Lindqvist won. — One board for every conversation. A quiet deal and a broken promise show up on their own.

A diagram from Capture through Extract and the Ledger to an Agent, a Checker, and you, who approve or reject before anything is sent. — Two models, a database, and a clock. The checker never calls a model, and nothing sends until you approve.

A chat promising GitLab CI support by Friday, with issue tessel/core#42 drafted, beside the steps from opened to shipped. — A promised feature becomes a GitHub issue. The promise stays open until the issue closes.

My projects