Quote Chaser

A proposal follow-up tracker app idea: a tracker that nudges clients who went quiet on a quote. Weekend build with Next.js, Supabase, faster-whisper and Resend, for small agency owners and tradespeople sending quotes by email.

See the spec
Why now

Why now

Empacer's launch shows small business owners want voice-first help with admin work like this. Faster transcription through faster-whisper, which is rising on PyPI, makes it practical to log a quote by speaking after a site visit. From the signals of the week of 2 Nov 2026.

The spec

The spec

Log each quote with its amount and send date, and get a drafted follow-up at the right moment based on how the client last replied. It stops quotes from dying because nobody wrote the second email.

Build time

WeekendBasic logic / CRUD · Level 2 of 5

Audience

Small agency owners and tradespeople sending quotes by email.

Stack

  • Next.js
  • Supabase
  • faster-whisper
  • Resend

Fun factor

Seeing the overdue list shrink to zero feels like finding money in a coat pocket.

Core features

  • Quote log with amount, client and status
  • Follow-up schedule per quote
  • Voice note entry for new quotes
  • One-click mark as won or lost

AI features

  • Drafts a follow-up that references the specific job and the client's last message
  • Transcribes a spoken note and extracts client, amount and scope into fields

Stretch goals

  • Send follow-ups through Gmail
  • Win-rate report by quote size
  • Reminder when a quote is about to expire

First version

A quote list with due-date follow-up reminders and an AI drafted email for each one.

Build plan

Build plan

4 milestones, in the order you would build them. Saved ideas get this plan with checkboxes and notes.

Create the quote tableStore client, amount, sent date and status.
Start here
Schedule remindersCompute next follow-up dates and show an overdue list.
Draft follow-upsGenerate an email from the quote details and past replies.
Add voice entryTranscribe a note and fill the quote form.
The build prompt

The build prompt

Paste this into ChatGPT, Claude, Codex, or Cursor, then build the first version before anything else.

quote-chaser-2026-w45.prompt.md
# Build Quote Chaser

You are a senior full-stack engineer pairing with me on a side project. Build a working first version of the product described below. Read the whole brief before writing any code, then follow "How to work" at the end.

## The idea

**Quote Chaser.** Log each quote with its amount and send date, and get a drafted follow-up at the right moment based on how the client last replied. It stops quotes from dying because nobody wrote the second email.

**Why now:** Empacer's launch shows small business owners want voice-first help with admin work like this. Faster transcription through faster-whisper, which is rising on PyPI, makes it practical to log a quote by speaking after a site visit.

**Who it is for:** Small agency owners and tradespeople sending quotes by email

**What makes it fun:** Seeing the overdue list shrink to zero feels like finding money in a coat pocket.

## Scope

- **Build time:** Weekend. Size every decision to ship a working first version inside this window.
- **Technical ambition:** Level 2 of 5, "Basic logic / CRUD". A few screens over a simple data model with create, read, update, and delete. One lightweight persistence layer, no heavy infrastructure.
- **First version only.** Ship the core features below end to end. Stretch goals are listed so you can design around them, not build them.

## Core features (each must work end to end in the first version)

1. Quote log with amount, client and status
2. Follow-up schedule per quote
3. Voice note entry for new quotes
4. One-click mark as won or lost

## AI features

- Drafts a follow-up that references the specific job and the client's last message
- Transcribes a spoken note and extracts client, amount and scope into fields

How to build them:
- Put every model call behind one server-side module with a typed interface, so the provider can change without touching the UI.
- Read API keys from environment variables only, and document each one in `.env.example`.
- Write prompts as versioned constants with clear instructions and an example of the expected output; parse and validate responses before using them.
- Handle timeouts, rate limits, and malformed output with a graceful fallback the user can understand. Stream responses where a wait would exceed a couple of seconds.
- Never let a feature depend on the model being perfect. Show the result, let the user edit or retry.

## Stretch goals (later, not in the first version)

- Send follow-ups through Gmail
- Win-rate report by quote size
- Reminder when a quote is about to expire

Leave clean seams for these (a module boundary, a nullable column, a feature flag), but do not implement them unless I ask.

## Tech stack

Use exactly: Next.js, Supabase, Faster-whisper, Resend.

