- Added REPO_INVENTORY.md with all repos, branches, remotes, and staging info - Added .gitignore - Synced all existing docs from local workspace - Centralized documentation hub for GrowQR team
2179 lines
74 KiB
Markdown
2179 lines
74 KiB
Markdown
# GrowQR Curator ICP Task & Subtask Playbook
|
|
|
|
Date: 2026-06-15
|
|
Purpose: define example 30/60-day streak tasks, weekly progress suggestions, and service handoffs for the GrowQR curator across core ICPs.
|
|
|
|
## 1. Product framing
|
|
|
|
GrowQR should not feel like a list of disconnected tools. The user experience should feel like:
|
|
|
|
> Onboarding identifies my current situation, goals, blockers, and urgency. GrowQR turns that into a 30/60-day instructed growth plan. Streaks and weekly progress are the daily execution layer. Each task either creates evidence, improves confidence, raises Q Score, or moves me closer to opportunities.
|
|
|
|
Core services:
|
|
|
|
- **Q Score / QX Score**: readiness measurement and progress ledger.
|
|
- **Resume**: proof packaging, role-fit evidence, credibility artifact.
|
|
- **Interview**: confidence, articulation, offer-readiness practice.
|
|
- **Roleplay**: high-stakes conversation practice: recruiter, manager, client, investor, negotiation.
|
|
- **Social / personal branding**: visibility, trust, inbound surface area.
|
|
- **Pathways / matchmaking**: convert readiness into direction, jobs, clients, collaborators, or customers.
|
|
|
|
The curator should always answer: **why this task today, what service it unlocks, and what the user gets after completing it.**
|
|
|
|
---
|
|
|
|
## 2. ICP taxonomy from onboarding
|
|
|
|
### A. Individual career users
|
|
|
|
Onboarding signals:
|
|
|
|
- Intent: better job, feel stuck, grow here, know where I stand.
|
|
- Current state: actively hunting, employed but ready to move, between jobs, student/recent grad, exploring.
|
|
- Blockers: don't know where to start, no callbacks, interviews not converting, weak profile, stuck in role, not enough time.
|
|
- Goal: land exciting role, higher pay, switch field, build skills, leadership, start own thing.
|
|
- Work area: tech/product/data, design/creative, sales/growth/partnerships, leadership/strategy, student, other.
|
|
- Experience: 0-2, 2-5, 5-10, 10+ years.
|
|
- Pace: 1-month sprint, 3-month steady climb, flexible long game.
|
|
|
|
Primary sub-segments for this doc:
|
|
|
|
1. Students / recent grads.
|
|
2. Interns.
|
|
3. Freshers / early professionals under 5 years.
|
|
4. Experienced professionals above 5 years.
|
|
|
|
### B. Gig / freelance users
|
|
|
|
Onboarding signals:
|
|
|
|
- Current state: just starting, few clients, steady income, ready to scale, side hustle.
|
|
- Blockers: client pipeline, pricing, standing out, online trust, income consistency, referrals.
|
|
- Goal: consistent pipeline, higher rates, work I love, personal brand, full-time freelancing, recurring income.
|
|
- Service area: design, tech/dev, writing/content, consulting/strategy, coaching/training, marketing/social.
|
|
- Experience: new, under 1 year, 1-3 years, 3+ years.
|
|
- First milestone: first client, double income, full-time, Rs 1L/month, waitlist.
|
|
|
|
### C. Founder / solopreneur users
|
|
|
|
Onboarding signals:
|
|
|
|
- Stage: idea, MVP, traction, scaling, pre-revenue.
|
|
- Blockers: team, funding, visibility, customers, proving model, burn.
|
|
- Goal: hire key people, raise, authority, first 100 customers, validate idea, cofounder.
|
|
- Space: B2B SaaS, consumer, marketplace, deeptech/hardware, services/agency, other.
|
|
- Founder type: first-time, built before, serial, operator turned founder.
|
|
- 90-day priority: ship MVP, close customers, hire, raise pre-seed, build presence.
|
|
|
|
---
|
|
|
|
## 3. Curator task design rules
|
|
|
|
Every curator task should have:
|
|
|
|
1. **Business reason**: why this helps the user's stated outcome.
|
|
2. **Service owner**: Q Score, Resume, Interview, Roleplay, Social, Pathways, Matchmaking.
|
|
3. **One focused action**: no broad advice.
|
|
4. **Subtasks**: 2-4 small steps max.
|
|
5. **Handoff**: if service-backed, the user should land directly in a useful preview/setup state.
|
|
6. **Signal**: what will improve in Q Score or user readiness ledger.
|
|
7. **Timebox**: preferably 5, 10, 15, or 20 minutes.
|
|
|
|
Good task title examples:
|
|
|
|
- “Prepare your first PM interview preview”
|
|
- “Turn your project into a resume proof point”
|
|
- “Practice your salary ask with a recruiter”
|
|
- “Package your first freelance offer”
|
|
- “Draft your founder credibility post”
|
|
|
|
Bad task title examples:
|
|
|
|
- “Improve career”
|
|
- “Use interview service”
|
|
- “Complete profile”
|
|
- “Do task 1”
|
|
|
|
---
|
|
|
|
## 4. Universal 30/60-day plan structure
|
|
|
|
### Days 1-7: Baseline and first proof
|
|
|
|
Goal: establish Q Score baseline, identify target, create first useful artifact.
|
|
|
|
Common tasks:
|
|
|
|
- Complete Q Score baseline.
|
|
- Upload/import resume, LinkedIn, portfolio, GitHub, website, pitch deck.
|
|
- Pick one target outcome.
|
|
- Generate first service preview: interview, roleplay, resume audit, or profile audit.
|
|
- Complete one confidence-building practice.
|
|
|
|
### Days 8-14: Fix obvious gaps
|
|
|
|
Goal: remove blockers surfaced by onboarding.
|
|
|
|
Common tasks:
|
|
|
|
- Rewrite weak headline / summary / resume bullets.
|
|
- Practice top interview or conversation blocker.
|
|
- Build proof bank: projects, client wins, traction, metrics.
|
|
- Create first public credibility artifact.
|
|
|
|
### Days 15-30: Repetition and market-facing action
|
|
|
|
Goal: repeat practice, publish/apply/reach out, collect feedback.
|
|
|
|
Common tasks:
|
|
|
|
- 2-4 mock interviews or roleplays.
|
|
- 5 targeted applications / leads / warm intros.
|
|
- One profile/resume iteration using results.
|
|
- One Q Score check-in.
|
|
|
|
### Days 31-60: Conversion loop
|
|
|
|
Goal: convert readiness into outcomes.
|
|
|
|
Common tasks:
|
|
|
|
- Interview-to-offer loop.
|
|
- Salary/client/investor conversation practice.
|
|
- Stronger market proof: case study, portfolio, founder update.
|
|
- Matchmaking / opportunities / collaborator pipeline.
|
|
|
|
---
|
|
|
|
## 5. ICP playbooks
|
|
|
|
## 5.1 Students / recent grads
|
|
|
|
### Main jobs-to-be-done
|
|
|
|
- Figure out what roles to target.
|
|
- Build a credible identity before graduation.
|
|
- Turn coursework/projects into proof.
|
|
- Practice interviews before real rounds.
|
|
- Build confidence and a daily habit.
|
|
|
|
### Suggested 30-day plan theme
|
|
|
|
**“First Role Readiness Sprint”**
|
|
|
|
### Example weekly progress suggestions
|
|
|
|
#### Task: Pick your first target role
|
|
|
|
Service: Pathways / Q Score
|
|
Business reason: students often lack direction; role clarity makes resume and interview prep specific.
|
|
|
|
Subtasks:
|
|
|
|
1. Choose 1-2 role families: software, product, data, design, growth, consulting.
|
|
2. Capture current strengths: coursework, projects, internships, societies.
|
|
3. Compare requirements against your current proof.
|
|
4. Save target role into GrowQR plan.
|
|
|
|
Curator first question:
|
|
|
|
> Which role family do you want to prepare for first: engineering, product, data, design, growth, or something else?
|
|
|
|
CTA:
|
|
|
|
- “Review pathway”
|
|
- “Update Q Score baseline”
|
|
|
|
Signals:
|
|
|
|
- goal clarity
|
|
- role alignment
|
|
- readiness baseline
|
|
|
|
#### Task: Turn one project into resume proof
|
|
|
|
Service: Resume
|
|
Business reason: students usually have weak experience sections but strong hidden project evidence.
|
|
|
|
Subtasks:
|
|
|
|
1. Pick one project/coursework/internship.
|
|
2. Capture problem, action, result.
|
|
3. Convert it into 2 resume bullets.
|
|
4. Save to resume workspace.
|
|
|
|
Curator first question:
|
|
|
|
> Which project should we package today, and what did it achieve?
|
|
|
|
CTA:
|
|
|
|
- “Open resume workspace”
|
|
|
|
Signals:
|
|
|
|
- resume evidence
|
|
- proof density
|
|
- project articulation
|
|
|
|
#### Task: Prepare first mock interview preview
|
|
|
|
Service: Interview
|
|
Business reason: early practice reduces anxiety and creates interview readiness signals.
|
|
|
|
Subtasks:
|
|
|
|
1. Pick role and round type.
|
|
2. Choose difficulty: easy/medium.
|
|
3. Generate interview preview.
|
|
4. Complete the practice and review feedback.
|
|
|
|
Curator first question:
|
|
|
|
> What role should I prepare this mock interview for?
|
|
|
|
Default preview:
|
|
|
|
- type: behavioral
|
|
- difficulty: medium
|
|
- duration: 5 minutes
|
|
- media: audio or video depending quota/default
|
|
|
|
CTA:
|
|
|
|
- “Open interview preview”
|
|
|
|
Signals:
|
|
|
|
- interview confidence
|
|
- communication clarity
|
|
- Q Score practice signal
|
|
|
|
#### Task: Practice “Tell me about yourself”
|
|
|
|
Service: Roleplay or Interview
|
|
Business reason: this is the most reusable first-round answer.
|
|
|
|
Subtasks:
|
|
|
|
1. Capture target role.
|
|
2. Capture current student background.
|
|
3. Practice 60-second pitch.
|
|
4. Save improved version.
|
|
|
|
Curator first question:
|
|
|
|
> What role should your intro be tailored toward?
|
|
|
|
CTA:
|
|
|
|
- “Open roleplay preview” or “Open interview preview”
|
|
|
|
Signals:
|
|
|
|
- self-pitch quality
|
|
- confidence
|
|
- communication readiness
|
|
|
|
#### Task: Build your first credibility post
|
|
|
|
Service: Social / Personal branding
|
|
Business reason: public proof can increase recruiter trust even before full-time experience.
|
|
|
|
Subtasks:
|
|
|
|
1. Pick a project or learning insight.
|
|
2. Draft a LinkedIn post.
|
|
3. Add one measurable takeaway.
|
|
4. Save/publish.
|
|
|
|
Curator first question:
|
|
|
|
> Which project or lesson should this post highlight?
|
|
|
|
CTA:
|
|
|
|
- “Draft profile post”
|
|
|
|
Signals:
|
|
|
|
- visibility
|
|
- public proof
|
|
- profile strength
|
|
|
|
---
|
|
|
|
## 5.2 Interns
|
|
|
|
### Main jobs-to-be-done
|
|
|
|
- Convert internship into full-time offer.
|
|
- Communicate impact to manager/team.
|
|
- Build workplace confidence.
|
|
- Prepare for return offer or external interviews.
|
|
|
|
### Suggested 30-day plan theme
|
|
|
|
**“Intern-to-Offer Sprint”**
|
|
|
|
### Example tasks
|
|
|
|
#### Task: Capture your internship impact
|
|
|
|
Service: Resume / Q Score
|
|
|
|
Subtasks:
|
|
|
|
1. List current internship project.
|
|
2. Capture metric or visible outcome.
|
|
3. Convert into resume bullet.
|
|
4. Add to proof bank.
|
|
|
|
Curator first question:
|
|
|
|
> What project are you working on in your internship, and what changed because of your work?
|
|
|
|
CTA:
|
|
|
|
- “Open resume workspace”
|
|
|
|
Signals:
|
|
|
|
- proof density
|
|
- experience clarity
|
|
|
|
#### Task: Practice manager check-in
|
|
|
|
Service: Roleplay
|
|
|
|
Subtasks:
|
|
|
|
1. Define desired outcome: feedback, extension, full-time offer, better project.
|
|
2. Capture manager context.
|
|
3. Generate roleplay preview.
|
|
4. Practice the check-in.
|
|
|
|
Curator first question:
|
|
|
|
> What do you want from the manager conversation: feedback, return offer, clearer expectations, or project scope?
|
|
|
|
CTA:
|
|
|
|
- “Open roleplay preview”
|
|
|
|
Signals:
|
|
|
|
- workplace communication
|
|
- confidence
|
|
- initiative
|
|
|
|
#### Task: Prepare return-offer interview
|
|
|
|
Service: Interview
|
|
|
|
Subtasks:
|
|
|
|
1. Choose role/function.
|
|
2. Capture internship project context.
|
|
3. Generate preview.
|
|
4. Complete one mock round.
|
|
|
|
Curator first question:
|
|
|
|
> Which return-offer role or team should this interview prepare you for?
|
|
|
|
CTA:
|
|
|
|
- “Open interview preview”
|
|
|
|
Signals:
|
|
|
|
- interview readiness
|
|
- internship conversion readiness
|
|
|
|
#### Task: Write your weekly internship update
|
|
|
|
Service: Social / Resume
|
|
|
|
Subtasks:
|
|
|
|
1. Capture what shipped this week.
|
|
2. Capture what you learned.
|
|
3. Draft manager-ready update.
|
|
4. Save one resume proof point.
|
|
|
|
Curator first question:
|
|
|
|
> What did you complete or learn this week that your manager should notice?
|
|
|
|
CTA:
|
|
|
|
- “Draft update”
|
|
|
|
Signals:
|
|
|
|
- communication discipline
|
|
- workplace visibility
|
|
|
|
---
|
|
|
|
## 5.3 Freshers / early professionals under 5 years
|
|
|
|
### Main jobs-to-be-done
|
|
|
|
- Get callbacks.
|
|
- Convert interviews.
|
|
- Switch role/field or grow compensation.
|
|
- Build confidence and sharper positioning.
|
|
|
|
### Suggested 30-day plan themes
|
|
|
|
- **“Callback Recovery Sprint”** for no callbacks.
|
|
- **“Interview Conversion Sprint”** for interviews not converting.
|
|
- **“Role Switch Sprint”** for career transition.
|
|
|
|
### Example tasks
|
|
|
|
#### Task: Diagnose why callbacks are low
|
|
|
|
Service: Resume / Q Score
|
|
|
|
Subtasks:
|
|
|
|
1. Select target role.
|
|
2. Upload or open resume.
|
|
3. Run resume role-fit audit.
|
|
4. Save top 3 fixes.
|
|
|
|
Curator first question:
|
|
|
|
> What role are you applying for most often right now?
|
|
|
|
CTA:
|
|
|
|
- “Open resume audit”
|
|
|
|
Signals:
|
|
|
|
- resume fit
|
|
- role alignment
|
|
- application readiness
|
|
|
|
#### Task: Rewrite your headline and summary
|
|
|
|
Service: Social / Resume
|
|
|
|
Subtasks:
|
|
|
|
1. Capture current role and target role.
|
|
2. Capture 2 strongest proof points.
|
|
3. Generate headline options.
|
|
4. Save best version.
|
|
|
|
Curator first question:
|
|
|
|
> What target role should your profile headline sell you for?
|
|
|
|
CTA:
|
|
|
|
- “Draft profile update”
|
|
|
|
Signals:
|
|
|
|
- profile clarity
|
|
- recruiter discoverability
|
|
|
|
#### Task: Generate interview preview for target role
|
|
|
|
Service: Interview
|
|
|
|
Subtasks:
|
|
|
|
1. Confirm role.
|
|
2. Pick round type: behavioral, role-related, warm-up.
|
|
3. Generate preview.
|
|
4. Practice and review feedback.
|
|
|
|
Curator first question:
|
|
|
|
> Which role and interview round should I prepare for you today?
|
|
|
|
CTA:
|
|
|
|
- “Open interview preview”
|
|
|
|
Signals:
|
|
|
|
- interview practice
|
|
- answer structure
|
|
- confidence
|
|
|
|
#### Task: Practice salary expectation answer
|
|
|
|
Service: Roleplay
|
|
|
|
Subtasks:
|
|
|
|
1. Capture current/target salary or range.
|
|
2. Capture role and recruiter context.
|
|
3. Generate negotiation roleplay preview.
|
|
4. Practice answer.
|
|
|
|
Curator first question:
|
|
|
|
> What salary conversation do you need to prepare for: recruiter screen, offer call, or manager discussion?
|
|
|
|
CTA:
|
|
|
|
- “Open roleplay preview”
|
|
|
|
Signals:
|
|
|
|
- negotiation confidence
|
|
- communication readiness
|
|
|
|
#### Task: Build one STAR story
|
|
|
|
Service: Interview / Resume
|
|
|
|
Subtasks:
|
|
|
|
1. Pick one work/project situation.
|
|
2. Capture task/action/result.
|
|
3. Convert to STAR answer.
|
|
4. Practice it in interview preview.
|
|
|
|
Curator first question:
|
|
|
|
> Which achievement or challenge should we turn into a STAR story today?
|
|
|
|
CTA:
|
|
|
|
- “Open interview preview”
|
|
|
|
Signals:
|
|
|
|
- story bank depth
|
|
- answer quality
|
|
|
|
---
|
|
|
|
## 5.4 Experienced professionals above 5 years
|
|
|
|
### Main jobs-to-be-done
|
|
|
|
- Move into leadership or higher compensation.
|
|
- Communicate strategic impact.
|
|
- Prepare for senior interviews.
|
|
- Negotiate scope, salary, title, or authority.
|
|
|
|
### Suggested plan theme
|
|
|
|
**“Leadership Readiness Sprint”**
|
|
|
|
### Example tasks
|
|
|
|
#### Task: Translate execution into leadership impact
|
|
|
|
Service: Resume
|
|
|
|
Subtasks:
|
|
|
|
1. Pick one major project.
|
|
2. Capture business outcome, team size, scope.
|
|
3. Rewrite into leadership bullet.
|
|
4. Save to resume.
|
|
|
|
Curator first question:
|
|
|
|
> Which project best proves you can lead beyond individual execution?
|
|
|
|
CTA:
|
|
|
|
- “Open resume workspace”
|
|
|
|
Signals:
|
|
|
|
- leadership proof
|
|
- seniority alignment
|
|
|
|
#### Task: Practice senior stakeholder interview
|
|
|
|
Service: Interview
|
|
|
|
Subtasks:
|
|
|
|
1. Choose target role.
|
|
2. Pick round: leadership, strategy, behavioral.
|
|
3. Generate preview.
|
|
4. Complete mock.
|
|
|
|
Curator first question:
|
|
|
|
> What senior role or leadership round should this mock prepare you for?
|
|
|
|
CTA:
|
|
|
|
- “Open interview preview”
|
|
|
|
Signals:
|
|
|
|
- executive communication
|
|
- senior interview readiness
|
|
|
|
#### Task: Roleplay promotion conversation
|
|
|
|
Service: Roleplay
|
|
|
|
Subtasks:
|
|
|
|
1. Capture desired title/scope.
|
|
2. Capture manager/stakeholder context.
|
|
3. Generate promotion conversation preview.
|
|
4. Practice and refine ask.
|
|
|
|
Curator first question:
|
|
|
|
> What are you asking for: title change, salary increase, larger scope, or leadership opportunity?
|
|
|
|
CTA:
|
|
|
|
- “Open roleplay preview”
|
|
|
|
Signals:
|
|
|
|
- negotiation confidence
|
|
- leadership communication
|
|
|
|
#### Task: Build authority proof post
|
|
|
|
Service: Social
|
|
|
|
Subtasks:
|
|
|
|
1. Pick strategic lesson.
|
|
2. Add one example from your work.
|
|
3. Draft concise post.
|
|
4. Save/publish.
|
|
|
|
Curator first question:
|
|
|
|
> What leadership lesson or strategic insight can you credibly talk about this week?
|
|
|
|
CTA:
|
|
|
|
- “Draft authority post”
|
|
|
|
Signals:
|
|
|
|
- market visibility
|
|
- senior credibility
|
|
|
|
---
|
|
|
|
## 5.5 Freelancers and gig workers
|
|
|
|
### Main jobs-to-be-done
|
|
|
|
- Find clients consistently.
|
|
- Stand out in crowded markets.
|
|
- Price confidently.
|
|
- Build trust online.
|
|
- Move from inconsistent income to predictable pipeline.
|
|
|
|
### Suggested 30-day plan themes
|
|
|
|
- **“First Client Sprint”** for new freelancers.
|
|
- **“Pipeline Stabilizer”** for feast/famine.
|
|
- **“Premium Rate Sprint”** for pricing/positioning.
|
|
|
|
### Example tasks
|
|
|
|
#### Task: Package your offer clearly
|
|
|
|
Service: Resume/Profile/Social
|
|
|
|
Subtasks:
|
|
|
|
1. Define target client.
|
|
2. Define painful problem solved.
|
|
3. Package one clear offer.
|
|
4. Save as profile headline/portfolio intro.
|
|
|
|
Curator first question:
|
|
|
|
> Who do you want to serve first, and what problem do you solve for them?
|
|
|
|
CTA:
|
|
|
|
- “Draft offer profile”
|
|
|
|
Signals:
|
|
|
|
- positioning clarity
|
|
- client readiness
|
|
|
|
#### Task: Practice discovery call
|
|
|
|
Service: Roleplay
|
|
|
|
Subtasks:
|
|
|
|
1. Choose client type.
|
|
2. Define service offered.
|
|
3. Generate discovery call preview.
|
|
4. Practice handling objections.
|
|
|
|
Curator first question:
|
|
|
|
> What kind of client call should we rehearse: first discovery, pricing, scope, or renewal?
|
|
|
|
CTA:
|
|
|
|
- “Open roleplay preview”
|
|
|
|
Signals:
|
|
|
|
- sales confidence
|
|
- client communication
|
|
|
|
#### Task: Build pricing confidence script
|
|
|
|
Service: Roleplay
|
|
|
|
Subtasks:
|
|
|
|
1. Capture current rate and target rate.
|
|
2. Capture service value.
|
|
3. Generate pricing conversation.
|
|
4. Practice saying the rate clearly.
|
|
|
|
Curator first question:
|
|
|
|
> What service are you pricing, and what rate do you want to confidently quote?
|
|
|
|
CTA:
|
|
|
|
- “Open roleplay preview”
|
|
|
|
Signals:
|
|
|
|
- pricing confidence
|
|
- sales readiness
|
|
|
|
#### Task: Turn a client/project into a case study
|
|
|
|
Service: Resume/Profile/Social
|
|
|
|
Subtasks:
|
|
|
|
1. Pick a project.
|
|
2. Capture before/after/result.
|
|
3. Draft case study summary.
|
|
4. Add to portfolio/profile.
|
|
|
|
Curator first question:
|
|
|
|
> Which project best proves the outcome you deliver for clients?
|
|
|
|
CTA:
|
|
|
|
- “Draft case study”
|
|
|
|
Signals:
|
|
|
|
- proof quality
|
|
- trust surface area
|
|
|
|
#### Task: Draft one inbound post
|
|
|
|
Service: Social
|
|
|
|
Subtasks:
|
|
|
|
1. Pick client pain point.
|
|
2. Add quick teaching insight.
|
|
3. Draft post.
|
|
4. Save/publish.
|
|
|
|
Curator first question:
|
|
|
|
> What client problem do you want to be known for solving?
|
|
|
|
CTA:
|
|
|
|
- “Draft LinkedIn post”
|
|
|
|
Signals:
|
|
|
|
- visibility
|
|
- inbound readiness
|
|
|
|
---
|
|
|
|
## 5.6 Solopreneurs and founders
|
|
|
|
### Main jobs-to-be-done
|
|
|
|
- Validate idea.
|
|
- Build public credibility.
|
|
- Find customers, investors, cofounders, or hires.
|
|
- Practice high-stakes conversations.
|
|
- Convert founder identity into trust.
|
|
|
|
### Suggested 30/60-day themes
|
|
|
|
- **“MVP Validation Sprint”**
|
|
- **“First 100 Customers Sprint”**
|
|
- **“Founder Visibility Sprint”**
|
|
- **“Fundraising Readiness Sprint”**
|
|
- **“Cofounder / First Hire Sprint”**
|
|
|
|
### Example tasks
|
|
|
|
#### Task: Clarify founder one-liner
|
|
|
|
Service: Social / Q Score
|
|
|
|
Subtasks:
|
|
|
|
1. Capture product, audience, problem.
|
|
2. Draft one-line positioning.
|
|
3. Compare against current profile.
|
|
4. Save as founder identity statement.
|
|
|
|
Curator first question:
|
|
|
|
> In one sentence, what are you building, for whom, and what painful problem does it solve?
|
|
|
|
CTA:
|
|
|
|
- “Draft founder profile”
|
|
|
|
Signals:
|
|
|
|
- positioning clarity
|
|
- founder credibility
|
|
|
|
#### Task: Practice customer discovery call
|
|
|
|
Service: Roleplay
|
|
|
|
Subtasks:
|
|
|
|
1. Define customer segment.
|
|
2. Define assumption to validate.
|
|
3. Generate discovery roleplay preview.
|
|
4. Practice asking non-leading questions.
|
|
|
|
Curator first question:
|
|
|
|
> Which customer segment should this discovery call simulate?
|
|
|
|
CTA:
|
|
|
|
- “Open roleplay preview”
|
|
|
|
Signals:
|
|
|
|
- customer discovery skill
|
|
- validation readiness
|
|
|
|
#### Task: Practice investor intro
|
|
|
|
Service: Roleplay
|
|
|
|
Subtasks:
|
|
|
|
1. Capture stage: idea, MVP, traction, raise.
|
|
2. Capture traction or proof.
|
|
3. Generate investor conversation preview.
|
|
4. Practice concise pitch and objection handling.
|
|
|
|
Curator first question:
|
|
|
|
> Are you pitching an idea, MVP, traction story, or active fundraise?
|
|
|
|
CTA:
|
|
|
|
- “Open roleplay preview”
|
|
|
|
Signals:
|
|
|
|
- fundraising readiness
|
|
- founder communication
|
|
|
|
#### Task: Prepare first-hire interview
|
|
|
|
Service: Interview / Roleplay
|
|
|
|
Subtasks:
|
|
|
|
1. Define role needed.
|
|
2. Capture what success looks like.
|
|
3. Generate interview or roleplay preview.
|
|
4. Practice evaluating fit.
|
|
|
|
Curator first question:
|
|
|
|
> What key role are you trying to hire or find as a collaborator?
|
|
|
|
CTA:
|
|
|
|
- “Open interview preview” or “Open roleplay preview”
|
|
|
|
Signals:
|
|
|
|
- hiring readiness
|
|
- team-building clarity
|
|
|
|
#### Task: Draft build-in-public update
|
|
|
|
Service: Social
|
|
|
|
Subtasks:
|
|
|
|
1. Pick milestone or learning.
|
|
2. Add founder insight.
|
|
3. Draft post.
|
|
4. Save/publish.
|
|
|
|
Curator first question:
|
|
|
|
> What did you learn or ship this week that would build trust with customers, investors, or collaborators?
|
|
|
|
CTA:
|
|
|
|
- “Draft founder update”
|
|
|
|
Signals:
|
|
|
|
- authority
|
|
- visibility
|
|
- credibility
|
|
|
|
#### Task: Validate pricing or business model
|
|
|
|
Service: Roleplay / Q Score
|
|
|
|
Subtasks:
|
|
|
|
1. Capture pricing hypothesis.
|
|
2. Pick target buyer.
|
|
3. Roleplay pricing conversation.
|
|
4. Save learning.
|
|
|
|
Curator first question:
|
|
|
|
> What price or business model assumption do you need to test first?
|
|
|
|
CTA:
|
|
|
|
- “Open roleplay preview”
|
|
|
|
Signals:
|
|
|
|
- model validation
|
|
- buyer communication
|
|
|
|
---
|
|
|
|
## 6. Service-specific task libraries
|
|
|
|
## 6.1 Interview task library
|
|
|
|
Use for students, interns, freshers, experienced professionals, and founders hiring candidates.
|
|
|
|
Task examples:
|
|
|
|
1. First mock interview for target role.
|
|
2. Behavioral round preview.
|
|
3. Role-related technical/product/design/data round.
|
|
4. Internship return-offer interview.
|
|
5. Senior leadership interview.
|
|
6. Career switch interview.
|
|
7. Founder first-hire interview.
|
|
8. STAR story practice.
|
|
9. Weakness/strength answer practice.
|
|
10. “Tell me about yourself” practice.
|
|
|
|
Standard subtasks:
|
|
|
|
1. Capture target role.
|
|
2. Capture round type.
|
|
3. Capture difficulty or pressure level.
|
|
4. Generate preview.
|
|
5. Complete session.
|
|
6. Review feedback and update Q Score.
|
|
|
|
Default preview params:
|
|
|
|
- role: inferred from onboarding target, user answer, task context.
|
|
- type: behavioral unless task says technical/role-related.
|
|
- difficulty: medium.
|
|
- duration: 5 minutes for streak tasks.
|
|
- source: curator-v1 or daily-mission.
|
|
|
|
Good CTA copy:
|
|
|
|
- “Open interview preview”
|
|
- “Preview your mock interview”
|
|
- “Start from preview”
|
|
|
|
## 6.2 Roleplay task library
|
|
|
|
Use for conversations where the user needs to speak with another person.
|
|
|
|
Task examples:
|
|
|
|
1. Recruiter screen practice.
|
|
2. Salary expectation conversation.
|
|
3. Offer negotiation.
|
|
4. Manager promotion ask.
|
|
5. Internship return-offer check-in.
|
|
6. Client discovery call.
|
|
7. Freelance pricing call.
|
|
8. Scope creep conversation.
|
|
9. Investor intro.
|
|
10. Customer discovery.
|
|
11. Cofounder alignment conversation.
|
|
12. Difficult stakeholder conversation.
|
|
|
|
Standard subtasks:
|
|
|
|
1. Capture scenario.
|
|
2. Capture counterpart.
|
|
3. Capture desired outcome.
|
|
4. Generate preview.
|
|
5. Practice.
|
|
6. Save best script or learning.
|
|
|
|
Default preview params:
|
|
|
|
- scenario: inferred from task and answer.
|
|
- counterpart: recruiter, manager, client, investor, customer, cofounder, stakeholder.
|
|
- outcome: offer, feedback, price agreement, intro, validation, next step.
|
|
- source: curator-v1 or daily-mission.
|
|
|
|
Good CTA copy:
|
|
|
|
- “Open roleplay preview”
|
|
- “Practice this conversation”
|
|
- “Preview roleplay scenario”
|
|
|
|
## 6.3 Resume/profile task library
|
|
|
|
Task examples:
|
|
|
|
1. Resume baseline upload.
|
|
2. Role-fit audit.
|
|
3. Rewrite top 3 bullets.
|
|
4. Add project proof.
|
|
5. Convert internship to experience.
|
|
6. Convert freelance project to case study.
|
|
7. Founder profile rewrite.
|
|
8. Leadership impact rewrite.
|
|
9. LinkedIn headline and summary.
|
|
10. Portfolio/GitHub audit.
|
|
|
|
Standard subtasks:
|
|
|
|
1. Capture target role or audience.
|
|
2. Import/upload artifact.
|
|
3. Identify top gap.
|
|
4. Generate rewrite.
|
|
5. Save changes.
|
|
|
|
Good CTA copy:
|
|
|
|
- “Open resume workspace”
|
|
- “Review profile audit”
|
|
- “Rewrite this proof point”
|
|
|
|
## 6.4 Q Score task library
|
|
|
|
Task examples:
|
|
|
|
1. Complete baseline Q Score.
|
|
2. Review weakest readiness driver.
|
|
3. Compare current vs target role.
|
|
4. Check confidence after mock interview.
|
|
5. Update proof ledger after resume change.
|
|
6. Weekly progress check-in.
|
|
7. Readiness gap summary.
|
|
|
|
Standard subtasks:
|
|
|
|
1. Confirm target.
|
|
2. Review score breakdown.
|
|
3. Pick one driver to improve.
|
|
4. Route to service action.
|
|
5. Recalculate signal.
|
|
|
|
Good CTA copy:
|
|
|
|
- “Review Q Score”
|
|
- “See readiness gaps”
|
|
- “Pick next driver”
|
|
|
|
## 6.5 Social / branding task library
|
|
|
|
Task examples:
|
|
|
|
1. LinkedIn headline rewrite.
|
|
2. About section rewrite.
|
|
3. Weekly project post.
|
|
4. Founder build-in-public update.
|
|
5. Freelance case study post.
|
|
6. Student learning proof post.
|
|
7. Leadership insight post.
|
|
8. Recruiter-facing profile polish.
|
|
9. Investor-facing founder profile polish.
|
|
|
|
Standard subtasks:
|
|
|
|
1. Pick audience.
|
|
2. Pick proof/insight.
|
|
3. Draft copy.
|
|
4. Save/publish.
|
|
5. Track profile signal.
|
|
|
|
Good CTA copy:
|
|
|
|
- “Draft post”
|
|
- “Update profile”
|
|
- “Save authority proof”
|
|
|
|
---
|
|
|
|
## 7. Three-suggestion weekly progress model
|
|
|
|
When a user clicks the streak/week progress component, show three suggestions that map to their onboarding state.
|
|
|
|
### Suggested formula
|
|
|
|
1. **One measurement task**: Q Score / readiness check.
|
|
2. **One proof task**: resume/profile/project/case study.
|
|
3. **One practice task**: interview or roleplay preview.
|
|
|
|
### Examples by ICP
|
|
|
|
#### Student
|
|
|
|
1. “Pick your first target role” - Q Score / Pathways.
|
|
2. “Turn one project into resume proof” - Resume.
|
|
3. “Practice your first mock interview” - Interview.
|
|
|
|
#### Intern
|
|
|
|
1. “Capture internship impact” - Resume.
|
|
2. “Practice manager check-in” - Roleplay.
|
|
3. “Prepare return-offer interview” - Interview.
|
|
|
|
#### Fresher under 5 years
|
|
|
|
1. “Diagnose why callbacks are low” - Resume/Q Score.
|
|
2. “Build one STAR story” - Interview.
|
|
3. “Practice salary expectation answer” - Roleplay.
|
|
|
|
#### Freelancer
|
|
|
|
1. “Package your offer clearly” - Profile.
|
|
2. “Practice discovery call” - Roleplay.
|
|
3. “Draft one inbound post” - Social.
|
|
|
|
#### Founder / solopreneur
|
|
|
|
1. “Clarify founder one-liner” - Social/Q Score.
|
|
2. “Practice customer discovery call” - Roleplay.
|
|
3. “Draft build-in-public update” - Social.
|
|
|
|
---
|
|
|
|
## 8. Example generated curator tasks
|
|
|
|
These are examples of what the backend curator could generate as `CuratorTask`-like objects.
|
|
|
|
### Student example
|
|
|
|
```json
|
|
{
|
|
"title": "Prepare your first PM interview preview",
|
|
"subtitle": "Turn your student projects into a confident first-round story.",
|
|
"serviceId": "interview-service",
|
|
"serviceName": "Interview service",
|
|
"cta": "Open interview preview",
|
|
"contextNarrative": "The user is a student/recent grad targeting product roles and needs confidence before first interviews.",
|
|
"subtasks": [
|
|
"Confirm target role and round type",
|
|
"Pick one project to use as proof",
|
|
"Generate mock interview preview",
|
|
"Complete practice and review feedback"
|
|
],
|
|
"signals": ["interview.confidence", "role_alignment", "communication_clarity"]
|
|
}
|
|
```
|
|
|
|
### Freelancer example
|
|
|
|
```json
|
|
{
|
|
"title": "Practice your next pricing conversation",
|
|
"subtitle": "Build confidence quoting your rate without discounting too early.",
|
|
"serviceId": "roleplay-service",
|
|
"serviceName": "Roleplay service",
|
|
"cta": "Open roleplay preview",
|
|
"contextNarrative": "The user is a freelancer who selected pricing confidently as a blocker.",
|
|
"subtasks": [
|
|
"Capture service and target client",
|
|
"Capture current and target rate",
|
|
"Generate pricing roleplay preview",
|
|
"Practice objection handling"
|
|
],
|
|
"signals": ["pricing_confidence", "client_communication", "sales_readiness"]
|
|
}
|
|
```
|
|
|
|
### Founder example
|
|
|
|
```json
|
|
{
|
|
"title": "Rehearse your customer discovery call",
|
|
"subtitle": "Validate the riskiest assumption before building more.",
|
|
"serviceId": "roleplay-service",
|
|
"serviceName": "Roleplay service",
|
|
"cta": "Open roleplay preview",
|
|
"contextNarrative": "The user is a first-time founder at idea/MVP stage trying to validate customers.",
|
|
"subtasks": [
|
|
"Choose customer segment",
|
|
"Capture assumption to validate",
|
|
"Generate discovery call preview",
|
|
"Save learning after practice"
|
|
],
|
|
"signals": ["customer_discovery", "validation_readiness", "founder_communication"]
|
|
}
|
|
```
|
|
|
|
---
|
|
|
|
## 9. Curator prompt guidance
|
|
|
|
The prompt should make the curator act like a productized growth coach, not a generic chatbot.
|
|
|
|
### Voice
|
|
|
|
- Warm, direct, concise.
|
|
- One question at a time.
|
|
- No long motivational paragraphs.
|
|
- No internal route names in text.
|
|
- Always explain the business value in plain words.
|
|
|
|
### First-turn examples
|
|
|
|
Interview task:
|
|
|
|
> This is your practice step for today. What role or interview round should I prepare the preview for?
|
|
|
|
Roleplay task:
|
|
|
|
> Let's rehearse the conversation before it matters. Who are you speaking with: recruiter, manager, client, investor, or customer?
|
|
|
|
Resume task:
|
|
|
|
> Let's turn your experience into proof. What role or audience should this resume section target?
|
|
|
|
Founder task:
|
|
|
|
> Let's make this useful for your next milestone. Are you trying to validate customers, raise, hire, or build visibility first?
|
|
|
|
### Handoff-ready examples
|
|
|
|
Interview:
|
|
|
|
> Got it. I prepared a mock interview preview for Product Manager behavioral practice. Open the preview to start or adjust the setup.
|
|
|
|
Roleplay:
|
|
|
|
> Got it. I prepared a roleplay preview for a salary conversation with a recruiter. Open the preview to practice or adjust details.
|
|
|
|
Resume:
|
|
|
|
> Saved. Open the resume workspace and we will turn this into role-fit proof.
|
|
|
|
---
|
|
|
|
## 10. UX requirements for streak chat
|
|
|
|
The DailyRetentionStrip chat should show:
|
|
|
|
1. Assistant message.
|
|
2. User answer.
|
|
3. Assistant summary.
|
|
4. Service preview card when handoff is ready.
|
|
5. Persistent CTA even after subtask is marked complete.
|
|
|
|
CTA card fields:
|
|
|
|
- Eyebrow: `INTERVIEW PREVIEW`, `ROLEPLAY PREVIEW`, `RESUME WORKSPACE`, `Q SCORE CHECK`.
|
|
- Title: clear outcome.
|
|
- Subtitle: why this helps.
|
|
- Details: role, scenario, difficulty, duration, service.
|
|
- Button: action verb.
|
|
|
|
Important: for interview and roleplay, the CTA should route to preview or preview-equivalent state, not a blank setup screen.
|
|
|
|
---
|
|
|
|
## 11. Prioritization matrix
|
|
|
|
### If user blocker is “not getting callbacks”
|
|
|
|
Priority:
|
|
|
|
1. Resume role-fit audit.
|
|
2. LinkedIn/profile rewrite.
|
|
3. Interview warm-up only after proof improves.
|
|
|
|
### If blocker is “interviews not converting”
|
|
|
|
Priority:
|
|
|
|
1. Interview preview.
|
|
2. STAR story practice.
|
|
3. Roleplay recruiter or salary conversation.
|
|
|
|
### If blocker is “don't know where to start”
|
|
|
|
Priority:
|
|
|
|
1. Q Score baseline.
|
|
2. Pathway/target role selection.
|
|
3. One small proof task.
|
|
|
|
### If blocker is “pricing confidently”
|
|
|
|
Priority:
|
|
|
|
1. Offer packaging.
|
|
2. Pricing roleplay.
|
|
3. Case study proof.
|
|
|
|
### If blocker is “fundraising”
|
|
|
|
Priority:
|
|
|
|
1. Founder one-liner.
|
|
2. Investor roleplay.
|
|
3. Founder authority post.
|
|
|
|
### If blocker is “finding customers”
|
|
|
|
Priority:
|
|
|
|
1. Customer segment clarity.
|
|
2. Discovery roleplay.
|
|
3. Build-in-public/customer pain post.
|
|
|
|
---
|
|
|
|
## 12. Implementation implications
|
|
|
|
For the upcoming engineering pass:
|
|
|
|
1. The curator prompt should be externalized so these rules can be edited without TypeScript changes.
|
|
2. `CuratorTask` generation should use onboarding answers to pick ICP, blocker, goal, urgency, service, and task library.
|
|
3. The streak chat should not reuse TalkToMe route/component; it should only borrow UX patterns.
|
|
4. Interview and roleplay handoffs should route directly to preview or preview-equivalent pages with default params.
|
|
5. Handoff CTA should be deterministic and persistent.
|
|
6. Completion should not hide the next action.
|
|
7. Every daily task should map to at least one Q Score/progress signal.
|
|
|
|
---
|
|
|
|
## 13. Open product questions
|
|
|
|
1. Should students get a 30-day default and professionals/founders get 60-day default, or should plan length depend on urgency?
|
|
2. Should Q Score visible baseline always start at 35 after onboarding, or vary by imported proof quality?
|
|
3. Should streak completion require service completion, or just curator context capture?
|
|
4. Should interview/roleplay preview generation count as a streak completion, or only completed session/review?
|
|
5. Should freelancers and founders see “Q Score” language, “QX Score”, or a more business-facing label like “Credibility Score”?
|
|
6. Should social branding be a first-class service in the curator registry for all ICPs?
|
|
7. Should preview cards support “Change details” quick action directly inside the chat?
|
|
|
|
|
|
---
|
|
|
|
# 14. Literal 30-day progression examples by ICP
|
|
|
|
Use these as concrete seed examples for curator plans. Each day has three suggestions. Each suggestion includes small subtasks. In production, pick/modify based on onboarding signals, imported resume/LinkedIn/portfolio data, service history, and completion events.
|
|
|
|
## 14.1 Student / recent grad: First Role Readiness Sprint
|
|
|
|
Onboarding pattern: `individual + student/recent grad + 0-2 years + role/skills + before graduation/within 6 months`.
|
|
|
|
### Day 1
|
|
1. **Set your first target role** — subtasks: pick role family; choose target role; save role goal.
|
|
2. **Start Q Score baseline** — subtasks: review baseline score; pick weakest driver; save first improvement focus.
|
|
3. **Upload resume or LinkedIn** — subtasks: import profile; confirm education/projects; mark missing proof.
|
|
|
|
### Day 2
|
|
1. **Turn one project into proof** — subtasks: choose project; capture problem/action/result; draft 2 bullets.
|
|
2. **Prepare first mock interview preview** — subtasks: confirm role; select behavioral round; open preview.
|
|
3. **Draft student profile headline** — subtasks: pick target audience; write headline; save best version.
|
|
|
|
### Day 3
|
|
1. **Practice “Tell me about yourself”** — subtasks: capture background; pick one project proof; open interview preview.
|
|
2. **Map role requirements** — subtasks: list 3 must-have skills; mark known gaps; choose one gap to fix.
|
|
3. **Create first credibility post** — subtasks: pick project insight; draft post; save/publish.
|
|
|
|
### Day 4
|
|
1. **Resume gap scan** — subtasks: compare resume to role; identify weak section; open resume workspace.
|
|
2. **Roleplay recruiter intro** — subtasks: choose recruiter scenario; define desired next step; open roleplay preview.
|
|
3. **Build proof bank v1** — subtasks: list projects; add metrics; tag best 3 for interviews.
|
|
|
|
### Day 5
|
|
1. **Mock interview: easy warm-up** — subtasks: open preview; complete 5-min round; review feedback.
|
|
2. **Rewrite project bullet** — subtasks: select weak bullet; add action verb; add outcome.
|
|
3. **Q Score check-in** — subtasks: review changed drivers; log confidence; choose weekend focus.
|
|
|
|
### Day 6
|
|
1. **Prepare application shortlist** — subtasks: choose 5 roles; score fit; save top 2.
|
|
2. **Practice common HR screen** — subtasks: choose fresher screen; capture expected questions; open roleplay preview.
|
|
3. **Polish LinkedIn About** — subtasks: draft 3-line summary; add role target; save update.
|
|
|
|
### Day 7
|
|
1. **Weekly readiness review** — subtasks: review completed tasks; note score movement; pick next week theme.
|
|
2. **Create STAR story #1** — subtasks: choose challenge; write situation/task/action/result; save story.
|
|
3. **Apply to two aligned roles** — subtasks: pick roles; tailor resume headline; record applications.
|
|
|
|
### Day 8
|
|
1. **Skill gap micro-plan** — subtasks: pick one missing skill; choose resource; schedule 3 practice blocks.
|
|
2. **Interview preview: role-related** — subtasks: confirm role; select role-related round; open preview.
|
|
3. **Improve education/project section** — subtasks: remove filler; add relevant coursework; add project result.
|
|
|
|
### Day 9
|
|
1. **Practice project explanation** — subtasks: pick project; define architecture/approach; open interview preview.
|
|
2. **Draft outreach message** — subtasks: choose alumni/recruiter; write 80-word note; save/send.
|
|
3. **Update Q Score proof ledger** — subtasks: add project proof; tag skill; refresh readiness driver.
|
|
|
|
### Day 10
|
|
1. **Mock interview: medium pressure** — subtasks: open preview; complete round; save feedback.
|
|
2. **Fix top resume weakness** — subtasks: select weakness; rewrite section; compare before/after.
|
|
3. **Roleplay networking call** — subtasks: choose alumni scenario; define ask; open roleplay preview.
|
|
|
|
### Day 11
|
|
1. **Build portfolio/GitHub proof** — subtasks: select repo/project; write README summary; add outcome.
|
|
2. **Practice weakness answer** — subtasks: choose honest weakness; add improvement proof; open interview preview.
|
|
3. **Draft learning post** — subtasks: pick technical lesson; write concise post; save/publish.
|
|
|
|
### Day 12
|
|
1. **Application tailoring sprint** — subtasks: select one JD; map keywords; tailor 3 bullets.
|
|
2. **Roleplay recruiter callback** — subtasks: define screen goal; practice intro; save best answer.
|
|
3. **Q Score confidence pulse** — subtasks: rate confidence; compare to day 1; choose next practice.
|
|
|
|
### Day 13
|
|
1. **Mock interview review loop** — subtasks: read feedback; pick one weak pattern; generate next preview.
|
|
2. **Build STAR story #2** — subtasks: choose teamwork example; structure STAR; save story.
|
|
3. **Profile credibility check** — subtasks: review headline/About; add project link; save update.
|
|
|
|
### Day 14
|
|
1. **Week 2 review** — subtasks: review applications/practice; log wins; pick week 3 conversion goal.
|
|
2. **Apply to three roles** — subtasks: select roles; tailor resume; record status.
|
|
3. **Practice first-round interview** — subtasks: open preview; complete round; save feedback.
|
|
|
|
### Day 15
|
|
1. **Build interview story bank** — subtasks: list 5 stories; tag leadership/teamwork/problem-solving; save.
|
|
2. **Roleplay salary expectation** — subtasks: define range; practice recruiter answer; save script.
|
|
3. **Improve resume summary** — subtasks: write target summary; remove vague words; save.
|
|
|
|
### Day 16
|
|
1. **Technical/role skill drill** — subtasks: pick weak topic; answer 3 questions; log confidence.
|
|
2. **Mock interview: targeted weakness** — subtasks: choose weak area; open preview; practice.
|
|
3. **Draft recruiter follow-up** — subtasks: choose application; write follow-up; send/record.
|
|
|
|
### Day 17
|
|
1. **Project deep-dive practice** — subtasks: select project; explain tradeoffs; open interview preview.
|
|
2. **Portfolio polish** — subtasks: add screenshot/demo link; write impact; save.
|
|
3. **Q Score readiness check** — subtasks: review score; identify lowest service signal; route next action.
|
|
|
|
### Day 18
|
|
1. **Roleplay group discussion** — subtasks: define scenario; practice concise contribution; save feedback.
|
|
2. **Resume bullet metrics pass** — subtasks: find vague bullets; add numbers/scope; save.
|
|
3. **Publish proof post** — subtasks: pick project outcome; draft; publish/save.
|
|
|
|
### Day 19
|
|
1. **Mock interview: medium full round** — subtasks: open preview; complete; review feedback.
|
|
2. **Application quality audit** — subtasks: review last 5 applications; identify mismatch; adjust target list.
|
|
3. **Networking ask practice** — subtasks: pick contact; roleplay ask; send message.
|
|
|
|
### Day 20
|
|
1. **Create final fresher pitch** — subtasks: draft 60-sec pitch; practice; save best version.
|
|
2. **Interview confidence repair** — subtasks: pick anxiety point; run warm-up preview; note improvement.
|
|
3. **Role-fit score update** — subtasks: compare proof to JD; update gaps; choose next proof.
|
|
|
|
### Day 21
|
|
1. **Week 3 conversion review** — subtasks: review callbacks; review mock scores; choose final sprint focus.
|
|
2. **Prepare top-company version** — subtasks: choose target company; tailor resume; create interview preview.
|
|
3. **Follow-up queue** — subtasks: list pending applications; draft follow-ups; send 2.
|
|
|
|
### Day 22
|
|
1. **Behavioral story refinement** — subtasks: choose weakest STAR; tighten action/result; practice.
|
|
2. **Roleplay recruiter screen** — subtasks: simulate screen; practice compensation/location; save script.
|
|
3. **LinkedIn activity boost** — subtasks: comment on 3 posts; publish one insight; record.
|
|
|
|
### Day 23
|
|
1. **Mock interview: hard question set** — subtasks: open preview; complete; review feedback.
|
|
2. **Resume final pass** — subtasks: grammar scan; role keyword scan; export version.
|
|
3. **Opportunity shortlist refresh** — subtasks: find 5 new roles; rank fit; save top 3.
|
|
|
|
### Day 24
|
|
1. **Practice rejection recovery** — subtasks: roleplay rejection; ask for feedback; save response.
|
|
2. **Case/project mini-deck** — subtasks: outline project; add result; create shareable summary.
|
|
3. **Q Score improvement log** — subtasks: compare day 1/day 24; note drivers; choose final week target.
|
|
|
|
### Day 25
|
|
1. **Interview preview for top role** — subtasks: choose best role; open preview; complete practice.
|
|
2. **Referral request roleplay** — subtasks: pick contact; practice ask; send message.
|
|
3. **Update proof bank** — subtasks: add new stories; tag to questions; save.
|
|
|
|
### Day 26
|
|
1. **Application sprint** — subtasks: tailor resume; apply to 3 roles; record status.
|
|
2. **Confidence pitch practice** — subtasks: open roleplay; practice intro; save script.
|
|
3. **Profile final polish** — subtasks: headline; About; featured project link.
|
|
|
|
### Day 27
|
|
1. **Mock interview replay** — subtasks: rerun weakest area; compare feedback; save improvement.
|
|
2. **Prepare interview questions to ask** — subtasks: draft 5 questions; tailor to role; save.
|
|
3. **Networking follow-up** — subtasks: follow up with 3 contacts; record replies.
|
|
|
|
### Day 28
|
|
1. **Final readiness review** — subtasks: review Q Score; review resume; review interview feedback.
|
|
2. **Create next 30-day plan** — subtasks: choose goal; select service focus; schedule cadence.
|
|
3. **Publish progress proof** — subtasks: draft post; highlight learning; publish/save.
|
|
|
|
### Day 29
|
|
1. **Offer-readiness roleplay** — subtasks: practice offer call; salary answer; closing question.
|
|
2. **Top role interview preview** — subtasks: open preview; complete; save feedback.
|
|
3. **Resume export and versioning** — subtasks: export PDF; name by role; save.
|
|
|
|
### Day 30
|
|
1. **30-day outcome review** — subtasks: compare baseline/current; record wins; identify next gap.
|
|
2. **Choose next sprint** — subtasks: interview conversion, callbacks, skills, or networking; save.
|
|
3. **Celebrate streak and unlock next plan** — subtasks: claim reward; set cadence; start next stage.
|
|
|
|
## 14.2 Intern: Intern-to-Offer Sprint
|
|
|
|
Onboarding pattern: `individual + student/recent grad or 0-2 years + employed/internship context + role/pay/grow`.
|
|
|
|
### Day 1
|
|
1. **Define internship outcome** — subtasks: choose return offer/feedback/project impact; save goal; set deadline.
|
|
2. **Capture current project** — subtasks: describe project; identify stakeholder; list expected result.
|
|
3. **Start Q Score baseline** — subtasks: review score; pick communication/proof driver; save focus.
|
|
|
|
### Day 2
|
|
1. **Practice manager check-in** — subtasks: define ask; capture manager context; open roleplay preview.
|
|
2. **Turn internship work into proof** — subtasks: pick task; capture action/result; draft resume bullet.
|
|
3. **Write weekly update v1** — subtasks: list shipped work; list blockers; draft update.
|
|
|
|
### Day 3
|
|
1. **Clarify success metrics** — subtasks: list project KPIs; ask what good looks like; save metrics.
|
|
2. **Roleplay feedback request** — subtasks: define feedback needed; practice ask; save script.
|
|
3. **Update resume internship section** — subtasks: add company/team; add project; add first bullet.
|
|
|
|
### Day 4
|
|
1. **Prepare return-offer interview preview** — subtasks: confirm role; select behavioral; open preview.
|
|
2. **Stakeholder map** — subtasks: list manager/mentor/peer; identify influence; plan one touchpoint.
|
|
3. **Draft LinkedIn learning post** — subtasks: pick lesson; remove confidential details; draft.
|
|
|
|
### Day 5
|
|
1. **Mock interview warm-up** — subtasks: open preview; complete 5-min round; review feedback.
|
|
2. **Manager update roleplay** — subtasks: simulate status update; practice concise wording; save.
|
|
3. **Q Score pulse** — subtasks: log confidence; choose next week improvement; save.
|
|
|
|
### Day 6
|
|
1. **Build impact log** — subtasks: create weekly wins list; add metric/evidence; save proof bank.
|
|
2. **Ask for better scope** — subtasks: define desired project; roleplay ask; prepare message.
|
|
3. **Improve internship bullet** — subtasks: add action verb; add metric; save resume update.
|
|
|
|
### Day 7
|
|
1. **Week 1 internship review** — subtasks: review project progress; identify blocker; choose next action.
|
|
2. **Prepare mentor conversation** — subtasks: define question; roleplay mentor chat; save ask.
|
|
3. **Publish learning proof** — subtasks: finalize post; publish/save; record signal.
|
|
|
|
### Day 8
|
|
1. **Return-offer readiness check** — subtasks: identify requirements; compare proof; choose gap.
|
|
2. **Interview preview: project deep dive** — subtasks: choose project; open preview; practice.
|
|
3. **Draft manager check-in email** — subtasks: summarize progress; ask for feedback; send/save.
|
|
|
|
### Day 9
|
|
1. **Practice conflict/blocker conversation** — subtasks: define blocker; roleplay manager discussion; save script.
|
|
2. **Document project decisions** — subtasks: list decisions; note rationale; add to proof bank.
|
|
3. **Resume proof pass** — subtasks: add collaboration detail; add tool/skill; save.
|
|
|
|
### Day 10
|
|
1. **Mock return-offer round** — subtasks: open preview; complete; review feedback.
|
|
2. **Peer feedback request** — subtasks: identify peer; draft ask; send.
|
|
3. **Q Score update** — subtasks: add internship proof; check driver movement; choose next task.
|
|
|
|
### Day 11
|
|
1. **Prepare final project narrative** — subtasks: write before/action/after; identify metric; save.
|
|
2. **Roleplay full-time conversion ask** — subtasks: define timing; practice ask; save script.
|
|
3. **Profile headline update** — subtasks: add internship role; add target role; save.
|
|
|
|
### Day 12
|
|
1. **Practice technical/project questions** — subtasks: list 5 likely questions; open interview preview; practice.
|
|
2. **Manager visibility touchpoint** — subtasks: choose update; send concise note; record response.
|
|
3. **Build portfolio artifact** — subtasks: anonymize project; write summary; save.
|
|
|
|
### Day 13
|
|
1. **Feedback synthesis** — subtasks: collect feedback; identify pattern; choose improvement.
|
|
2. **Roleplay receiving criticism** — subtasks: simulate feedback; practice response; save.
|
|
3. **Resume internship finalization v1** — subtasks: tighten bullets; add metrics; export draft.
|
|
|
|
### Day 14
|
|
1. **Week 2 review** — subtasks: review impact log; review feedback; set conversion action.
|
|
2. **Interview replay on weakness** — subtasks: choose weak topic; open preview; practice.
|
|
3. **Draft thank-you / relationship note** — subtasks: choose mentor; write note; send/save.
|
|
|
|
### Day 15
|
|
1. **Full-time offer path map** — subtasks: identify decision maker; timeline; required proof.
|
|
2. **Roleplay offer conversation** — subtasks: define ask; open roleplay preview; practice.
|
|
3. **Strengthen project proof** — subtasks: add metric; add stakeholder quote; save.
|
|
|
|
### Day 16
|
|
1. **Mock interview: medium pressure** — subtasks: open preview; complete; review.
|
|
2. **Prepare demo/update deck** — subtasks: outline 3 slides; add result; save.
|
|
3. **LinkedIn credibility update** — subtasks: draft internship lesson; publish/save.
|
|
|
|
### Day 17
|
|
1. **Ask for explicit feedback** — subtasks: draft 3 questions; roleplay ask; send.
|
|
2. **Roleplay prioritization discussion** — subtasks: define conflict; practice tradeoff explanation; save.
|
|
3. **Q Score signal review** — subtasks: review communication/proof; select lowest driver; route task.
|
|
|
|
### Day 18
|
|
1. **Return-offer interview preview** — subtasks: role; behavioral; open preview; practice.
|
|
2. **Manager one-on-one prep** — subtasks: agenda; wins; asks; send/save.
|
|
3. **Resume role-fit tailoring** — subtasks: choose post-internship role; tailor bullets; save.
|
|
|
|
### Day 19
|
|
1. **Practice project storytelling** — subtasks: prepare 90-sec story; open interview; save best answer.
|
|
2. **Internal networking task** — subtasks: pick team member; write intro; schedule chat.
|
|
3. **Impact log refresh** — subtasks: add week wins; add blockers solved; save.
|
|
|
|
### Day 20
|
|
1. **Roleplay conversion close** — subtasks: practice direct ask; handle hesitation; save script.
|
|
2. **Mock interview feedback loop** — subtasks: compare attempts; pick improvement; schedule next.
|
|
3. **Profile polish** — subtasks: update headline; add internship proof; save.
|
|
|
|
### Day 21
|
|
1. **Week 3 conversion review** — subtasks: assess offer odds; identify missing proof; plan final week.
|
|
2. **Prepare final presentation** — subtasks: outline impact; add metric; rehearse.
|
|
3. **Q Score progress check** — subtasks: compare baseline/current; choose final improvement.
|
|
|
|
### Day 22
|
|
1. **Practice final presentation Q&A** — subtasks: list likely questions; open interview preview; practice.
|
|
2. **Roleplay manager decision meeting** — subtasks: define outcome; practice ask; save.
|
|
3. **Resume final internship bullets** — subtasks: refine 3 bullets; export role version; save.
|
|
|
|
### Day 23
|
|
1. **Stakeholder thank-you loop** — subtasks: list people; write notes; send.
|
|
2. **Mock interview hard round** — subtasks: open preview; complete; review.
|
|
3. **External backup plan** — subtasks: choose 5 roles; tailor resume; save shortlist.
|
|
|
|
### Day 24
|
|
1. **Promotion/return-offer script** — subtasks: write ask; practice; save.
|
|
2. **Portfolio case study** — subtasks: anonymize project; write challenge/action/result; save.
|
|
3. **LinkedIn post final** — subtasks: draft; review confidentiality; publish/save.
|
|
|
|
### Day 25
|
|
1. **Offer conversation preview** — subtasks: choose roleplay; set counterpart manager; practice.
|
|
2. **Interview final polish** — subtasks: practice top 3 answers; save feedback.
|
|
3. **Q Score readiness summary** — subtasks: review signals; save final sprint note; choose next.
|
|
|
|
### Day 26
|
|
1. **Ask for recommendation/referral** — subtasks: choose person; draft ask; roleplay if needed.
|
|
2. **Application backup sprint** — subtasks: apply to 3 roles; record status; follow up.
|
|
3. **Manager update final** — subtasks: summarize impact; state interest; send.
|
|
|
|
### Day 27
|
|
1. **Decision meeting rehearsal** — subtasks: roleplay; practice compensation/role scope; save script.
|
|
2. **Resume export** — subtasks: final grammar; export PDF; save version.
|
|
3. **Proof bank finalization** — subtasks: tag stories; tag metrics; save.
|
|
|
|
### Day 28
|
|
1. **Final internship review** — subtasks: compare goals; capture outcomes; identify next move.
|
|
2. **Mock interview replay** — subtasks: rerun weakness; compare feedback; save.
|
|
3. **Relationship maintenance plan** — subtasks: list contacts; schedule follow-ups; save.
|
|
|
|
### Day 29
|
|
1. **Offer or next-role roleplay** — subtasks: choose scenario; open preview; practice.
|
|
2. **Q Score closeout** — subtasks: compare day 1/day 29; record evidence; choose next sprint.
|
|
3. **Publish milestone update** — subtasks: draft; review; publish/save.
|
|
|
|
### Day 30
|
|
1. **Intern-to-offer outcome review** — subtasks: record offer/status; note lessons; choose next plan.
|
|
2. **Start next sprint** — subtasks: return offer, external search, skill gap, or leadership; save.
|
|
3. **Claim streak milestone** — subtasks: review streak; claim reward; schedule cadence.
|
|
|
|
## 14.3 Fresher / early professional under 5 years: Callback-to-Offer Sprint
|
|
|
|
Onboarding pattern: `individual + 0-2 or 2-5 years + hunting/between/employed + callbacks/interviews/profile/pay/switch`.
|
|
|
|
### Day 1
|
|
1. **Choose your target role** — subtasks: pick role; pick industry; save goal.
|
|
2. **Run Q Score baseline** — subtasks: review score; choose weakest driver; save focus.
|
|
3. **Import resume/profile** — subtasks: upload resume; connect LinkedIn; mark missing proof.
|
|
|
|
### Day 2
|
|
1. **Resume role-fit audit** — subtasks: select target JD; compare resume; save top 3 fixes.
|
|
2. **Interview warm-up preview** — subtasks: choose role; open preview; practice.
|
|
3. **Rewrite profile headline** — subtasks: target role; proof point; save headline.
|
|
|
|
### Day 3
|
|
1. **Callback blocker diagnosis** — subtasks: review applications; identify mismatch; update target list.
|
|
2. **Build STAR story #1** — subtasks: choose achievement; structure STAR; save.
|
|
3. **Roleplay recruiter screen** — subtasks: choose scenario; open preview; practice.
|
|
|
|
### Day 4
|
|
1. **Rewrite top resume bullets** — subtasks: select 3 bullets; add metrics; save.
|
|
2. **Practice “why this role”** — subtasks: define motivation; open interview preview; save answer.
|
|
3. **Application shortlist** — subtasks: find 5 roles; rank fit; save top 3.
|
|
|
|
### Day 5
|
|
1. **Mock interview medium round** — subtasks: open preview; complete; review feedback.
|
|
2. **LinkedIn About rewrite** — subtasks: draft summary; add proof; save.
|
|
3. **Q Score check-in** — subtasks: review movement; choose next driver; save.
|
|
|
|
### Day 6
|
|
1. **Tailor resume to one JD** — subtasks: map keywords; rewrite summary; export version.
|
|
2. **Roleplay salary expectation** — subtasks: define range; open preview; practice.
|
|
3. **Draft recruiter outreach** — subtasks: write message; send 2; record.
|
|
|
|
### Day 7
|
|
1. **Week 1 review** — subtasks: review applications; review mock feedback; choose week 2 focus.
|
|
2. **Apply to three roles** — subtasks: tailor resume; apply; record status.
|
|
3. **Publish credibility post** — subtasks: choose work lesson; draft; publish/save.
|
|
|
|
### Day 8
|
|
1. **Interview weakness drill** — subtasks: pick weak answer; open preview; practice.
|
|
2. **Proof bank v1** — subtasks: list wins; tag metrics; connect to questions.
|
|
3. **Profile visibility action** — subtasks: comment on 3 relevant posts; record.
|
|
|
|
### Day 9
|
|
1. **Role transition map** — subtasks: compare current/target; identify gaps; pick one gap.
|
|
2. **Resume gap fix** — subtasks: add missing skill proof; rewrite section; save.
|
|
3. **Roleplay networking call** — subtasks: choose contact; open preview; practice ask.
|
|
|
|
### Day 10
|
|
1. **Mock interview role-related** — subtasks: open preview; complete; review.
|
|
2. **Follow-up sprint** — subtasks: list pending applications; draft follow-ups; send 3.
|
|
3. **Q Score proof update** — subtasks: add resume changes; refresh driver; save.
|
|
|
|
### Day 11
|
|
1. **STAR story #2** — subtasks: choose conflict/teamwork; structure; save.
|
|
2. **Practice weakness answer** — subtasks: draft honest answer; open interview; practice.
|
|
3. **Opportunity shortlist refresh** — subtasks: find 5 roles; rank; save.
|
|
|
|
### Day 12
|
|
1. **Recruiter call roleplay** — subtasks: intro; compensation; next step; practice.
|
|
2. **Resume final role version** — subtasks: edit summary; bullets; export.
|
|
3. **Profile proof link** — subtasks: add project/case link; update featured section; save.
|
|
|
|
### Day 13
|
|
1. **Mock interview feedback loop** — subtasks: review last feedback; pick pattern; practice again.
|
|
2. **Application quality audit** — subtasks: score 5 applications; remove bad-fit roles; save.
|
|
3. **Draft referral ask** — subtasks: pick contact; write ask; send.
|
|
|
|
### Day 14
|
|
1. **Week 2 review** — subtasks: compare callbacks; compare confidence; choose conversion goal.
|
|
2. **Practice behavioral round** — subtasks: open preview; complete; save feedback.
|
|
3. **Publish proof post** — subtasks: pick result; draft; publish/save.
|
|
|
|
### Day 15
|
|
1. **Interview conversion plan** — subtasks: identify weak round; choose practice cadence; save.
|
|
2. **Roleplay offer/salary call** — subtasks: scenario; desired range; practice.
|
|
3. **Update resume with new proof** — subtasks: add story; add metric; save.
|
|
|
|
### Day 16
|
|
1. **Hard question practice** — subtasks: choose 3 hard questions; open preview; practice.
|
|
2. **Recruiter pipeline update** — subtasks: list active leads; next action; send follow-up.
|
|
3. **Q Score review** — subtasks: check lowest driver; route next service; save.
|
|
|
|
### Day 17
|
|
1. **Project deep dive practice** — subtasks: select project; explain decisions; open preview.
|
|
2. **Networking follow-up** — subtasks: follow up 3 contacts; record response.
|
|
3. **Profile credibility pass** — subtasks: headline; About; featured; save.
|
|
|
|
### Day 18
|
|
1. **Application sprint** — subtasks: tailor; apply to 3 roles; record status.
|
|
2. **Roleplay rejection recovery** — subtasks: practice asking feedback; save script.
|
|
3. **STAR story #3** — subtasks: leadership/ownership example; structure; save.
|
|
|
|
### Day 19
|
|
1. **Mock interview full round** — subtasks: open preview; complete; review.
|
|
2. **Resume keyword pass** — subtasks: compare JD; add relevant terms; export.
|
|
3. **Personal brand post** — subtasks: choose insight; draft; publish/save.
|
|
|
|
### Day 20
|
|
1. **Interview answer polish** — subtasks: pick top 3 answers; shorten; practice.
|
|
2. **Roleplay hiring manager call** — subtasks: define scenario; open preview; practice.
|
|
3. **Q Score progress note** — subtasks: compare baseline/current; note drivers; choose final sprint.
|
|
|
|
### Day 21
|
|
1. **Week 3 review** — subtasks: review interviews/callbacks; identify blocker; choose final week push.
|
|
2. **Target company prep** — subtasks: choose company; research; prepare questions.
|
|
3. **Follow-up sprint** — subtasks: pending list; send 3; record.
|
|
|
|
### Day 22
|
|
1. **Mock interview target company** — subtasks: role; company context; open preview.
|
|
2. **Referral request roleplay** — subtasks: pick contact; practice ask; send.
|
|
3. **Resume final polish** — subtasks: grammar; formatting; export.
|
|
|
|
### Day 23
|
|
1. **Salary negotiation prep** — subtasks: define range; roleplay; save script.
|
|
2. **Portfolio/case proof** — subtasks: choose project; write case summary; save.
|
|
3. **Q Score readiness check** — subtasks: review score; choose final gap; act.
|
|
|
|
### Day 24
|
|
1. **Mock interview hard mode** — subtasks: open preview; complete; review.
|
|
2. **LinkedIn recruiter visibility** — subtasks: update headline; comment on posts; send 2 messages.
|
|
3. **Application conversion audit** — subtasks: analyze stages; identify drop-off; plan fix.
|
|
|
|
### Day 25
|
|
1. **Offer call roleplay** — subtasks: scenario; compensation; closing ask; practice.
|
|
2. **Interview replay on weakest area** — subtasks: open preview; practice; compare feedback.
|
|
3. **Proof bank final pass** — subtasks: tag stories; add metrics; save.
|
|
|
|
### Day 26
|
|
1. **Final application sprint** — subtasks: apply to 3 high-fit roles; record; follow up.
|
|
2. **Manager/recruiter communication drill** — subtasks: choose scenario; roleplay; save.
|
|
3. **Profile proof publish** — subtasks: draft post; publish/save; record.
|
|
|
|
### Day 27
|
|
1. **Interview questions to ask** — subtasks: draft 5 smart questions; tailor; save.
|
|
2. **Resume export versions** — subtasks: create 2 role versions; export; save.
|
|
3. **Q Score final push** — subtasks: pick one driver; complete linked task; save.
|
|
|
|
### Day 28
|
|
1. **Readiness review** — subtasks: compare baseline; review artifacts; identify next sprint.
|
|
2. **Mock interview final** — subtasks: open preview; complete; save feedback.
|
|
3. **Networking cadence plan** — subtasks: choose contacts; schedule weekly outreach; save.
|
|
|
|
### Day 29
|
|
1. **Negotiation or recruiter screen replay** — subtasks: open roleplay; practice; save script.
|
|
2. **Opportunity pipeline review** — subtasks: active roles; next actions; deadlines.
|
|
3. **Profile final polish** — subtasks: headline; About; resume link; save.
|
|
|
|
### Day 30
|
|
1. **30-day outcome review** — subtasks: callbacks/interviews/score; record wins; choose next sprint.
|
|
2. **Select next plan** — subtasks: interview conversion, salary negotiation, transition, leadership; save.
|
|
3. **Claim streak milestone** — subtasks: review progress; claim reward; schedule next cadence.
|
|
|
|
## 14.4 Freelancer / gig worker: Client Pipeline Sprint
|
|
|
|
Onboarding pattern: `gig + starting/fewclients/sidehustle + clients/pricing/standout/trust/income + firstclient/doubleincome/fulltime/1lakh`.
|
|
|
|
### Day 1
|
|
1. **Define your client niche** — subtasks: choose target client; define pain; save niche.
|
|
2. **Start credibility/Q Score baseline** — subtasks: review baseline; pick trust driver; save focus.
|
|
3. **Import portfolio/profile** — subtasks: add LinkedIn/portfolio/GitHub; mark missing proof.
|
|
|
|
### Day 2
|
|
1. **Package your core offer** — subtasks: define problem; define deliverable; write offer line.
|
|
2. **Practice discovery call preview** — subtasks: choose client scenario; open roleplay preview; practice.
|
|
3. **Draft profile headline** — subtasks: client type; outcome; save headline.
|
|
|
|
### Day 3
|
|
1. **Build case study #1** — subtasks: pick project; before/action/after; draft summary.
|
|
2. **Pricing confidence roleplay** — subtasks: current/target rate; open preview; practice.
|
|
3. **Draft inbound post** — subtasks: pick client pain; write insight; save/publish.
|
|
|
|
### Day 4
|
|
1. **Client pipeline map** — subtasks: list lead sources; rank channels; choose first 2.
|
|
2. **Offer page/profile polish** — subtasks: add offer; add proof; add CTA.
|
|
3. **Roleplay objection handling** — subtasks: pick objection; open preview; practice.
|
|
|
|
### Day 5
|
|
1. **Outreach message v1** — subtasks: define audience; write message; send 5.
|
|
2. **Q Score trust check** — subtasks: review credibility gaps; choose proof task; save.
|
|
3. **Portfolio proof pass** — subtasks: add metric/testimonial; improve case study; save.
|
|
|
|
### Day 6
|
|
1. **Discovery call script** — subtasks: write 5 questions; roleplay call; save script.
|
|
2. **Pricing page draft** — subtasks: define package tiers; add outcomes; save.
|
|
3. **Publish credibility post** — subtasks: finalize post; publish; record.
|
|
|
|
### Day 7
|
|
1. **Week 1 pipeline review** — subtasks: leads sent; replies; learnings; choose week 2 focus.
|
|
2. **Follow-up roleplay** — subtasks: practice polite follow-up; send 3.
|
|
3. **Update service profile** — subtasks: headline; offer; proof; save.
|
|
|
|
### Day 8
|
|
1. **Create lead list** — subtasks: find 20 prospects; score fit; save top 10.
|
|
2. **Roleplay first client call** — subtasks: scenario; desired close; practice.
|
|
3. **Case study polish** — subtasks: add visuals/link; add outcome; publish/save.
|
|
|
|
### Day 9
|
|
1. **Improve offer specificity** — subtasks: narrow audience; narrow outcome; update copy.
|
|
2. **Pricing objection drill** — subtasks: choose objection; roleplay; save response.
|
|
3. **Draft cold DM/email** — subtasks: write version; personalize 5; send.
|
|
|
|
### Day 10
|
|
1. **Q Score credibility update** — subtasks: add case proof; review movement; pick next gap.
|
|
2. **Client discovery replay** — subtasks: open roleplay; practice; save feedback.
|
|
3. **Inbound content draft** — subtasks: client pain; teaching point; CTA.
|
|
|
|
### Day 11
|
|
1. **Referral ask script** — subtasks: pick past client/contact; write ask; roleplay.
|
|
2. **Portfolio homepage audit** — subtasks: identify weak section; rewrite; save.
|
|
3. **Pipeline follow-up sprint** — subtasks: follow up 5 leads; record status.
|
|
|
|
### Day 12
|
|
1. **Proposal structure** — subtasks: define problem; solution; timeline; price.
|
|
2. **Roleplay proposal call** — subtasks: client scenario; open preview; practice.
|
|
3. **Proof post** — subtasks: share case insight; publish/save; record.
|
|
|
|
### Day 13
|
|
1. **Rate increase plan** — subtasks: current rate; target; justification proof.
|
|
2. **Pricing roleplay hard mode** — subtasks: discount objection; scope objection; practice.
|
|
3. **Lead source review** — subtasks: compare channels; double down; save.
|
|
|
|
### Day 14
|
|
1. **Week 2 review** — subtasks: leads/replies/calls; bottleneck; week 3 focus.
|
|
2. **Update profile CTA** — subtasks: write clear CTA; add booking/contact; save.
|
|
3. **Discovery call practice** — subtasks: open roleplay; practice; save.
|
|
|
|
### Day 15
|
|
1. **Client conversion plan** — subtasks: identify active leads; next action; deadlines.
|
|
2. **Scope creep roleplay** — subtasks: define scenario; practice boundary; save script.
|
|
3. **Case study #2** — subtasks: choose project; draft; save.
|
|
|
|
### Day 16
|
|
1. **Proposal follow-up script** — subtasks: draft; roleplay; send.
|
|
2. **Q Score trust review** — subtasks: review proof/social; choose next improvement.
|
|
3. **Authority post** — subtasks: client lesson; draft; publish/save.
|
|
|
|
### Day 17
|
|
1. **Package refinement** — subtasks: define starter package; define premium package; save.
|
|
2. **Roleplay premium offer** — subtasks: practice quote; handle pushback; save.
|
|
3. **Outreach sprint** — subtasks: send 5 targeted messages; record.
|
|
|
|
### Day 18
|
|
1. **Testimonial request** — subtasks: choose client; draft request; send.
|
|
2. **Client call replay** — subtasks: practice discovery/proposal; save feedback.
|
|
3. **Portfolio proof update** — subtasks: add testimonial/result; save.
|
|
|
|
### Day 19
|
|
1. **Inbound post #2** — subtasks: pick recurring client pain; draft; publish.
|
|
2. **Roleplay difficult client** — subtasks: late payment/scope; practice; save.
|
|
3. **Pipeline health check** — subtasks: leads/calls/proposals; next actions.
|
|
|
|
### Day 20
|
|
1. **Pricing confidence review** — subtasks: compare day 3/day 20; update script; save.
|
|
2. **Proposal template final** — subtasks: refine sections; add pricing; save.
|
|
3. **Q Score progress note** — subtasks: compare baseline; choose final sprint focus.
|
|
|
|
### Day 21
|
|
1. **Week 3 review** — subtasks: identify conversion bottleneck; choose final week push.
|
|
2. **Roleplay close call** — subtasks: practice close; handle hesitation; save.
|
|
3. **Lead list refresh** — subtasks: add 20 leads; score; save.
|
|
|
|
### Day 22
|
|
1. **Full-time freelancing plan** — subtasks: income target; client count; package math.
|
|
2. **Pricing/retainer roleplay** — subtasks: monthly retainer scenario; practice.
|
|
3. **Profile final proof pass** — subtasks: headline; case studies; CTA.
|
|
|
|
### Day 23
|
|
1. **Outreach sprint** — subtasks: personalize 10; send; record.
|
|
2. **Discovery call final practice** — subtasks: open roleplay; practice; save.
|
|
3. **Publish case study** — subtasks: finalize; publish; share.
|
|
|
|
### Day 24
|
|
1. **Referral engine setup** — subtasks: write referral ask; identify 10 contacts; send 3.
|
|
2. **Difficult negotiation roleplay** — subtasks: discount/scope; practice; save.
|
|
3. **Q Score credibility check** — subtasks: review; choose last improvement; act.
|
|
|
|
### Day 25
|
|
1. **Proposal follow-up sprint** — subtasks: list proposals; write follow-ups; send.
|
|
2. **Premium positioning update** — subtasks: rewrite offer; add proof; save.
|
|
3. **Authority post** — subtasks: client insight; draft; publish.
|
|
|
|
### Day 26
|
|
1. **Client onboarding script** — subtasks: define first call; roleplay; save.
|
|
2. **Portfolio final export/share** — subtasks: update links; test CTA; save.
|
|
3. **Pipeline next actions** — subtasks: assign next step to every lead; record.
|
|
|
|
### Day 27
|
|
1. **Close-call practice** — subtasks: open roleplay; practice; save script.
|
|
2. **Retainer offer draft** — subtasks: define recurring value; price; terms.
|
|
3. **Follow-up 5 leads** — subtasks: draft; send; record.
|
|
|
|
### Day 28
|
|
1. **30-day pipeline review prep** — subtasks: leads/replies/calls/revenue; summarize.
|
|
2. **Case study final polish** — subtasks: add outcome; share; save.
|
|
3. **Q Score final review** — subtasks: compare baseline; note trust gains; choose next sprint.
|
|
|
|
### Day 29
|
|
1. **Roleplay highest-value call** — subtasks: choose active lead; practice; save.
|
|
2. **Recurring income plan** — subtasks: define retainer target; prospect list; next actions.
|
|
3. **Publish progress post** — subtasks: write learning; publish; record.
|
|
|
|
### Day 30
|
|
1. **Client Pipeline outcome review** — subtasks: count leads/replies/calls; record wins; choose next plan.
|
|
2. **Select next sprint** — subtasks: first client, premium rates, retainer, inbound brand; save.
|
|
3. **Claim streak milestone** — subtasks: claim reward; set next cadence; start next stage.
|
|
|
|
## 14.5 Founder / solopreneur: Founder Visibility & Validation Sprint
|
|
|
|
Onboarding pattern: `founder + idea/MVP/traction/pre-revenue + customers/funding/visibility/team/model + 90-day priority`.
|
|
|
|
### Day 1
|
|
1. **Clarify 90-day founder priority** — subtasks: choose MVP/customers/raise/hire/presence; save goal.
|
|
2. **Founder Q Score baseline** — subtasks: review credibility drivers; pick weakest; save focus.
|
|
3. **Import founder proof** — subtasks: add LinkedIn/site/deck; mark missing proof.
|
|
|
|
### Day 2
|
|
1. **Write founder one-liner** — subtasks: audience; problem; solution; save.
|
|
2. **Practice customer discovery preview** — subtasks: choose segment; assumption; open roleplay.
|
|
3. **Draft founder profile headline** — subtasks: role; venture; outcome; save.
|
|
|
|
### Day 3
|
|
1. **Map riskiest assumption** — subtasks: identify assumption; define evidence needed; save.
|
|
2. **Build-in-public post v1** — subtasks: pick learning; draft; publish/save.
|
|
3. **Customer list v1** — subtasks: define ICP; list 20 prospects; score top 10.
|
|
|
|
### Day 4
|
|
1. **Discovery call script** — subtasks: write 5 questions; avoid leading; save.
|
|
2. **Roleplay customer interview** — subtasks: open preview; practice; save feedback.
|
|
3. **Founder credibility audit** — subtasks: review profile/site/deck; save top fixes.
|
|
|
|
### Day 5
|
|
1. **Q Score validation check** — subtasks: review credibility/clarity; choose next action.
|
|
2. **Outreach message to customers** — subtasks: write message; send 5; record.
|
|
3. **Founder one-liner revision** — subtasks: simplify; add pain; save.
|
|
|
|
### Day 6
|
|
1. **Investor/customer narrative draft** — subtasks: problem; insight; traction/proof; save.
|
|
2. **Roleplay objection handling** — subtasks: choose customer objection; practice; save.
|
|
3. **Publish market insight** — subtasks: draft; publish; record.
|
|
|
|
### Day 7
|
|
1. **Week 1 validation review** — subtasks: calls booked; replies; learning; choose week 2 focus.
|
|
2. **Discovery follow-up** — subtasks: write follow-up; send; record.
|
|
3. **Update founder profile** — subtasks: headline; one-liner; venture link; save.
|
|
|
|
### Day 8
|
|
1. **Customer discovery round 2** — subtasks: refine ICP; send 5 more; record.
|
|
2. **Roleplay investor intro** — subtasks: stage; proof; open preview; practice.
|
|
3. **Deck/site clarity pass** — subtasks: rewrite problem; rewrite audience; save.
|
|
|
|
### Day 9
|
|
1. **Validate pricing hypothesis** — subtasks: define price; buyer; test question.
|
|
2. **Pricing conversation roleplay** — subtasks: open preview; practice; save.
|
|
3. **Founder update post** — subtasks: share learning; draft; publish.
|
|
|
|
### Day 10
|
|
1. **Q Score credibility update** — subtasks: add profile/deck changes; review movement.
|
|
2. **Customer call replay** — subtasks: practice weak question; save feedback.
|
|
3. **Prospect pipeline update** — subtasks: statuses; next actions; save.
|
|
|
|
### Day 11
|
|
1. **MVP scope check** — subtasks: list features; mark must-have; cut one feature.
|
|
2. **Roleplay cofounder alignment** — subtasks: define role; open preview; practice.
|
|
3. **Authority post** — subtasks: pick contrarian insight; draft; publish.
|
|
|
|
### Day 12
|
|
1. **First customer offer** — subtasks: define pilot; outcome; price/free terms.
|
|
2. **Roleplay sales discovery** — subtasks: buyer; desired next step; practice.
|
|
3. **Profile proof update** — subtasks: add traction/learning; save.
|
|
|
|
### Day 13
|
|
1. **Investor intro email** — subtasks: draft concise note; add proof; save/send.
|
|
2. **Roleplay investor objections** — subtasks: market/team/traction objection; practice.
|
|
3. **Customer insight synthesis** — subtasks: summarize calls; identify pattern; save.
|
|
|
|
### Day 14
|
|
1. **Week 2 review** — subtasks: calls/learnings/proof; choose week 3 conversion goal.
|
|
2. **Build-in-public post #2** — subtasks: learning; metric; ask; publish.
|
|
3. **Q Score check-in** — subtasks: review clarity/visibility; choose next action.
|
|
|
|
### Day 15
|
|
1. **Customer conversion plan** — subtasks: active prospects; next ask; deadlines.
|
|
2. **Roleplay pilot close** — subtasks: offer; objection; next step; practice.
|
|
3. **Deck one-liner polish** — subtasks: problem; solution; why now; save.
|
|
|
|
### Day 16
|
|
1. **Hiring/collaborator need** — subtasks: define role; outcomes; score must-haves.
|
|
2. **Interview first hire preview** — subtasks: role; round; open interview preview.
|
|
3. **Founder profile social proof** — subtasks: add customers/advisors/proof; save.
|
|
|
|
### Day 17
|
|
1. **Customer discovery sprint** — subtasks: send 10 messages; record replies; schedule calls.
|
|
2. **Roleplay hard customer call** — subtasks: skeptical buyer; practice; save.
|
|
3. **Market narrative post** — subtasks: write insight; publish; record.
|
|
|
|
### Day 18
|
|
1. **Fundraising readiness check** — subtasks: stage; proof; gaps; choose fix.
|
|
2. **Investor roleplay replay** — subtasks: open preview; practice; save.
|
|
3. **Website/deck proof pass** — subtasks: add traction/quotes; save.
|
|
|
|
### Day 19
|
|
1. **Model validation task** — subtasks: unit assumption; test method; evidence target.
|
|
2. **Pricing/buyer roleplay** — subtasks: open preview; practice; save.
|
|
3. **Pipeline follow-up** — subtasks: follow up 5 prospects; record.
|
|
|
|
### Day 20
|
|
1. **Q Score progress note** — subtasks: compare baseline; identify strongest/weakest driver.
|
|
2. **Founder pitch practice** — subtasks: 60-sec pitch; roleplay; save script.
|
|
3. **Build-in-public post #3** — subtasks: progress; challenge; ask; publish.
|
|
|
|
### Day 21
|
|
1. **Week 3 review** — subtasks: validation evidence; customer pipeline; choose final week push.
|
|
2. **Pilot proposal draft** — subtasks: scope; timeline; price; success metric.
|
|
3. **Roleplay closing conversation** — subtasks: customer; next step; practice.
|
|
|
|
### Day 22
|
|
1. **Investor/customer FAQ** — subtasks: list hard questions; draft answers; save.
|
|
2. **Interview/collaborator preview** — subtasks: role; criteria; open preview.
|
|
3. **Founder profile polish** — subtasks: headline; one-liner; proof; save.
|
|
|
|
### Day 23
|
|
1. **Customer outreach sprint** — subtasks: send 10; record; schedule.
|
|
2. **Roleplay objection: no budget** — subtasks: practice; save response.
|
|
3. **Authority post** — subtasks: market lesson; draft; publish.
|
|
|
|
### Day 24
|
|
1. **Traction proof package** — subtasks: collect calls/replies/users/revenue; summarize.
|
|
2. **Investor intro replay** — subtasks: open roleplay; practice; save.
|
|
3. **Q Score final gap action** — subtasks: choose gap; complete linked task; save.
|
|
|
|
### Day 25
|
|
1. **Pilot close sprint** — subtasks: active prospects; send close asks; record.
|
|
2. **Founder pitch final** — subtasks: tighten 60-sec pitch; practice; save.
|
|
3. **Deck/site final clarity** — subtasks: problem; solution; proof; CTA.
|
|
|
|
### Day 26
|
|
1. **Hiring/collaborator outreach** — subtasks: define target; write message; send 5.
|
|
2. **Roleplay cofounder conversation** — subtasks: equity/scope/values; practice.
|
|
3. **Publish milestone update** — subtasks: metric/learning; publish; record.
|
|
|
|
### Day 27
|
|
1. **Customer interview synthesis** — subtasks: summarize patterns; decide pivot/persevere; save.
|
|
2. **Roleplay next-step close** — subtasks: pilot/customer/investor; practice.
|
|
3. **Founder credibility final pass** — subtasks: profile; site; proof links; save.
|
|
|
|
### Day 28
|
|
1. **30-day validation review prep** — subtasks: evidence; gaps; decision; next sprint.
|
|
2. **Q Score closeout** — subtasks: compare baseline; note drivers; choose next.
|
|
3. **Build-in-public recap** — subtasks: draft progress recap; publish/save.
|
|
|
|
### Day 29
|
|
1. **Highest-stakes conversation practice** — subtasks: investor/customer/hire; open roleplay; practice.
|
|
2. **Pipeline next actions** — subtasks: every prospect next step; deadlines; save.
|
|
3. **Pitch/deck export** — subtasks: final file/link; save; share-ready.
|
|
|
|
### Day 30
|
|
1. **Founder sprint outcome review** — subtasks: calls, customers, proof, score; record.
|
|
2. **Choose next founder sprint** — subtasks: MVP, customers, fundraising, hiring, visibility; save.
|
|
3. **Claim streak milestone** — subtasks: claim reward; schedule next cadence; start next stage.
|