← All work
A call waveform with marked moments, each traced out into a structured amber line item.

Live Call Assistant · Personal · 2026

Every discovery call becomes an opportunity map, two minutes after you hang up

The best evidence for what to automate inside a prospect's business lives in the discovery call itself. If nobody captures it the same way twice, that evidence disappears the moment you hang up.

Paste the meeting URL

one tap, from a phone

Bot joins silently

Recall.ai, never speaks

Transcript runs the methodology

OpenAI

Opportunity map posts

1 to 2 min after hang-up

Launched from a phone. The bot listens, then reports.
1 to 2 min
from hang-up to structured opportunity map
Silent
the bot joins and listens, never speaks in the call
One tap
launched by pasting the meeting URL

01 · Problem

The best evidence lived in one person's head

Discovery calls hold the best evidence of where automation pays inside a prospect’s business, but the analysis lived in one person’s head. Manual post-call writeups took an hour each, so they got skipped, and every call was diagnosed a little differently. Follow-ups went out thin.

02 · Solution

The diagnostic came first, the bot second

I wrote the methodology down before writing any code: anchor on hours per week, separate actions from decisions, apply the instruction-manual test, four probing questions. Only then did I build a silent bot that joins the meeting through Recall.ai and runs the transcript through that methodology with OpenAI.

A few design choices worth noting: launched from a phone (paste the meeting URL, tap once), no database (per-call JSON on a persistent volume), and the bot never speaks in the meeting. It listens, then reports.

03 · Result

The same structured map, every time, two minutes after hang-up

Every call now produces the same structured opportunity map about 1 to 2 minutes after hang-up: a summary, the automation wedge with direct prospect quotes, expansion plays, and questions for the next call. Every report lives at a permanent URL, so deal context never disappears into a notebook.

The bot is the easy part. Writing down how you diagnose a call, that’s the work.
The methodology came first. The software just runs it the same way, every time.

Want the code, or a version tuned for your team? The build is on request.

Request the code

raph@raphaelmercado.devlinkedin.com/in/raphmercadogithub.com/raphaelmercado-coder