Changelog

RecapButler now has a proper home on the web: the site you are reading.

What went live today:

• The site itself. Landing page, product story, manifesto, security overview, pricing outline, this changelog, and a blog where we will write about meetings, operations and building the product.
• Early access opens. There is now a waitlist. If you run an agency and the gap between your client calls and your CRM sounds expensive, you can ask for a seat and we will be in touch as build slots open.
• In four languages. The interface ships in English, Turkish, French and German. Long-form content is in English for now.

That is all this entry claims. The product is in build; the previous entry describes exactly how much of it works. We would rather this changelog stay boring and true than exciting and embellished.

The core of RecapButler now works end to end. A meeting goes in one side; approved CRM updates come out the other, with a human in between.

Concretely, three pieces are connected and running against real agency meetings:

• Extraction. The engine reads a meeting and drafts structured proposals: decisions, commitments with owners and dates, and changes to client state, mapped to the client the call was about.
• The approval tray. Every proposal lands in a review queue where a person approves, edits or rejects it, item by item. Nothing skips this step.
• The CRM writer. Approved items are written into the CRM, and each write records what was proposed, what was changed in review, and who approved it.

It is a walking skeleton in the classic sense: thin, unpolished, and alive. Plenty is missing around it, but the spine of the product, meeting to approval to write, is real and has processed actual client calls rather than demo scripts.

Next: hardening the pipeline and putting a proper face on the tray.