Build a Sales Tracking System Without a CRM
In small businesses, sales usually live in someone's head: who you talked to, who got a quote, who's waiting on a follow-up, all of it stored in memory. That works fine with five customers. By customer fifteen, someone gets forgotten, a quote goes unanswered, and a deal quietly dies. The surface problem is 'I can't afford a CRM'; the real problem is 'I'm managing sales as a series of separate conversations instead of a process, so I never see how many deals are stuck at which stage.' This prompt doesn't set up expensive software; it builds a system that ties your calls, quotes, and follow-ups to a simple spreadsheet: stage definitions, how often to follow up, why deals get lost, and a weekly review that takes a few minutes and keeps the whole thing alive. It doesn't script what to say on a call. It sets up how you keep your entire sales pipeline in view.
You are a sales operations consultant for small businesses. Your expertise: making a sales process visible and trackable with a simple spreadsheet, no expensive CRM software required. Your job is NOT to script what to say on a call; it's to tie calls, quotes, and follow-ups into one system so no deal quietly disappears. I'll give you: - [MY BUSINESS: what I sell, how long a typical sales cycle takes] - [HOW I TRACK NOW: notebook, WhatsApp, memory, a messy spreadsheet, whatever it is] - [ACTIVE DEAL COUNT: roughly how many customers I'm talking to or quoting at once] - [WHERE DEALS GET LOST MOST: forgotten follow-ups, unanswered quotes, first contact never returned] - [WHO'S TRACKING THIS: just me, or a small team] RETURN THE OUTPUT IN THIS EXACT ORDER, WITH THESE EXACT HEADERS: === STAGE DEFINITIONS === A clear 4 to 6 stage sequence specific to the sales process in the input (e.g. First Contact, Call, Quote, Follow-up, Won/Lost). Make the "condition to move to the next stage" explicit for each one: what has to happen for a deal to advance. === TRACKING TABLE TEMPLATE === Columns for a simple table: customer, stage, last contact date, next action date, quote amount, notes. Note which tool it can live in (Google Sheets, Notion, even paper), and whether it's built for solo use or shared, based on the team size in the input. === FOLLOW-UP RHYTHM === For each stage, how many days until the next contact. Don't leave this vague, give a concrete day count. === LOSS ANALYSIS === How a short reason tag (price, timing, competitor, went silent, no longer needed) gets attached to every lost deal, and how often those tags get reviewed. === WEEKLY REVIEW RITUAL === Once a week, how many minutes, which 3 questions to check to keep the table current (e.g. which deal hasn't been touched in over 7 days). === HOW NOT TO ABANDON THE SYSTEM === How systems this simple usually get abandoned (skipping updates during a busy week, forgetting the table exists), and which small habit prevents that. RULES: - Do NOT use made-up conversion rates or a made-up "average sales cycle is X days" statistic. - Adjust the number of stages to the input, don't overcomplicate; 4 to 6 stages is enough for a small business. - Don't recommend expensive software, integrations, or automation; keep the system something you can run by hand. - If the input is missing something, especially the active deal count, ask before assuming. - Write in natural, direct English, clear and immediately usable.
How to use it
- Step 1: Describe how you currently track sales (notebook, WhatsApp, memory, a messy spreadsheet) and how many stages your typical sales process actually goes through. Give your real stages, don't ask for a generic template.
- Step 2: Start filling the output's table template with your real data today, don't put it off. The system's value shows up in the actual deals that go into it, not in an empty template.
- Step 3: Lock the weekly review into a fixed day on your calendar. Reread the lost-deal analysis section once a month in particular; if the same loss reason keeps showing up, the problem isn't your process, it's your offer or your pricing.
Example / tip
Input: I've got 12 to 15 active deals going now, but tracking gets lost in WhatsApp messages, and I send a quote to some customers and forget to follow up entirely; I sell websites and digital marketing to small businesses. AI output (shortened): Stages: First Contact, Call Done, Quote Sent, Follow-up 1, Follow-up 2, Won/Lost. Table columns: customer name, stage, last contact date, next action date, quote amount, notes. Follow-up rhythm: first follow-up 3 days after the quote goes out, second at 7 days, tag as 'cold' if there's no response by day 14. Loss analysis: tag every lost deal with a one-word reason (price, timing, competitor, went silent), count the most common reason once a month.
Usage example
Copy the prompt as is, fill in the bracketed fields for your own business, and paste it into ChatGPT or Claude. The more concrete your input, the more useful the output. Take the first draft, ask for a one-sentence fix on whatever you don't like, then give it a final pass in your own voice.
When not to use it
This prompt is built for 5 to 50 active deals, the kind of volume one person or a small team can still track by hand. It doesn't replace an actual CRM once you've got a large sales team, a complex approval chain, or volume that needs automation.
Output quality checklist
- Are the stage definitions specific to the real sales process in the input, or is it a generic funnel?
- Is the follow-up rhythm tied to concrete day counts, or does it stay vague like 'follow up regularly'?
- Is the loss analysis built to surface a recurring pattern, not just log random reasons?
- Is the weekly review simple enough to do in a few minutes, or does it create a new chore?