Stay on current stable versions, follow each tool's official conventions, and add a library only when the standard library or the chosen stack cannot do the job cleanly. If part of this stack is a poor fit for a specific requirement, say so and propose the smallest change.

## Owner's notes

Written by me, the project owner. Treat these as requirements and preferences that override the generated material above when they conflict.

The first version should be exactly this, and no bigger: A quote list with due-date follow-up reminders and an AI drafted email for each one.

## Build plan (with saved progress)

0 of 4 steps complete. Resume at step 1: Create the quote table. Before you start it, check what is already implemented so you do not repeat finished work.

1. **Create the quote table** [not started]
   Store client, amount, sent date and status.

2. **Schedule reminders** [not started]
   Compute next follow-up dates and show an overdue list.

3. **Draft follow-ups** [not started]
   Generate an email from the quote details and past replies.

4. **Add voice entry** [not started]
   Transcribe a note and fill the quote form.

## Definition of done for the first version

- [ ] Quote log with amount, client and status works end to end, with real data, not a placeholder.
- [ ] Follow-up schedule per quote works end to end, with real data, not a placeholder.
- [ ] Voice note entry for new quotes works end to end, with real data, not a placeholder.
- [ ] One-click mark as won or lost works end to end, with real data, not a placeholder.
- [ ] Every screen handles loading, empty, and error states.
- [ ] Typecheck, lint, and any tests pass, and the main user flow was exercised by hand.
- [ ] A README explains setup, environment variables, and how to run it locally.

## Quality bar

- Responsive from a phone to a desktop, keyboard-accessible, semantic HTML, visible focus states, labelled inputs, and sensible contrast.
- Loading, empty, and error states for every screen that reads or writes data. Errors say what happened and what to do next.
- Validate on the server, never trust the client, and keep secrets in environment variables with a committed `.env.example`.
- Type-safe end to end. No `any` without a comment explaining why.
- Small, readable modules named after what they do. No premature abstraction, no dead code, no TODOs left for later without a note.
- Sensible defaults over settings. If a choice is not in this brief, pick the simplest option that keeps the product coherent and say what you chose.

## How to work

1. **Read, then restate.** Summarize the product in three sentences and list your assumptions. Ask only the questions that block implementation. For everything else, decide and note the decision.
2. **Plan before code.** List the files and modules you will create, in build order, mapped to the core features. If a build plan is included above, use it instead: resume at the first step not marked done and check what already exists before touching it.
3. **Set up.** If a project already exists, inspect its code, instructions, and conventions first and build on them. Otherwise scaffold the stack above with linting, formatting, a typecheck script, `.env.example`, and a README stub.
4. **Model the data first.** Define the types, schema, and any migrations before the UI, so the shape of the product is settled early.
5. **Build in vertical slices.** Finish one core feature end to end (data, logic, UI) before starting the next. Keep the app runnable after every slice and commit each slice with a message that says what changed and why.
6. **Then the interface.** Apply the quality bar above to each screen as it lands, not as a final pass.
7. **Verify.** Run typecheck, lint, and tests. Exercise the main user flow by hand. Check each item in the definition of done and each acceptance criterion.
8. **Report.** Tell me what works, what you tested and how, what is not done, every setup step I must complete myself, and the three most useful next steps. Never claim a service, test, or flow was verified when it was not.

If you can edit and run the project, start implementing right after the short plan. If you cannot, give me concrete code and the exact commands to run for the next step.

Rules: keep the product name and the scope as written, do not invent features, prefer boring and proven choices, and stop to ask me when a decision would be expensive to reverse.

How to use

  1. Copy the prompt above.
  2. Open ChatGPT, Claude, or your AI editor and paste it into a new conversation.
  3. Build milestone one, run it, then move to the next. Add stretch goals only after the first version works.

Want ideas built around you instead? Generate four from your own interests, time, and stack.

Frequently asked questions

FAQ

Frequently asked questions

Answers on what Quote Chaser is, how to build it, and where example ideas come from.

Similar ideas

Similar to Quote Chaser

More sales ideas, then a few from other categories.

Generate your own

Ready to generate yours?

Four ideas per round, shaped by your interests, skill level, and how much time you have.