<aside> 😊
Jak z tego korzystać?
<aside> 🚧
Pre-work nie może być widoczne dla klienta
</aside>
| # | Question | Examples | Answer |
|---|---|---|---|
| 1 | What is the ONE outcome this module delivers? | e.g. "Freelancer has a 3-tier offer ready to send in 10 minutes" | |
| 2 | What are the 3 critical/big steps to get there? | Step 1: … / Step 2: … / Step 3: … | |
| 3 | What is the #1 obstacle that stops most freelancers? | e.g. "They overthink pricing and never send the offer" | |
| 4 | Is this a SOP or a system | If this is a SOP make it with simple steps to follow, we don’t need the system bellow |
If this is a system, we need to write everything bellow. | |
(treat it like an agents.md file)
Voice & Language
- Write at a **5th grade reading level.** Short sentences. One idea per sentence.
- Max sentence length: 15 words. Break anything longer into two sentences.
- Every sentence has a value and it's clear.
- No jargon. If you use a term, explain it in one sentence immediately after.
- Write like you're texting a smart friend. Not like you're writing a report.
- Avoid: "It's important to note that…" / "In order to…" / "This allows you to…"
- Use "you" constantly. This is personal.
## Structure Rules
- **Never change the module structure.** Sections 0–7 are fixed. Always in order.
- Every section must exist. Don't skip. Don't merge.
- If a section has sub-roles, sub-phases, or sub-systems — **make them visually obvious.** Use headers, boxes, or clear labels. Never bury them inside a paragraph.
- Example: if there's a "Setter" phase and a "Closer" phase — each gets its OWN header, its OWN block, its OWN explanation. Never combined into one section.
---
## Content Rules
- **One outcome per module.** If you're solving two problems, that's two modules.
- Every mechanic step must be actionable. Not "think about X." Do X.
- Every tip must be implementable today. No "over time" advice.
- Context matters — but cut anything the freelancer doesn't need to act.
- If you write more than 5 lines of explanation: stop. Cut it in half.
---
## Question Banks (when relevant)
- Minimum 6 questions per bank. Maximum 10.
- Every question must be ready to copy-paste. No placeholders left blank.
- Label each question bank clearly by phase or purpose.
- Add a 💡 note after each bank explaining when/how to use it.
---
## Examples Section
- Always include: web designer, developer, copywriter, social media manager.
- Each example must show the system in action. Not just describe it.
- Include wrong-way examples. Contrast is how people learn.
- Keep each example tight. Max 150 words per niche.
---
## Formatting
- You can use tables for comparisons
- Use the ASCII box format for the mechanics overview (the "HOW IT WORKS" block).
- Use callout boxes (💡 🎯 🔒) for tips, rules, and non-negotiables.
- Bold the most important word in a sentence. Not every other word.
- Never bold more than one phrase per paragraph.
---
## Tone
- Direct. Confident. Zero fluff.
- Irony and edge are allowed — but only if it serves clarity.
- The freelancer is smart. Don't over-explain the obvious.
- Do explain the non-obvious. That's where the value is.
- Clear, very understandable. Even a kid can understands those systems
- Sometimes you can be motivational in a very smart way
---
## Pre-Work (hidden from client)
- Always fill the 3-Question Filter completely before writing anything else.
- The ONE outcome must be specific. "Freelancer will X in Y minutes" — not vague.
- The #1 obstacle must be real. Think about what stops most people, not the best-case user.
<aside> ✅
PONIŻEJ jest część widoczna dla klienta
</aside>