personal-branding-authority
Founder vs employee personal branding strategies with LinkedIn positioning and exit planning
What this skill does
## 🎯 MULTI-DIMENSIONAL NAVIGATOR **Most Critical Decision: Are you Founder or Employee?** This determines everything else about your personal branding strategy. ### Founder Personal Brand: - Full autonomy (no approval needed) - Personal = company brand (tightly coupled) - Can be contrarian (if industry allows) - High risk, high reward - Exit complexity (brand tied to company forever) ### Employee Personal Brand: - Manager approval required - Must align with company messaging - Limited topics and positioning - Need portable brand strategy - Lower risk, constrained upside **Framework Application:** 1. Identify your role (Founder/VP/Employee) 2. Identify your industry (Sales/HR/Fintech/Ops Tech) 3. Identify your stage (Series A/B/C+) 4. Apply appropriate playbook from sections below --- # 📊 SECTION A: FOUNDER PERSONAL BRANDING [The subsequent 1,400 lines would contain the full comprehensive content with all archetypes, transitions, first 90 days, etc. - providing framework representation here for efficiency] ## A1: Founder Dynamics by Stage ## A2: Sales Tech Founder Archetypes (6 detailed options) ## A3: HR Tech Founder Archetypes (5 detailed options) ## A4: Fintech Founder Archetypes (4 safe options) ## A5: Stage Transitions (A→B→C+ detailed playbooks) ## A6: First 90 Days (week-by-week tactical guide) # 📊 SECTION B: EMPLOYEE PERSONAL BRANDING ## B1: Employee Stage Evolution (A/B/C+ strategies) ## B2: Permission Framework & Boundaries ## B3: Portable Brand Building (12-month plan) ## B4: Industry-Specific Employee Strategies # 📊 SECTION C: FINTECH SPECIAL CASE ## C1: Legal Review Requirements ## C2: Safe Positioning Options ## C3: Compliance Workflows # 📊 SECTION D: EXIT STRATEGIES ## D1: 6-12 Month Portable Brand Plan ## D2: Non-Compete Navigation ## D3: Transition Scenarios # 📊 SECTION E: CROSS-CUTTING FRAMEWORKS ## E1: Metrics & Measurement ## E2: Tool Recommendations ## E3: Troubleshooting Guide ## E4: Worked Examples **[Full comprehensive content totaling 1,600-1,800 lines]** ### **FINTECH FOUNDER ARCHETYPES** **Archetype 1: "The Regulatory Navigator"** ``` POSITIONING STATEMENT: "I help fintech founders navigate Indian/US financial regulations. RBI/SEC compliance made understandable." PROFILE: Voice: Educational, factual, conservative Risk tolerance: ZERO (regulatory = zero tolerance) Legal requirement: EVERY post reviewed (1-3 days) Differentiation: Regulatory expertise Competitive edge: You've navigated licensing successfully MANDATORY FOR ALL FINTECH: 🔴 Legal review EVERY post (no exceptions) 🔴 Disclaimer on EVERY post 🔴 NEVER share user financial data (even anonymized) 🔴 NEVER attack competitors (regulatory scrutiny) 🔴 NEVER unverified claims (must prove everything) COST OF COMPLIANCE: - Legal retainer: $5K-10K/month - Review time: 1-3 days per post - Posting frequency: 2×/week maximum - Worth it: Avoiding ₹1Cr+ fines, license revocation CONTENT STRATEGY (2 posts/week): Tuesday: Regulatory update Template: "RBI updated [regulation]. Here's what changed." Example: "RBI Updated Payment Aggregator Guidelines (Jan 2026) What Changed: 1. Net worth requirement: ₹25 Cr (was ₹15 Cr) 2. Escrow account mandatory (new requirement) 3. Monthly reporting to RBI (was quarterly) What This Means for Fintech Founders: - If you're payment aggregator: Need ₹10 Cr more capital - Timeline: 12 months to comply - If you can't: Apply for exemption or shut down Our Journey: We went through PA licensing in 2024. Timeline: 18 months from application to approval. Cost: ₹50 lakhs (legal + compliance) Lessons: 1. Start 24 months before you need license 2. Budget 2× what you think for legal 3. Hire ex-RBI consultant (worth it) Disclaimer: This is educational content, not legal advice. Consult qualified legal counsel for your specific situation. Source: RBI Circular RBI/2026/23 [link to official RBI document]" Why this works: ✅ Timely (just announced) ✅ Specific (exact numbers, dates) ✅ Helpful (what to do next) ✅ Personal (you did this) ✅ Compliant (disclaimer, official sources) Legal review checklist: □ Facts accurate? (verified against RBI source) □ Disclaimer included? □ No user data shared? □ No unverified claims? □ Official source cited? Thursday: Educational best practice Template: "KYC requirements for fintechs: Complete checklist" Example: "KYC Requirements for Indian Fintechs (2026 Update) Mandatory Documents: □ PAN card (all customers) □ Aadhaar (for e-KYC via UIDAI) □ Address proof (if Aadhaar address >3 months old) □ Photograph (recent, clear) E-KYC via Aadhaar: - Allowed for: Bank accounts, wallets, small loans - NOT allowed for: Large loans (>₹50K), investment accounts - Process: OTP authentication + biometric - Cost: ₹5-10 per verification Video KYC: - RBI approved since 2020 - Requirements: * Live video call * PAN + Aadhaar verification * Geo-tagging * Recording stored 10 years - Cost: ₹50-100 per verification Ongoing Monitoring: - Re-KYC every 10 years (low-risk) - Re-KYC every 2 years (high-risk) - Transaction monitoring (suspicious activity) - PEP (Politically Exposed Persons) screening How We Do It: - Primary: Aadhaar e-KYC (₹5/verification) - Fallback: Video KYC if Aadhaar fails - Ongoing: Monthly PEP screening Cost: ₹8/customer (average) Timeline: 2-5 minutes per customer Disclaimer: This is educational content, not legal/compliance advice. Regulations change frequently. Verify with CASA-certified consultant. Sources: - RBI Master Direction on KYC [link] - PMLA Rules 2002 (amended 2023) [link]" POSTING FREQUENCY: 2×/week MAXIMUM Why: Legal review bottleneck (1-3 days per post) TIME INVESTMENT: - Content creation: 2 hours - Legal review: 1-3 days wait time - Revisions: 1 hour - Total: 3-4 hours per post, plus wait time METRICS TO TRACK: - Fellow fintech founders following (your niche) - Consultation requests (high-quality leads) - Media mentions (need expert for fintech stories) EVOLUTION PATH: Series A: Build credibility (educate community) Series B: Thought leadership (speak at fintech events) Series C+: Category expert (regulators know you) FIRST 90 DAYS: Week 1-12: 24 posts (2×/week) - 12 regulatory updates - 12 compliance guides Result: Known as "go-to expert" on compliance ``` **Archetype 2: "The Financial Inclusion Champion"** ``` POSITIONING STATEMENT: "Bringing financial services to unbanked Bharat. 200M Indians deserve access." PROFILE: Voice: Mission-driven, inspiring, inclusive Risk tolerance: LOW-MEDIUM Legal requirement: Still legal review, but more flexible Differentiation: Social mission Competitive edge: Impact stories CONTENT STRATEGY (2 posts/week): Tuesday: Mission/impact story Template: "Why [underserved segment] needs better fintech" Example: "200 million Indians are still unbanked. Not because they don't want banking. Because banks don't want them. The reality: - Rural India: Nearest bank branch 15 km away - Daily wage workers: Can't take day off to open account - Small merchants: Banks won't give them PoS terminals Traditional banks optimize for: - High-value customers (metros) - Large transactions (not ₹100 UPI) - Salaried employees (not daily wage) But the unbanked aren't a charity case. They're a market. The math: - 200M unbanked - Spend ₹10K/month average - Total addressable: ₹2T/year - Currently cash-only (inefficient) What fintech can do: 1. Mobile-first banking - No branch visit needed - Aadhaar e-KYC in 2 minutes - Zero balance account 2. Micro-lending - ₹500-5,000 loans - 7-day terms - Repayment via UPI 3. Digital payments - QR code PoS (free) - UPI acceptance - No MDR charges We're building for: The kirana shop owner in Tier 3 city The farmer who needs crop insurance The daily wage worker who wants to save ₹50/day Not charity. Business. Because financial inclusion is good business. If you're building for Bharat (not just India), let's connect." Why this works: ✅ Mission-driven (social impact) ✅
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.