---
name: solo-income-blueprint
description: >-
  Design a realistic one-person online income plan from the user's skills, time and
  budget: one recommended business model, one offer, a demand check, a content and
  sales path, automations, a minimal tool stack, and a 7-day launch plan. Use when
  someone asks how to make money online or with AI tools, what to sell, which
  business model fits them, how to turn a skill they already have into income, how
  to get a first paying customer, or wants a step-by-step plan for a side business
  or one-person business. Not for job hunting
  (application-pilot, applicant-kit), SEO for an existing site (seo-audit), or
  privacy and legal pages (paper-trail).
---

# Solo income blueprint

Turn "I want to make money online" into one concrete offer and one next action. The
deliverable is a plan the user can start today, not a catalogue of options.

## 1. Interview first

Ask at most five questions in one message:

1. What have you done that other people already pay for — a job, a hobby, a skill?
2. What could you talk about for an hour without preparing?
3. How many hours per week, realistically, and on which days?
4. What can you spend before the first sale — money and weeks?
5. What does "working" look like in 30 days: a first payment, a waitlist, or a habit?

If the user already supplied a profile, use it and ask only what is missing. Never ask
for passwords, account access, or secrets.

If the answers do not close mathematically — a large income goal in weeks on a few
hours with no audience — say so before recommending anything, and propose the fastest
honest path instead.

## 2. Recommend one model

Pick one model and tie it to the five answers. Name the runner-up and the one
condition that would flip the choice. Reject models that fail on time, budget, or
proof: a beginner with ten hours a week does not need a micro-SaaS.

Open `references/playbook.md` for the model comparison, validation thresholds, and
section templates.

## 3. Check demand before building

Give one validation step that fits the model: five conversations with the target
person, a pre-sale or deposit, a freelance proposal, or a one-page offer test. State
what response counts as evidence and what counts as a no. Do not let the user spend
two weeks building before this step.

## 4. Design the offer

One buyer, one problem, one outcome, one price, one delivery method. Use the offer
checklist in the playbook. Price from the outcome and the buyer's alternative, not
from hours. If the user cannot name a buyer they can reach, return to step 2.

## 5. Build the path to the first customer

- **Channel.** One primary platform where the audience already is and the user can
  sustain the format. At most one repurposed secondary channel.
- **Content.** Three pillars, one hook formula, a weekly cadence the user can keep.
- **Sales.** Services: a short outreach script and a follow-up cadence. Products: a
  lead magnet, a five-email sequence, and a one-page sales outline. Audience models
  (content, affiliate): a repeatable content-to-offer path and a disclosure rule.
- **Automations.** Automate capture, reminders, and repurposing only after the manual
  version has produced a result.
- **Tools.** Categories first, free tiers first. Name what each category must do; do
  not invent prices, and verify a free tier this session before calling it free.

## 6. Write the 7-day launch plan

Day by day, one outcome per day, estimated to fit the hours from the interview. The
plan launches the offer; it does not promise revenue. End with `START HERE FIRST` and
the single action for the next hour.

## Rules

- No earnings guarantees and no fabricated results, market sizes, or conversion
  rates. Label every assumption as an assumption.
- Refuse models built on deception: fake proof or testimonials, fake scarcity,
  undisclosed affiliate or sponsorship relationships, or misleading claims.
- Never state a tool price or free tier without checking it in this session; otherwise
  write "check current pricing".
- The user approves anything that spends money, publishes publicly, or contacts people
  at scale.
- Prefer a paid pilot over a large build. Prefer one channel over five.
- If the user already runs a business and wants SEO, ads, or site conversion work,
  this is not the skill — route to the marketing skills.

## Hand off

- Job search, resumes, or interview prep: `application-pilot`, `applicant-kit`, or
  `recruiter-lens`, with the user's actual request.
- SEO or visibility for a site that already exists: `seo-audit` or `findable`.
- Privacy, terms, or refund pages: `paper-trail`.
- Say which skill takes over and why; pass the request, not a summary of this one.
- If a sibling is not installed, name the job it would do and give the first manual
  step instead.

## Output shape

Deliver in chat, in this order:

1. **Read of you** — two or three lines tying the recommendation to the answers.
2. **Recommended model** — one, plus the runner-up and the flip condition.
3. **Demand check** — the test and the evidence threshold.
4. **Offer** — buyer, problem, outcome, price, delivery, guarantee, differentiator.
5. **Audience and channel** — profile, one primary channel, messaging angle.
6. **Content plan** — pillars, formats, cadence, three example hooks.
7. **Sales path** — script or sequence outline.
8. **Automations and tools** — what to automate, what to use, what to ignore.
9. **7-day plan** — day, outcome, hours.
10. **START HERE FIRST** — one action for the next hour.

If the user asks, save the blueprint to `income-blueprint.md`. Do not save it
unasked. The reply still ends with `START HERE FIRST`.