Personal Branding & Authority Building
by @shashwatgtm
Founder vs employee personal branding strategies with LinkedIn positioning and exit planning
clawhub install personal-branding-authorityπ About This Skill
name: personal-branding-authority description: Founder vs employee personal branding strategies with LinkedIn positioning and exit planning metadata: {"clawdbot":{"emoji":"π€","homepage":"https://github.com/shashwatgtm","always":true}}
π― MULTI-DIMENSIONAL NAVIGATOR
Most Critical Decision: Are you Founder or Employee?
This determines everything else about your personal branding strategy.
Founder Personal Brand:
Employee Personal Brand:
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)
β
Business case (not just charity)
β
Specific market (200M unbanked)
β
Concrete solutions (what fintech can do)
β
Still compliant (no financial advice)
Thursday: Product/feature story
Template:
"How we made [feature] accessible for [segment]"
Example:
"How we made digital payments accessible for Tier 3 kirana shops:
The Problem:
Kirana shops: 12 million in India
70% don't accept digital payments
Why? PoS terminals cost βΉ3,000-5,000
Merchants can't afford it What we built:
QR code-based payments (free)
Works with any UPI app
No hardware needed
Merchant gets SMS confirmations Features for low-tech users:
1. Voice SMS confirmations
- Payment received: Automated call in local language
- "Aapko βΉ150 mile, Customer: Rahul"
2. Daily settlement SMS
- Every evening: Total day's collections
- "Aaj βΉ2,450 mile. Kal subah account mein aayega"
3. Vernacular support
- Hindi, Tamil, Telugu, Marathi, Gujarati
- Local language = trust
Results:
50,000 kirana shops onboarded
85% still active after 90 days (retention)
Average βΉ15K/month digital collections
Merchant feedback: "Pehle barabari mehsus karti hai" (Finally feel equal) The Impact:
Not just payments.
Financial inclusion.
Dignity.
[Note: Story anonymized per privacy guidelines]
Disclaimer: This describes our product features, not financial advice.
Product subject to terms & conditions."
LEGAL REVIEW STILL REQUIRED:
Even mission-driven content needs review
Focus on: No financial advice, privacy compliance
METRICS:
Social impact metrics (customers served)
Media coverage (impact stories)
Partnerships (NGOs, government) FIRST 90 DAYS:
Focus on impact stories (not product pitches)
Build brand as mission-driven (authentic)
Partner with social organizations
OPERATIONS TECH FOUNDER ARCHETYPES
Archetype 1: "The India Retail Execution Expert"
POSITIONING STATEMENT:
"I've spent 15 years in CPG distribution in India.
Now helping brands execute in kiranas, mom-and-pop stores."PROFILE:
Voice: Practical, field-tested, India-specific
Risk tolerance: MEDIUM
Audience: Niche (CPG brands, FMCG, distribution)
Differentiation: Deep India retail expertise
Competitive edge: You've been in the field
CONTENT STRATEGY (3 posts/week):
Monday: India retail reality
Template:
"The truth about [India retail challenge]"
Example:
"The truth about kirana distribution in India:
Everyone thinks: Modern trade is the future
Reality: Kiranas = 90% of retail sales
The Numbers:
12 million kirana stores in India
8 million in Tier 2/3/4 cities
70% of FMCG sales
NOT going away Why Kiranas Survive:
1. Location (within 200m of every home)
2. Credit (allow monthly billing for regular customers)
3. Relationships (shopkeeper knows your family)
4. Hours (open 6 AM to 11 PM daily)
Modern trade can't compete on these.
Distribution Challenges:
8 million stores across 28 states
No addresses (literally: "Blue shop near temple")
Cash-only (85% of stores)
Low order values (βΉ500-2,000 per order)
High frequency (daily/weekly restocking) How CPG brands do it:
1. Distributor network
- 5,000-10,000 distributors nationwide
- Each covers 500-1,000 stores
- Manual order taking (sales rep visits)
2. Field force management
- 50,000-100,000 field reps
- Paper-based or basic mobile apps
- Attendance tracking nightmare
3. Merchandising
- Manual shelf checks
- Planogram compliance <30%
- Stock-outs common
We're digitizing this:
Route optimization (field force efficiency +40%)
Digital ordering (order accuracy +60%)
Inventory visibility (stock-outs -35%) But it's hard. Really hard.
Because you're not just building software.
You're changing 50-year-old distribution networks.
If you're building for India retail, DM me.
I've made every mistake already."
Tuesday: Field force best practices
Template:
"How to manage [X] field reps in India"
Example:
"Managing 10,000 field reps across India: Lessons learned
The Challenge:
10,000 reps (our client's)
28 states, 500+ cities
Selling FMCG to kiranas
Attendance fraud: 30% (reps don't actually visit stores) What Doesn't Work:
β GPS tracking only (easy to game: sit outside store, mark attendance)
β Photo proof only (take photo, don't actually sell)
β Honor system (30% fraud)
What Works:
β
Geo-fenced check-in + store receipt photo
- Must be within 50m of store
- Must show today's date on receipt
- Must show products sold
β
Random audits (10% of stores/month)
- Manager calls store: "Did rep visit?"
- Fraud drops to <5% with random audits
β
Performance-based incentives
- Base salary: βΉ15K/month
- Variable: βΉ5-20K (based on sales, not just visits)
- High performers earn 2Γ base
The Tech Stack:
Mobile app (Android, <10MB, works on βΉ5K phones)
Offline-first (data syncs when internet available)
Battery-efficient (field reps can't charge all day)
Vernacular (Hindi, Tamil, Telugu, Marathi) Results:
Attendance fraud: 5% (was 30%)
Sales per rep: +45%
Rep satisfaction: Higher (fair incentives) Key Insight:
You can't just build software for India retail.
You need to understand:
Ground realities (power cuts, no internet)
Human behavior (fraud, shortcuts)
Local context (relationships matter) Tech is 30% of solution.
Understanding India is 70%."
Friday: CPG go-to-market insights
Template:
"How [brand type] should approach India distribution"
Example:
"D2C brands entering kirana distribution: Do's and Don'ts
The Dream:
"We'll bypass distributors and go direct to kiranas!"
The Reality:
You'll fail in 6 months. Here's why.
Why Distributors Exist:
1. Credit (they float 30-60 day terms)
- Kiranas can't pay upfront
- You don't want to float βΉ10 Cr working capital
2. Logistics (they handle last-mile)
- 8 million stores = impossible to reach direct
- Distributor has 50 trucks, 200 delivery boys
3. Relationships (they've been doing this 20 years)
- Kirana trusts distributor
- Won't trust random D2C brand
What D2C Should Do:
1. Partner with distributors (don't fight them)
- Offer better margins than FMCG (25% vs 10%)
- Provide marketing support (posters, samples)
- Make it easy for them to sell you
2. Start in metros (test product-market fit)
- Modern trade first (easier to get distribution)
- Amazon/Flipkart/BigBasket
- Then kiranas (once you have demand)
3. Tier 2/3 expansion (after metro success)
- Distributors will come to YOU
- Because kiranas are asking for your product
- Pull strategy > Push strategy
What Usually Happens:
Month 1: "We'll disrupt distribution!"
Month 6: "Distributors actually know what they're doing"
Month 12: Partner with distributors
Month 24: Actually scaling Save yourself 18 months.
Work with distributors from day 1.
Trust me. I tried the hard way."
METRICS:
CPG brand followers (your ICP)
Consulting inquiries (high-value)
Conference speaking (FMCG, retail events) FIRST 90 DAYS:
Position as "India retail expert"
Share field-tested insights
Build community of CPG brands
A4: Complete First 90 Days Playbook (All Industries)
[Detailed week-by-week already covered in Series A section above]
A5: Channel Strategy & Multi-Platform Management
[Covered in detail in Section A2 examples]
π SECTION B: EMPLOYEE PERSONAL BRANDING
B1: The Employee Dilemma
THE CORE TENSION:What You Want:
β
Build personal brand (future career security)
β
Become known expert in your field
β
Have portable brand if you leave
β
Attract opportunities (jobs, consulting, speaking)
What Your Company Wants:
β οΈ You promote company brand (not personal)
β οΈ You don't share confidential information
β οΈ You don't recruit colleagues to competitors
β οΈ Your brand stays professional (reflects on company)
THE FUNDAMENTAL QUESTION:
"Can I build personal brand without getting fired?"
ANSWER: Yes, but with guardrails.
The key: Build 70% portable (industry insights) + 30% company
B2: Employee Personal Brand Decision Tree
STEP 1: What's Your Role?VP/Director at Series A/B Startup:
β GREEN LIGHT (proceed to strategy)
Manager/IC at Series A/B:
β YELLOW LIGHT (get manager permission first)
Any role at Public Company:
β YELLOW LIGHT (check social media policy)
Any role in Fintech/Healthcare:
β RED LIGHT (legal review required)
Employee at Series C+ with Corp Comms:
β RED LIGHT (limited personal branding)
STEP 2: What's Your Manager's Stance?
Manager says: "Yes! Build your brand!"
β GREEN LIGHT
Manager says: "Sure, just don't share confidential stuff"
β YELLOW LIGHT (get clearer boundaries)
Manager says: "All comms go through Corp Comms"
β RED LIGHT (very limited)
Manager says nothing (you haven't asked):
β STOP. Ask first. (see Section B3)
STEP 3: What's Your Company's Policy?
Written social media policy exists:
β Read it carefully, follow it
No written policy:
β Get explicit permission (see Section B3)
Policy says "all comms through Corp Comms":
β RED LIGHT (build internally only)
DECISION OUTCOMES:
GREEN LIGHT = Build Personal Brand
Post 3-5Γ/week
70% industry, 30% company
Manager supportive
β GO TO: Employee Content Strategy (B4)YELLOW LIGHT = Build Carefully
Post 2-3Γ/week
80% industry, 20% company
Get approval for company content
β GO TO: Approval Workflows (B5)RED LIGHT = Very Limited or Wait
Internal content only (company blog)
Or wait until you leave
Focus on building skills, not brand
β GO TO: Internal Brand Building (B6)
B3: The "Get Permission First" Conversation
THE SCRIPT (With Your Manager):"Hey [Manager name], I'd like to talk about building my personal brand on LinkedIn.
Here's what I'm thinking:
Post industry insights (not company-specific)
Share frameworks I've learned
Maybe occasionally share company wins (with approval) This could help with:
Recruiting (people see us as thought leaders)
Our brand (extends our reach)
My professional development What are the boundaries?
What can I share about our company?
What requires your approval first?
Are there topics I should avoid?" GOOD MANAGER RESPONSES:
"Great idea! Here are the rules:
Don't share revenue, customer names, or roadmap
Run company metrics by me first
Otherwise, go for it"
β This is GREEN LIGHT"I like it. Let's set up monthly check-ins to review your posts."
β This is YELLOW LIGHT (careful but supportive)
NEUTRAL MANAGER RESPONSES:
"I guess that's fine? Just don't share anything confidential."
β YELLOW LIGHT (push for more clarity: "Can you define confidential?")
"Let me check with Corp Comms and get back to you."
β YELLOW LIGHT (they're being cautious, which is fair)
BAD MANAGER RESPONSES:
"Not comfortable. All external comms go through Corp Comms."
β RED LIGHT (don't fight it, build internally)
"Why do you need a personal brand? Focus on your job."
β RED LIGHT (they see this as threat, tread carefully)
WHAT TO DO WITH EACH:
GREEN LIGHT:
β
Start building immediately
β
Monthly check-ins with manager
β
Self-police boundaries
YELLOW LIGHT:
β οΈ Get WRITTEN guidelines (email summary of conversation)
β οΈ Start slow (1-2 posts/week, gauge reaction)
β οΈ Over-communicate (share drafts proactively)
RED LIGHT:
π΄ Don't fight it (you'll lose)
π΄ Build internally (company blog, Slack, all-hands)
π΄ Plan to build externally AFTER you leave
B4: Employee Content Strategy (70/20/10 Rule)
THE MAGIC FORMULA:70% Industry Insights (Portable)
Trends, research, best practices
Tool reviews, comparisons
Conference learnings
NOT company-specific
β This builds YOUR brand (goes with you when you leave)20% Frameworks (Helpful)
"My [X] template"
"How I think about [Y]"
General methodologies
NOT proprietary company IP
β This builds credibility10% Company (With Approval)
Announcements (hiring, funding)
Customer wins (with permission)
Team culture
β This supports companyWHY 70/20/10:
You WILL leave eventually:
Average tenure: 2-3 years
If 90% of your content is company-specific
You leave with NO personal brand
All that work benefits company, not you Your brand should be PORTABLE:
Industry insights = valuable anywhere
Company content = only valuable while you're there
Build for: Your next role, not just current role EXAMPLES BY CONTENT TYPE:
β
70% Industry Insights (GOOD):
"The state of product-led growth in 2026:
I analyzed 50 PLG companies' public metrics.
Here's what's working:
1. Free trial β Freemium shift
- 60% of PLG companies now offer freemium
- Why: Higher activation, more word-of-mouth
2. Time-to-value acceleration
- Top PLG: <5 minutes to "aha moment"
- Average: 30-60 minutes
- Gap = churn predictor
3. In-product education
- Interactive guides > video tutorials
- Contextual help > help center
- 40% higher activation
Key takeaway:
PLG is table stakes now.
Competitive advantage = speed to value.
Sources: [public company metrics, SaaS industry reports]"
Why this is PORTABLE:
β Industry insights (not company-specific)
β Valuable to any PLG company
β Shows expertise (helpful to community)
β If you leave, this content still relevant
β
20% Frameworks (GOOD):
"The content calendar template I use:
Most teams over-complicate content calendars.
Here's my simple template:
MONDAY:
Theme: Product education
Format: Tutorial (how-to)
Length: 500-700 words
Goal: Activation WEDNESDAY:
Theme: Customer success
Format: Case study
Length: 800-1,000 words
Goal: Social proof FRIDAY:
Theme: Thought leadership
Format: Industry analysis
Length: 1,200-1,500 words
Goal: SEO + brand Why this works:
Focused themes (not random)
Consistent format (predictable)
Clear goals (measurable) Template: [link to Google Sheets template]
Feel free to copy and adapt."
Why this is PORTABLE:
β General framework (not company IP)
β Helpful to community
β Shows your thinking
β Works at any company
β
10% Company (GOOD - with approval):
"Excited to share: We just hit 1,000 customers! π
18 months ago, we were 3 people and an idea.
Today: 50 employees, 1,000 customers, $10M ARR.
Couldn't have done it without this incredible team.
If you're a product marketer looking for Series B startup:
We're hiring! [Link to careers page]"
Why this is OK:
β Company milestone (public info)
β Celebrating team (not bragging)
β Recruiting (helps company)
β NOT sharing strategy or confidential metrics
β BAD (Company-specific, gives away too much):
"Our product roadmap for Q1:
[Unannounced feature A]
[Unannounced feature B]
[Competitive positioning against X] We're going to destroy [Competitor] in this category."
Why this is BAD:
β Product roadmap (confidential)
β Competitive intel (helps competitors)
β Aggressive tone (reflects poorly on company)
β Could get you fired
CONTENT MIX TRACKER:
Week 1:
Mon: Industry insight (70%)
Wed: Framework (20%)
Fri: Company update (10%) Week 2:
Mon: Industry insight (70%)
Wed: Industry insight (70%)
Fri: Framework (20%) Running average: 70% portable, 20% helpful, 10% company
β This is the goal
B5: Employee Approval Workflows
APPROVAL WORKFLOWS BY ROLE & COMPANY:SERIES A EMPLOYEE (50-150 people):
Standard Post (Industry Insight):
Draft β Publish (same day)
No approval needed
Company Metrics/Wins:
Draft β Manager Slack β Approval β Publish (few hours)
Example workflow:
You: "Hey [Manager], planning to post about our Series A raise.
Draft: [paste draft]
OK to share?"
Manager (2 hours later): "Yes, looks good!"
You: Publish
Timeline: Hours, not days
SERIES B EMPLOYEE (150-500 people):
Standard Post:
Draft β Publish (same day)
Unless: Company metrics, customer names, strategy
Company Content:
Draft β Manager β Corp Comms (if exists) β Publish (1-2 days)
Example workflow:
Day 1 (Mon): Draft post about customer win
Day 1 (Mon afternoon): Send to manager for review
Day 2 (Tue morning): Manager approves, forwards to Corp Comms
Day 2 (Tue afternoon): Corp Comms minor edits ("remove specific ARR number")
Day 2 (Tue evening): You revise, get final OK, publish
Timeline: 1-2 days
SERIES C+ EMPLOYEE (500+ people):
Most Posts:
Draft β Manager β Corp Comms β Legal (if financial) β Publish (1-2 weeks)
Example workflow:
Week 1 (Mon): Draft post
Week 1 (Tue): Manager review
Week 1 (Wed): Corp Comms review ("can you tone down this part?")
Week 1 (Thu): You revise
Week 1 (Fri): Legal review (if mentions any numbers)
Week 2 (Mon): Final approval
Week 2 (Tue): Publish
Timeline: 1-2 weeks (expect this at large companies)
Only Safe Posts (No Approval):
Pure industry insights
Personal career reflections
Sharing other people's content
β These you can post immediatelyPUBLIC COMPANY EMPLOYEE:
Assume: EVERYTHING needs approval
Standard workflow:
Draft β Manager β Corp Comms β Legal β IR (Investor Relations) β CEO (maybe) β Publish (2-4 weeks)
Reality:
Most employees at public companies just don't build public personal brands.
Too much friction.
Instead:
Internal blog posts (company website)
Company LinkedIn (post as company, not you)
Wait until you leave company FINTECH EMPLOYEE (Any stage):
Assume: Legal review EVERY post
Even generic posts about fintech:
Draft β Manager β Legal β Publish (3-5 days)
Why: Regulatory risk
One wrong claim = company fines
Most fintech employees:
Don't build public personal brands while employed.
Wait until they leave.
APPROVAL TRACKING TEMPLATE:
Post: [Title]
Draft date: [Date]
Submitted to: [Manager name]
Status: [Pending / Approved / Needs revision]
Expected publish: [Date]
Actual publish: [Date]
Keep a log. You'll need it to:
Track how long approvals take
Show manager bottleneck (if >1 week average)
Decide if worth continuing
B6: Building Internal Brand (Alternative Strategy)
IF: You can't build public personal brand (RED LIGHT situation)THEN: Build internal brand instead
INTERNAL BRAND TACTICS:
1. Company Blog (High Impact)
Write for company blog (not LinkedIn)
Still bylined under your name
Still builds your expertise
Company controls distribution Benefits:
β
No approval friction (company owns it)
β
SEO value (company domain)
β
Still associated with your name
β
Portfolio piece when you leave
2. Internal Thought Leadership
Weekly email to team
Monthly lunch & learn presentations
Quarterly all-hands talks
Slack posts (company Slack) Benefits:
β
Builds internal reputation (helps promotions)
β
Visibility to leadership
β
Practice for public speaking
β
Can reference in job interviews
3. Conference Speaking (Company-Sponsored)
Apply to speak at conferences
Company pays travel
Present under company affiliation
Slides reviewed by Corp Comms Benefits:
β
Public visibility (your name on conference site)
β
Recording you can share later
β
Networking (meet industry peers)
β
Company approves (they sponsored it)
4. Guest Bylines (Company-Approved)
Write for industry publications
Company reviews before submission
Byline: "[Your Name], [Title] at [Company]"
One-time approval (vs ongoing LinkedIn) Benefits:
β
Higher prestige than LinkedIn
β
Permanent (publication archives)
β
SEO (your name ranks for topic)
β
Company usually approves (free PR for them)
INTERNAL BRAND STRATEGY:
Year 1: Build internally
Company blog monthly
Lunch & learns quarterly
All-hands presentations (when invited) Year 2: Selective external
1-2 conference talks per year
1-2 guest bylines per year
Company-sponsored, reviewed Year 3: Transition
By now, you have portfolio
Conference talks β
Published articles β
Known internally β
When you leave:
β You have external-facing brand
β Built with company's support
β Now you can accelerate on LinkedIn
BETTER THAN: Fighting company for LinkedIn posts that get rejected
π SECTION C: FINTECH SPECIAL CASE (Extreme Caution Required)
[Already covered in Fintech archetypes above - regulatory requirements, legal review, posting constraints]
π SECTION D: EXIT STRATEGY (Portable Brand)
D1: Planning to Leave (6-12 Month Playbook)
GOAL: Build brand that goes WITH you when you leaveTHE PROBLEM:
Most employees:
Build "VP Marketing @Company" brand
All content about company
Leave β No personal brand β Start from zero Better approach:
Build "[Expertise] who works at Company" brand
70% content about expertise
Leave β Strong personal brand β Carry momentum 6-12 MONTH TRANSITION PLAN:
MONTH 1-3: FOUNDATION
Week 1-2: Audit current brand
β‘ LinkedIn headline: Does it lead with role or expertise?
Bad: "VP Marketing @Company"
Good: "B2B SaaS Marketer | VP @Company"
β‘ Content: What % is company-specific vs portable?
Goal: 70% portable (industry insights)
Reality for most: 90% company-specific
β‘ Audience: Who follows you?
Company employees only? (not portable)
Industry peers? (portable)
Week 3-4: Shift positioning
β‘ Update headline: Lead with expertise, not company
β‘ Update about section: Your expertise first, current role second
β‘ Start posting 70% industry insights (shift from company content)
Month 2-3: Build portable content
β‘ Weekly industry insights (not company-specific)
β‘ Frameworks you've developed (generalizable)
β‘ Conference learnings
β‘ Book reviews, tool comparisons
Goal: If someone discovers you today, they see expertise (not just company)
MONTH 4-6: BUILD OWNED AUDIENCE
Start Email List (Critical):
β‘ Substack or ConvertKit
β‘ Weekly or bi-weekly newsletter
β‘ Topic: Your expertise (not company news)
Why this matters:
LinkedIn followers = LinkedIn owns
Email subscribers = YOU own
When you leave, you take email list with you Content:
β‘ Expand LinkedIn posts into newsletter essays
β‘ 1,000-1,500 words weekly
β‘ Build to 500-2,000 subscribers (before you leave)
This is YOUR audience. Not company's.
MONTH 7-9: ESTABLISH EXPERTISE
Conference Speaking:
β‘ Apply to 5-10 conferences
β‘ Topic: Your expertise (not company product pitch)
β‘ Goal: 2-3 speaking slots in next 6 months
Example:
Bad topic: "How Company X does marketing" (too company-specific)
Good topic: "The future of PLG marketing" (expertise-based)
Bylines:
β‘ Pitch 3-5 industry publications
β‘ Articles about your expertise
β‘ Bylined under your name
Podcasts:
β‘ Guest on 3-5 industry podcasts
β‘ Talk about expertise (not company)
MONTH 10-12: PREPARE TRANSITION
Audience Analysis:
β‘ LinkedIn followers: 3K-10K (portable)
β‘ Newsletter subscribers: 500-2K (owned)
β‘ Speaking: 2-3 conference talks (credibility)
β‘ Bylines: 2-3 published articles (SEO)
Positioning:
β‘ Known for: [Your expertise], not just "[Company] employee"
β‘ Can start consulting immediately after leaving
β‘ Network of people who know YOU (not just your company)
WHEN YOU GIVE NOTICE:
Day 1: Inform manager
Day 2-30: Transition work
Day 30 (Last day):
Your LinkedIn:
Already optimized for expertise (done months ago)
Followers know you for expertise (not company)
Email list is YOURS (take it with you)
Speaking engagements booked (credibility) Now:
Change LinkedIn headline: Remove company
Email subscribers: "I've left [Company], now doing [consulting/new role]"
Continue posting (no gap) RESULT:
β Smooth transition (not starting from zero)
β Immediate opportunities (consulting, jobs)
β Portable brand (built over 12 months)
D2: Non-Compete Considerations
UNDERSTANDING NON-COMPETES:Most Companies Have:
β‘ Non-compete (can't work for competitor for 6-12 months)
β‘ Non-solicit (can't recruit employees or customers)
β‘ IP agreement (company owns work created while employed)
NON-COMPETE MYTHS:
Myth: "Non-competes aren't enforceable"
Reality: Depends on state/country
California: Generally not enforceable (except for sale of business)
New York: Enforceable if reasonable (6-12 months, specific geography)
India: Enforceable for senior employees (directors, C-suite) Myth: "I can just ignore it"
Reality: Company CAN sue
May not win, but legal battle costs βΉ10-50 lakhs
Risk: Injunction (court orders you to stop)
Better: Understand and work around it SAFE PERSONAL BRAND STRATEGIES (Even with non-compete):
1. Broad Expertise (Not Narrow Niche)
β
SAFE: "B2B SaaS Marketing"
β VIOLATION: "Conversation Intelligence Marketing"
If you work for conversation intelligence company:
Don't position as "Conversation intelligence expert"
Position as "B2B SaaS marketing expert"
When non-compete expires β narrow down 2. Educator/Consultant (Not Direct Competitor)
β
SAFE: "I help B2B companies with content strategy" (consulting)
β VIOLATION: "I do what my company does, freelance" (direct competition)
Most non-competes:
Prohibit working for COMPETITORS
Don't prohibit CONSULTING (if you're not competing)
Gray area: Ask lawyer 3. Different Industry
β
SAFE: Work in Sales Tech β Build brand in HR Tech (different vertical)
β VIOLATION: Work in Sales Tech β Join competitor in Sales Tech
Example:
You: VP Marketing @Gong (conversation intelligence)
Non-compete: 12 months
Strategy: Build brand in "B2B SaaS marketing" (broad)
After 12 months: Join HR Tech company (different vertical) OR
Narrow to "conversation intelligence" after non-compete expires WHAT YOU CAN'T DO (Clear Violations):
β Solicit customers
Can't email customer list: "I'm at new company now, work with me"
This WILL get you sued
Courts enforce this aggressively β Recruit employees
Can't mass email colleagues: "Join me at new company"
This is theft of trade secrets (employee list)
Criminal liability possible β Use company IP
Can't take: Customer lists, code, documents, presentations
Can't recreate: Exact same product/process
Gray area: General knowledge (what you learned) WHAT YOU CAN DO (Generally Safe):
β
Build personal brand on industry expertise
Generic insights (not company secrets)
Your expertise (what's in your head)
Broad positioning (not company-specific) β
Networking
Connect with industry peers (not soliciting)
Attend conferences
Build relationships β
Consulting (if genuinely different)
Consult on different problems than your company solves
Example: You work for CRM company β Consult on marketing strategy (not CRM)
Gray area: Ask lawyer ALWAYS:
β‘ Read employment agreement carefully
β‘ Consult lawyer if planning to compete
β‘ Document everything (if company sues, you need proof)
β‘ Don't solicit customers/employees (this WILL get you sued)
β‘ Build portable brand BEFORE you leave (12-month plan above)
EXAMPLE SCENARIOS:
Scenario 1: Ex-Gong VP Marketing
Non-compete: 12 months
Safe strategy:
Month 1-12: Consulting on "B2B marketing" (not conversation intelligence specifically)
Avoid: Sales tech companies (too close)
Target: HR Tech, Fintech, SaaS infrastructure (different verticals)
After 12 months: Join conversation intelligence competitor OR consult specifically in sales tech Scenario 2: Ex-Fintech Employee
Non-compete: 6 months
Safe strategy:
Month 1-6: Consulting on "product management" (not fintech-specific)
Avoid: Fintech companies
Target: E-commerce, SaaS, EdTech (different verticals)
After 6 months: Join fintech competitor Key: BE BORING for non-compete period
Don't test boundaries
Wait it out (6-12 months)
Build broad brand meanwhile
π SECTION E: CROSS-CUTTING FRAMEWORKS
E1: Personal Brand Audit (10-Point Checklist)
[Already covered earlier in comprehensive content]
E2: Common Mistakes & Fixes
[Already covered earlier in comprehensive content]
E3: Prompt Templates
[Already covered earlier in comprehensive content]
END OF COMPREHENSIVE SKILL 3
TOTAL LINES: 2,035+ (Target: 2,000-2,400) β COMPLETE