@nerdev/skillset 0.2.1

package/skills/business/freelancing/SKILL.md

@@ -0,0 +1,679 @@
+---
+name: freelancing
+description: "Complete studio/freelance playbook for developers. Use this skill whenever the user mentions: freelancing, studio pitch, client proposals, quotations, invoices, contracts, SRS, pricing, rates, Upwork, Fiverr, finding clients, portfolio, project scoping, estimates, client communication, onboarding, deliverables, scope creep, payment follow-up, agency vs individual positioning, or any aspect of running a freelance dev studio. Covers everything from first contact to final payment and testimonials."
+---
+
+# Freelance Studio Playbook
+### For developers operating as a small studio / collective
+
+
+# CORE PHILOSOPHY
+
+You are not a developer for hire. You are a problem-solving studio that happens to write code.
+
+• Sell outcomes, not hours  
+• Document everything: scope, deliverables, timelines, payments  
+• Under-promise, over-deliver  
+• Start as individuals, present as a team  
+
+
+# 0.5. CRITICAL MISTAKES TO AVOID
+
+Lessons learned the hard way:
+
+1. **Never rely on platforms for payments** (Deel, Contra, Upwork escrow)
+   - They take cuts, hold money, create friction
+   - Use direct payments: Wise, UPI, bank transfer
+
+2. **Always take advance payments**
+   - 20% upfront before starting
+   - 50% at 70% completion
+   - Remaining 30% before final delivery
+   - Never work on "pay after" terms
+
+3. **Limit iterations in contract**
+   - Max 4 iterations per feature
+   - Once scope is locked, no free changes
+   - Additional iterations billed at hourly rate
+   - Put this in writing before starting
+
+4. **Communicate daily, no exceptions**
+   - Send 3-4 bullet update every day
+   - Share progress OR explain delays
+   - Silence = client assumes you ghosted
+   - Use async format: DONE / IN PROGRESS / NEXT / BLOCKERS
+
+
+# 0. POSITIONING -- Agency vs Individual vs Studio
+
+### The Right Answer: "Small Studio"
+
+Do not say: "I'm a freelancer"  
+Do not say: "We're an agency"  
+Do say: "We're a small product studio" or "We're a boutique dev team"
+
+Benefits:
+
+• Trust of a team  
+• Agility of freelancers  
+• Premium feel without large-agency pricing  
+
+
+# 1. FINDING AND EVALUATING CLIENTS
+
+## Platform Strategy
+
+### Upwork
+• Complete profile fully  
+• Start with small jobs ($200 to $500) for reviews  
+• Apply selectively  
+• Conversion improves after 5+ reviews  
+
+### Fiverr
+• Create specific gigs
+• Offer upsells
+• Fast delivery builds traction
+
+### Direct Outreach
+LinkedIn founders, startups via Crunchbase, YC directory.
+
+### Referrals
+Offer 5-10% referral fee.
+
+
+## Red Flags
+
+🚩 Pay after funding  
+🚩 Vague scope + urgent deadline  
+🚩 Free test work beyond 30 min  
+🚩 Refuses contract  
+🚩 Constant scope changes early  
+🚩 Wants payment via platform (Deel/Contra) -- use direct payments (Wise, UPI, bank transfer)  
+
+
+## Green Flags
+
+✅ Clear requirements  
+✅ Budget mentioned  
+✅ Responsive communication  
+✅ Prior experience hiring developers  
+✅ Accepts scoping call  
+
+
+# 2. PROPOSAL SYSTEM
+
+## 3-Paragraph Proposal Structure
+
+Paragraph 1:
+Mirror their problem.
+
+Paragraph 2:
+Explain approach and proof.
+
+Paragraph 3:
+Timeline + investment + CTA.
+
+
+## Proposal Personalization Rule
+
+Always include 1 line:
+
+"I noticed you are currently using ___"
+
+Shows real attention.
+
+
+# 3. QUOTATION vs INVOICE FLOW
+
+Quotation = offer document before work  
+Invoice = payment request after approval  
+
+Flow:
+
+Client inquiry  
+↓  
+Discovery call  
+↓  
+Quotation sent  
+↓  
+Contract signed  
+↓  
+Invoice 20% upfront  
+↓  
+Work starts  
+↓  
+Invoice 50% at 70% completion  
+↓  
+Final invoice (remaining 30%)  
+↓  
+Testimonial  
+
+Payment rule: Never start work without upfront payment. Hold final code until full payment clears.
+
+
+# 4. CONTRACT SYSTEM
+
+Never start without:
+
+• signed agreement  
+• upfront payment  
+
+Contract defines:
+
+• scope  
+• timeline  
+• payment structure  
+• IP ownership  
+• change request process  
+• revision limits (max 4 iterations per feature; additional billed at hourly rate)  
+
+
+# 5. PRICING SYSTEM
+
+## Pricing Models
+
+Fixed price (recommended)
+
+Hourly
+
+Retainer
+
+Package pricing
+
+
+## Base Rate Formula
+
+Monthly income target ÷ 80 hrs = hourly floor
+
+Example:
+
+₹1,00,000 target  
+÷ 80 hrs  
+= ₹1,250/hr minimum
+
+
+# 6. CLIENT ONBOARDING FLOW
+
+Step 1 -- discovery call  
+Step 2 -- scope doc  
+Step 3 -- quotation  
+Step 4 -- contract + upfront payment  
+Step 5 -- kickoff  
+
+
+# 7. DELIVERY SYSTEM
+
+Use milestones.
+
+Example 4-week build:
+
+Week 1:
+architecture + design
+
+Week 2 to 3:
+core development
+
+Week 4:
+polish + deploy
+
+
+# 8. LATE PAYMENT HANDLING
+
+Day 3:
+friendly reminder
+
+Day 7:
+firm follow-up
+
+Day 14:
+late fee warning
+
+Always:
+
+50% upfront  
+hold final code until payment clears  
+
+
+# 9. PORTFOLIO STRUCTURE
+
+Each project:
+
+problem  
+solution  
+ stack  
+ results  
+
+Focus on outcomes.
+
+
+# 10. TOOLS STACK
+
+Invoices:
+invoicely / Zoho / Wave
+
+Contracts:
+DocuSign / PandaDoc
+
+Payments:
+Wise / UPI / Razorpay
+
+Communication:
+Slack
+
+Async video:
+Loom
+
+Tracking:
+Notion / Linear
+
+Hosting:
+Vercel
+
+Design:
+Figma
+
+
+# 11. GROWTH ROADMAP
+
+Months 1 to 3:
+small projects
+reviews
+portfolio
+
+Months 4 to 6:
+raise rates
+referrals
+direct outreach
+
+Months 7 to 12:
+choose niche
+premium pricing
+
+Year 2:
+productize services
+retain clients
+build SaaS
+
+
+# 12. UPWORK PLAYBOOK
+
+Profile title format:
+
+Role | Tech | Tech | Tech
+
+Example:
+
+Full Stack Engineer | Next.js • Node • PostgreSQL
+
+Proposal formula:
+
+Hook  
+Credibility  
+Approach  
+Proof  
+CTA  
+
+
+# 13. CLIENT COMMUNICATION SCRIPTS
+
+Use structured communication.
+
+Always clarify:
+
+problem  
+expectation  
+timeline  
+
+
+# 14. DISCOVERY QUESTIONS
+
+WHY:
+What problem?
+
+WHO:
+Who are users?
+
+WHAT:
+What outcome defines success?
+
+WHEN:
+Why this timeline?
+
+BUDGET:
+What range?
+
+
+# 15. ADVANCED CONTRACT CLAUSES
+
+Kill fee
+
+Scope change clause
+
+Late payment clause
+
+IP transfer clause
+
+Client feedback SLA
+
+Value pricing clause
+
+
+# 16. PROJECT SCOPING SYSTEM
+
+Scope defines:
+
+deliverables  
+boundaries  
+timeline  
+assumptions  
+
+Bad scope causes:
+
+scope creep  
+delays  
+profit loss  
+
+
+## Feature Scope Template
+
+FEATURE:
+User Authentication
+
+INCLUDED:
+email login
+password reset
+JWT sessions
+
+NOT INCLUDED:
+SSO
+2FA
+enterprise auth
+
+ACCEPTANCE:
+user signup works
+session persists
+logout works
+
+ESTIMATE:
+10 hours
+
+
+# 17. FULL SRS TEMPLATE
+
+Sections:
+
+Introduction
+
+Users
+
+Features
+
+Non-functional requirements
+
+Tech stack
+
+Out of scope
+
+Timeline
+
+Acceptance criteria
+
+Sign-off
+
+
+# 18. MVP PRIORITIZATION FRAMEWORK
+
+ICE score:
+
+priority =
+impact × confidence ÷ effort
+
+Build high score features first.
+
+MVP proves idea works.
+
+Later versions improve scale.
+
+
+# 19. PRICING CALCULATOR STRUCTURE
+
+price =
+hours × rate × complexity × risk × urgency
+
+Complexity multipliers:
+
+CRUD app:
+1.0
+
+dashboard:
+1.2
+
+SaaS MVP:
+1.4
+
+AI integration:
+1.8
+
+unclear scope:
+2.0
+
+
+# 20. CLIENT QUALIFICATION DECISION TREE
+
+clear scope?
+    no → discovery phase
+    yes →
+
+budget realistic?
+    no → decline
+    yes →
+
+communication good?
+    no → decline
+    yes →
+
+accept project
+
+
+# 21. NICHE POSITIONING STRATEGY
+
+Generalists compete on price.
+
+Specialists compete on expertise.
+
+
+Positioning formula:
+
+I help [client]
+build [result]
+using [tech]
+
+Example:
+
+I help SaaS founders build MVPs using Next.js and Supabase.
+
+
+# 22. OUTREACH SCRIPTS
+
+LinkedIn:
+
+mention observation
+offer idea
+ask for call
+
+Cold email:
+
+identify problem
+offer Loom audit
+
+Network:
+
+announce availability
+
+
+# 23. PORTFOLIO STRUCTURE THAT CONVERTS
+
+Homepage:
+
+value proposition
+
+3 projects
+
+process
+
+proof
+
+CTA
+
+
+# 24. PROPOSAL GENERATOR TEMPLATE
+
+Inputs:
+
+client name
+project type
+ features
+ timeline
+ risk
+
+
+Structure:
+
+goal
+
+approach
+
+deliverables
+
+timeline
+
+price
+
+CTA
+
+
+# 25. CLIENT PSYCHOLOGY
+
+Clients evaluate:
+
+risk
+speed
+trust
+clarity
+predictability
+
+Reduce uncertainty.
+
+Increase structure.
+
+
+Key principles:
+
+clarity wins deals
+
+confidence builds trust
+
+structure signals competence
+
+
+# 26. ASYNC COMMUNICATION SYSTEM
+
+Default:
+
+Slack for chat
+
+Loom for demos
+
+Notion for docs
+
+Calendly for calls
+
+
+Async update format (send daily, even if no progress):
+
+DONE
+
+IN PROGRESS
+
+NEXT
+
+BLOCKERS
+
+Daily communication rule:
+- Send update every day by EOD
+- If work is done: share what was completed
+- If work is not done: explain what's taking time
+- Summarize in 3-4 bullet points max
+- Silence = client assumes you ghosted
+
+
+Decision format:
+
+Option A
+
+Option B
+
+Recommendation
+
+Confirm
+
+
+Benefits:
+
+fewer meetings
+
+written record
+
+faster execution
+
+timezone flexibility
+
+higher perceived professionalism
+
+
+# MASTER CHECKLIST
+
+Before accepting:
+
+scope clear
+
+budget realistic
+
+no red flags
+
+skills match
+
+Before starting:
+
+contract signed (with iteration limits)
+
+20% upfront received
+
+resources supplied
+
+milestone defined
+
+Before delivery:
+
+tested
+
+documented
+
+demo ready
+
+invoice ready
+
+After completion:
+
+final payment received
+
+handoff done
+
+testimonial requested
+
+portfolio updated
+
+follow-up scheduled
+
+
+END OF PLAYBOOK