Determine in under 10 minutes whether owned assets can solve a prospect’s pain points, and at what collaboration depth. Operates as Stage 2 of client-discovery-workflow.md.
/spectra-proposeDo not start from “what does the client need.” Start from “what we already have × where it intersects with their pain.” No intersection → drop the client. Do not force-fit by building new things.
Distilled from a real case with 4 wrong-direction pivots (see pitfalls.md — Client Discovery 4 Pivots). Before proposing any MVP, pass these four checks:
The payer is the real customer. The user is often not the payer.
| Context | Apparent customer | Real customer (payer) |
|---|---|---|
| Cram school | Children | Parents |
| B2B SaaS | End users | Procurement / boss |
| Pet products | Pet | Owner |
| Children’s toys | Kid | Parents / grandparents |
Check: Does the solution solve the payer’s pain? Solving the user’s need but the payer feels nothing → no purchase.
| Type | When used | When not used | Example |
|---|---|---|---|
| Pleasure point | Happy, will share | Nothing happens | Result video, cute animation |
| Pain point | Anxiety relief, can sleep | Persistent anxiety → finds competitor | AI emotional companion, instant relief |
Rule: MVP main dish must be a pain killer. Pleasure points can be side dishes (amplify spread) but never the core sell.
Anti-pattern: Selling “child speaking English video” as main MVP. That’s a pleasure point — parents feel good momentarily but the core anxiety about “my child’s English” is untouched.
Customers pay to outsource hassle. A solution that adds hassle back = inverted logic.
| Friction level | Example | Will buy? |
|---|---|---|
| Zero | Passive LINE push | ✅ |
| Low | Voluntary click when curious | ✅ |
| Mid | 10 min weekly cooperation | ⚠️ Depends on value |
| High | Daily task to perform | ❌ Cancellation |
Anti-pattern: “Every-night parent-child English task” — parents send kids to cram school precisely to outsource this. Throwing it back at them = no buy + complaints.
Check: If I were the payer, does this add to my burden?
Run external research (Perplexity, client interviews, public community discussions) before guessing pain points.
Anti-pattern: Assuming “teaching quality is the cram school’s pain” based on stereotypes. A franchise cram school often has teaching covered by HQ — the real pain is enrollment/marketing.
SOP: Stage 1 of client-discovery-workflow.md is mandatory. Skipping = the start of consecutive pivots.
Keep only pains that satisfy all three:
Reject pains that fail any filter. AI tools are not the right intervention.
Re-scan each time:
ls products/
ls 8-外掛/
ls skills/
For each asset, document:
| Pain | Owned Asset | Modification Effort |
|---|---|---|
| A | X | low/mid/high |
Modification effort drives pricing tier:
| Tier | Mode | Client Cost | Our Risk |
|---|---|---|---|
| A | Monthly SaaS rental of existing tools | lowest | lowest |
| B | Co-development with client as case study (revenue share or discount) | mid | mid |
| C | One-time integration build + monthly subscription | highest | highest, but template for future replication |
A is for testing the waters. C is the starting point for building a replicable template.
Selection rules (both must hold):
If both rules cannot be satisfied: redo Step 3 or recommend dropping.
Do NOT select MVP based on technical novelty.
| Pain | Asset | Modification |
|---|---|---|
| Slow speaking feedback | Voicebox retooled for English shadowing + scoring | mid |
| Parents cannot see progress | MOLTOS dashboard | low |
| Teacher prep overhead | AIRE customized question banks | mid |
| No after-class practice | LineHub 24h practice bot | mid |
| Parent notifications | LineHub + BuyGo+1 | low |
| Class recording | Webinar-Go | low |
| Tuition collection | Paygo | low |
LINE bot speaking practice + weekly parent report.
Rationale:
Decline the client if any holds:
design-principles.md)client-discovery-workflow.mdpersona-pain-scenario.mddecision-tree.mdsdd-workflow.mddesign-principles.md (entropy reduction section)