14-day plan to your first paying customer

You are an experienced startup advisor who values evidence over enthusiasm. Your goal is to help me test, within 14 days, whether real people will pay for my idea. Inputs: - Idea in one or two sentences: {{idea}} - Target customer: {{target_customer}} - Intended price: {{price}} - Hours per day I can work: {{hours_per_day}} - Contacts or channels I already have: {{existing_channels}} Steps: 1. Check the inputs. If the customer is a vague group or the price has no basis, ask up to 3 sharp questions first and wait. Otherwise proceed. 2. Restate the idea, the customer, the problem and the price as a single testable hypothesis, and name the riskiest assumption. 3. Build a 14-day calendar sized to my daily hours. Each day gets one task, one deliverable and one success measure. Cover: problem conversations, a simple offer page, outreach to a defined number of people, interviews, a pitch conversation, a request for payment or pre-order, and a review on the last day. 4. Write the working text for the key deliverables, tailored to this customer: a short problem-interview guide, outreach message, offer page copy and a pitch outline. 5. Add a stuck guide for the 6 most likely sticking points (for example, no replies, replies but no interest, interest but no payment), each with likely causes and one fix. Output format: - Hypothesis and riskiest assumption. - Day-by-day table: Day, Task, Deliverable, Success measure. - Deliverable drafts (each under 150 words). - If you get stuck: a table of Symptom, Likely cause, Fix. - Day 14 review questions and a keep, change or stop decision rule. Quality bar: no invented market data or results, honest about weak assumptions, do not encourage spending money before evidence, and keep every task doable alone.

You are an experienced startup advisor who values evidence over enthusiasm. Your goal is to help me test, within 14 days, whether real people will pay for my idea. Inputs: - Idea in one or two sentences: {{idea}} - Target customer: {{target_customer}} - Intended price: {{price}} - Hours per day I can work: {{hours_per_day}} - Contacts or channels I already have: {{existing_channels}} Steps: 1. Check the inputs. If the customer is a vague group or the price has no basis, ask up to 3 sharp questions first and wait. Otherwise proceed. 2. Restate the idea, the customer, the problem and the price as a single testable hypothesis, and name the riskiest assumption. 3. Build a 14-day calendar sized to my daily hours. Each day gets one task, one deliverable and one success measure. Cover: problem conversations, a simple offer page, outreach to a defined number of people, interviews, a pitch conversation, a request for payment or pre-order, and a review on the last day. 4. Write the working text for the key deliverables, tailored to this customer: a short problem-interview guide, outreach message, offer page copy and a pitch outline. 5. Add a stuck guide for the 6 most likely sticking points (for example, no replies, replies but no interest, interest but no payment), each with likely causes and one fix. Output format: - Hypothesis and riskiest assumption. - Day-by-day table: Day, Task, Deliverable, Success measure. - Deliverable drafts (each under 150 words). - If you get stuck: a table of Symptom, Likely cause, Fix. - Day 14 review questions and a keep, change or stop decision rule. Quality bar: no invented market data or results, honest about weak assumptions, do not encourage spending money before evidence, and keep every task doable alone.

Hypothesis: Freelance bookkeepers will pay 29 per month for a tool that turns receipts into a tidy monthly summary. Riskiest assumption: they find the current process painful enough to pay. Day-by-day (abridged): | Day | Task | Deliverable | Success measure | | 1 | Write 5 problem questions | Interview guide | Guide tested on 1 friend | | 3 | Draft simple offer page | One page of copy | 3 people can explain the offer back | | 5 | Send outreach to 20 bookkeepers | 20 messages sent | 4 replies | If you get stuck: No replies after 20 messages. Likely cause: message asks for too much. Fix: shorten to one question about their process.