Live prompts during a cold call

While you're on the phone, an overlay listens (with consent) and feeds the next question, objection handle, and close — timed to the conversation, not a static script.

For SDRs and founders who still have to pick up the phone

Spotted on postyourbuildideas via @gianmauric

The problem, sharper

SDRs and founders who still have to pick up the phone already tried the generic version and bounced. While you're on the phone, an overlay listens (with consent) and feeds the next question, objection handle, and close — timed to the conversation, not a static script. The wedge is the constraint, not another feature list.

Features that make the pitch true

01Capture the job in one screen: While you're on the phone, an overlay listens (with consent) and feeds the next question,…
02Audience-aware defaults for sdrs and founders who still have to pick up the phone.
03Shareable artifact you can send to a teammate in one tap.
04Honest empty states. No fake social proof, no infinite onboarding.
05Export: the user can leave with their data on day one.

This weekend

Friday: landing page, one happy path, seed data.
Saturday: the core loop that makes the pitch true.
Sunday: share link, ugly-but-working export, tell ten people.

Stack

— Next.js + TypeScript
— Local-first persistence, server later
— streaming LLM calls
— structured output schemas
— eval set of 20 real examples
— role-based access

User stories

As a person in this group: SDRs and founders who still have to pick up the phone, I can describe the job in one sentence and get a usable first result.
As a skeptic, I can try it without creating an account.
As someone who might build this, I can copy a spec and start this weekend.

Paste into Cursor, Claude Code, or Codex

Build a working product called QuietLane.

Tagline: Live prompts during a cold call — without the usual product theater.

One-liner: While you're on the phone, an overlay listens (with consent) and feeds the next question, objection handle, and close — timed to the conversation, not a static script.

Who it is for: SDRs and founders who still have to pick up the phone

Non-goals: do not build a generic ai app. Do not add auth until the core loop works. Do not invent extra personas.

Must-have features:
1. Capture the job in one screen: While you're on the phone, an overlay listens (with consent) and feeds the next question,…
2. Audience-aware defaults for sdrs and founders who still have to pick up the phone.
3. Shareable artifact you can send to a teammate in one tap.
4. Honest empty states. No fake social proof, no infinite onboarding.
5. Export: the user can leave with their data on day one.

Suggested stack:
- Next.js + TypeScript
- Local-first persistence, server later
- streaming LLM calls
- structured output schemas
- eval set of 20 real examples
- role-based access

UX:
- Distinctive, editorial, not purple-gradient SaaS
- Works on a phone
- Empty states teach the product
- One primary action per screen

Ship this weekend:
1. A landing page that states the job in one breath
2. The core loop end to end with sample data
3. A shareable output
4. A README that explains what was intentionally left out

Constraints: TypeScript. Keep the first version local-first if a database would slow you down. Name the product QuietLane unless you have a clearly better one.