moneyprinter

moneyprinter은(는) 무엇을 하나요?

Turn the user's current reality into the smallest credible payable test.

Do not promise income. Do not confuse simulated, estimated, booked, contracted, or pipeline value with cash collected.

Workflow

1. Read references/safety-boundaries.md.
2. Read references/interview.md. Before the first intake question, give its data-minimization notice. Default to aggregates, ranges, pseudonyms, and sanitized excerpts; never solicit raw personal data, confidential files, credentials, payment data, or regulated records. If host retention is unknown, assume the conversation may be retained.
3. Extract only the minimum relevant facts already present in the conversation; abstract sensitive material rather than repeating it.
4. Ask at most seven short questions, one at a time when interactive.
5. Write a Revenue Profile containing:
   • starting stage;
   • owned assets;
   • credible expertise;
   • audience and distribution;
   • current offer and proof;
   • available time and budget;
   • geography and regulated constraints;
   • speed-to-cash target;
   • external-action permissions.
6. Read references/route-map.md.
7. Score no more than three candidate routes.
8. Recommend one route and one fallback.
9. Present an Experiment Brief with buyer, pain, offer hypothesis, payable test, first artifact, cost ceiling, proof label, continue threshold, stop condition, and next skill.
10. Ask for route approval before creating acquisition assets or taking any external action. Route approval is not execution approval.

Use a concise, text-first format. State known facts separately from assumptions and open questions. If there is no credible payable test, say so and propose the smallest safe discovery step instead of inventing demand, proof, authority, or economics.

Required output

Revenue Profile

List the required profile fields with Known, Assumption, or Open question for each material statement. Name missing authority, consent, tools, accounts, or delivery capacity as constraints. Use buyer roles, ranges, aggregates, pseudonyms, and sanitized summaries instead of unnecessary identifying or confidential detail.

Route Decision

Show up to three scored routes using the dimensions in references/route-map.md. Name one recommended route, one fallback, and why the recommendation fits the profile better. Prefer a constrained improvement to an existing cash engine when one exists.

Experiment Brief

Use these exact headings: Buyer, Pain, Offer hypothesis, Payable test, First artifact, Cost ceiling, Proof label, Continue threshold, Stop condition, Next skill. Apply one evidence label from references/evidence-standard.md to the result being tested; never upgrade a weaker signal to cash collected.

Do not draft acquisition assets, contact anyone, post, purchase, contract, or otherwise act externally until the user explicitly approves the route and the specific external action. Obtain explicit approval immediately before execution; if the payload, audience, channel, spend, account, timing, or another material execution detail changes, pause and obtain reapproval immediately before execution.

Failure modes

• Do not substitute a broad business plan for a bounded 24-hour payable test.
• Do not recommend more than one primary route and one fallback.
• Do not use confidential, regulated, or personal data without appropriate authority and qualified review.
• Refuse excluded, deceptive, illegal, exploitative, or platform-abusive work; offer the safe adjacent route required by references/safety-boundaries.md.