A meeting notetaker you own.
Penny joins your Google Meet, Teams and Zoom calls, writes minutes with actions, emails them to you and files them in your CRM. She runs on your own Cloudflare account, with Recall.ai doing the recording. You pay for the hours she sits in meetings, with no charge per seat.
The notes live in someone else's product.
A hosted notetaker charges per person per month and keeps your recordings, transcripts and summaries on its servers. The summary reaches your CRM as a pasted note, if it gets there at all, and when the subscription stops, so do the notes.
What a business needs from a meeting is small: what was agreed, who does what by when, and a record on the client's file. That is a bot in the call, a transcript, one model call and two deliveries. It fits on infrastructure you already pay for.
Calendar in, minutes out, nothing to remember.
She books herself
- Reads your Google or Microsoft 365 calendar every 10 to 15 minutes.
- Books a bot for each meeting with a video link, a day ahead.
- Moved meetings are re-booked; cancelled or declined ones are dropped.
#nopennyin a title keeps her out.
She joins and says so
- A Recall.ai bot joins a minute early, under a name you choose.
- It posts a recording notice in the chat for everyone to see.
- Anyone can ask for it to leave, and one click removes it.
She writes them up
- The transcript is stored in your database and Recall's recording is deleted.
- An AI model writes a summary, actions with owner and due date, decisions and open questions.
- Owners and dates are kept as spoken. Nothing is invented.
Email and CRM
- Minutes are emailed to the calendar's owner, a few minutes after the call.
- They are posted to your CRM and filed against the people who were invited.
- An action becomes a CRM task in one click.
Minutes a busy person can act on.
Each meeting produces the same five parts, in an email and on the client's record. They are a draft from the transcript, and say so; the transcript is one click away while it is kept.
"What did we agree with them last week?" In the 2nth CRM, Penny answers from her own minutes: the decision, the open actions and who owns each one.
Illustrative. Real minutes name real clients, so they stay private.
The same job, with the data and the bill in your hands.
| Penny Notetaker | A per-seat notetaker | |
|---|---|---|
| What you pay for | Meeting hours: $0.50 recording and $0.15 transcription per hour at Recall.ai's list prices (November 2026), plus a few cents of model use | A subscription per person, per month, used or not |
| Where the notes live | Your database, on your Cloudflare account | The vendor's servers |
| The recording | Deleted from Recall as soon as the transcript is stored; transcripts cleared after 90 days | Kept under the vendor's retention policy |
| CRM | Minutes filed against the contacts and companies invited, actions become tasks | An integration per CRM, where one exists |
| Who gets the minutes | The calendar's owner, at your own email domains only | Often every attendee, by default |
| The AI model | Your choice, changed in one setting | The vendor's choice |
| If you stop | The notes stay; you switch off a Worker | Export what you can before the account closes |
A 45-minute meeting costs about $0.49 to capture. Twenty hours of meetings a month is about $13.
Everyone in the call knows, and the notes stay inside.
Announced in the chat
The bot posts a recording notice when it joins, pinned on Google Meet, with a way to ask for it to be removed. Its name says what it is.
Only real meetings
Private entries, solo blocks, all-day events and declined invitations are never booked. One switch pauses calendar joining altogether.
Internal by default
Minutes go to the calendar's owner at your own domains. They are never sent to the other people in the call.
Short by design
Recall's recording is deleted once the transcript is stored. The transcript is cleared after 90 days. The minutes and actions stay.
Where audio is processed
Recall.ai processes the call in the region you choose: EU, US or Japan. Mine runs in Frankfurt. Notes and transcripts then live in your own database.
Capture behind one interface
Recall.ai sits behind a small adapter, so a self-hosted recorder in South Africa can replace it where audio must not leave the country. That swap is designed for but not built yet.
Running in two businesses, from one design.
Penny has taken the minutes of my own client meetings since November 2026, booked from my Microsoft 365 calendar and filed in the 2nth CRM. An earlier build of the same design runs for a recruitment firm: it watches three people's Google calendars and also writes client briefing notes and interview scorecards.
The standalone product is a single Cloudflare Worker with its own database and a small console. It has been tested end to end against Recall.ai. Live calls so far have been on Google Meet; Teams and Zoom use the same bot and are next to prove.
- Capture: Recall.ai meeting bots, scheduled from the calendar
- App: one Cloudflare Worker, D1 database, a two-minute cron
- Calendars: Google Calendar by a small script in your account; Microsoft 365 through the 2nth CRM
- Minutes: open models on Workers AI as built, any model through AI Gateway
- Email: Resend, from your own domain
- CRM: a signed webhook with the minutes and attendees; built into the 2nth CRM
Your meetings, your notes, your CRM.
A walkthrough takes 30 minutes and uses a real call. Setup is a short build: a Recall.ai account in your name, the Worker on your Cloudflare account, your calendars connected, and the minutes wired to the CRM you already run (HubSpot, Salesforce, ERPNext or your own). Code access on request.