Skip to content

Instantly share code, notes, and snippets.

@adamseoul
Created February 5, 2026 18:47
Show Gist options
  • Select an option

  • Save adamseoul/6c54908802430ede4dd39a29a9967ffd to your computer and use it in GitHub Desktop.

Select an option

Save adamseoul/6c54908802430ede4dd39a29a9967ffd to your computer and use it in GitHub Desktop.
TendVillage - Local Care Marketplace Business Plan

Local Care Marketplace - Business Plan

The Opportunity

Care.com dominates nationally but ignores local SEO. They're one brand trying to rank everywhere. Meanwhile, the Google Local Pack (the 3 listings that show up on Maps) is wide open in most American cities.

Winston-Salem Example

Search: "nanny near me" in Winston-Salem, NC (population 250,000)

What shows up:

  • ONE local listing: "Family Friend Nanny Placement"
  • 5.0 stars, 1 review
  • No website
  • No business hours listed

This is a ghost listing. Someone set it up years ago and forgot about it. They're probably getting 100+ clicks/month and fumbling every lead.

We can take this traffic for free.


Market Size

Cities Like Winston-Salem

City Size Count in US Competition Level
50,000 - 100,000 ~800 cities Almost zero
100,000 - 250,000 ~200 cities Very weak
250,000 - 500,000 ~70 cities Weak to moderate
500,000 - 1,000,000 ~30 cities Some competition
1,000,000+ ~10 cities Competitive

Target: ~1,000+ cities with population 50,000 - 500,000

Most have either:

  • No local listings at all
  • 1-2 stale listings with no website, few reviews
  • Local agencies not doing digital marketing

Search Volume Estimates

For a city of 250,000 (like Winston-Salem):

Keyword Monthly Searches
nanny near me 50-100
nanny [city name] 30-50
babysitter near me 100-200
babysitter [city name] 50-100
childcare [city name] 50-100
daycare near me 100-200
Total ~400-750/month

Extrapolated across 1,000 cities: 400,000 - 750,000 searches/month

These are HIGH INTENT searches - people actively looking to hire.

Traffic Value

Metric Conservative Optimistic
Total monthly searches 400,000 750,000
Local pack click rate 44% 44%
Clicks to our listings 176,000 330,000
Conversion to signup 5% 10%
New users/month 8,800 33,000

At $20/month subscription = $176,000 - $660,000 MRR from free organic traffic alone.


Business Model

Two-Sided Marketplace

Families:

  • Search for caregivers
  • Free to browse
  • $20/month to message/connect (or per-connection fee)

Caregivers:

  • Create profile for free
  • Get found by local families
  • Optional: $10/month for "featured" placement
  • Optional: $35 for background check badge

Revenue Streams

Stream Price Notes
Family subscription $20/month Unlimited messaging
Caregiver featured listing $10/month Higher visibility
Background checks $35 one-time Via Checkr API, we keep $5
Job postings $25/post Families post specific jobs

Local Operator Model (Franchise-Style)

Why Local Operators?

Each city needs someone to:

  • Run local Facebook groups / community outreach
  • Handle customer service for that area
  • Vet and approve caregivers
  • Build Google reviews
  • Do local marketing / word of mouth

We can't do this from one central location. We need boots on the ground.

Operator Economics

Their City Revenue Their Cut (5%)
$1,000/month $50
$5,000/month $250
$10,000/month $500
$20,000/month $1,000

Not a full-time job, but real money for:

  • Stay-at-home parents
  • Retirees
  • Side hustlers
  • People already running local Facebook groups

Operator Responsibilities

  1. Customer Service - Respond to local support tickets within 24 hours
  2. Caregiver Vetting - Review and approve local caregiver profiles
  3. Community Building - Grow local Facebook group, attend local events
  4. Review Generation - Get families to leave Google reviews
  5. Quality Control - Flag bad actors, resolve disputes

Performance Metrics

Operators must maintain:

  • Response time < 24 hours
  • Customer satisfaction > 4.0 stars
  • Minimum 10 new caregivers onboarded/month
  • Active in local Facebook group weekly

Miss metrics = warning. Repeat = lose territory.


Crypto/Blockchain Layer

The Problem

Local operators need to trust they're getting their fair cut.

Traditional approach: "Trust our spreadsheet."

Their concern: "Are you really showing me all the revenue? How do I know I'm getting my 5%?"

The Solution: On-Chain Accounting

Every transaction recorded on blockchain. Operators can verify themselves. No disputes.

Revenue comes in (credit card via Stripe)
         ↓
Transaction recorded on-chain:
  - City: Winston-Salem
  - Amount: $20
  - Date: 2026-02-05
         ↓
Smart contract calculates operator cut:
  - Winston-Salem operator: $1.00 (5%)
         ↓
Tokens minted to operator's wallet
         ↓
Operator can view balance anytime
         ↓
Redemption: Burn tokens → receive USD

Token Model (Non-Tradeable)

Key insight: The token is NOT publicly traded.

Feature Why
Minted by platform only We control supply
Cannot be sold on exchanges No SEC issues
Redeemable only through us We pay USD on redemption
Visible on-chain Transparent accounting

It's like store credit on blockchain. They can see their balance, verify the math, but only cash out through us.

1 token = $1 USD (fixed rate)

Why This Works

Benefit Explanation
Transparency Operators audit the ledger themselves
Trust No "you're hiding revenue" accusations
Simplicity They get paid in USD like they want
Regulatory safety Not a tradeable security
Accountability Every dollar tracked, nothing hidden

Technical Implementation

  • ERC-20 token on Base (Coinbase L2) - cheap gas fees
  • Mint function: Only platform can mint new tokens
  • Burn function: Tokens destroyed on redemption
  • Dashboard: Operators see balance + transaction history
  • Redeem button: Request payout → tokens burned → USD sent

Estimated dev time: 1-2 weeks for smart contracts


Why Local Operators? The Traffic Opportunity

The Problem We Discovered

Searched "nanny near me" in Winston-Salem:

  • ONE local result - a ghost listing with 1 review, no website
  • But there's a Facebook group with 800+ people actively discussing childcare

This is everywhere. Every city has:

  • Weak or zero Google local results
  • Active Facebook groups with hundreds/thousands of members
  • Moderators already doing this work for free

Who We Target First

Facebook group moderators. They're already:

  • Running local childcare communities
  • Vetting recommendations informally
  • Answering questions from parents
  • Trusted by their community

Our pitch to them:

"You're already doing this. You have 800 people in your group. But you get nothing - Facebook gets the ad money.

What if you owned winstonsalem.tendvillage.com? What if every subscription in Winston-Salem put money in your pocket? What if your work actually built something that's yours?"

Local Business = Local Traffic

Each operator can set up a real local business:

  • Register an LLC in their state (optional but looks legit)
  • Use their home address on Google Business Profile
  • Get a local phone number
  • Own a subdomain: winstonsalem.tendvillage.com

Why this matters:

Google shows local results based on:

  1. Relevance (we have nanny keywords)
  2. Distance (their home address is IN the city)
  3. Prominence (reviews, activity)

A real person with a real address beats a corporate "serving all of America" listing.

Subdomain Structure

tendvillage.com (main site)
├── winstonsalem.tendvillage.com (Winston-Salem operator)
├── charlotte.tendvillage.com (Charlotte operator)
├── dallas.tendvillage.com (Dallas operator)
└── ... 1,000 cities

Each subdomain:

  • Has its own Google Business Profile
  • Ranks locally for that city
  • Is "owned" by the local operator
  • Shows local caregivers only

It's not replacing Facebook groups - it's giving them a home base.

They keep running their Facebook group. But now they have:

  • A real website they can link to
  • A way to get paid for their work
  • A permanent record that isn't owned by Facebook

Google Business Profile Strategy

How to Dominate Local Search

Each city gets its own Google Business Profile:

Example:

  • Business Name: "TendVillage Winston-Salem"
  • Category: "Nanny Service" or "Child Care Agency"
  • Address: Operator's home address (real local address)
  • Phone: Local number (via Twilio)
  • Website: winstonsalem.tendvillage.com

Ranking Factors

Factor How We Win
Relevance Nanny/childcare keywords on profile
Distance Local address in the city
Prominence Reviews, photos, activity

Review Generation Machine

  • Every happy family = ask for Google review
  • Incentivize: "Leave a review, get 1 month free"
  • Operators responsible for hitting review targets
  • Profiles with 100+ photos get 1065% more clicks

Scaling to 1,000 Cities

Phase Cities Timeline
Phase 1 10 pilot cities Month 1-3
Phase 2 50 cities Month 4-6
Phase 3 200 cities Month 7-12
Phase 4 1,000 cities Year 2

Each city = one operator + one Google Business Profile + local Facebook presence


Competitive Advantage

Why Care.com Can't Do This

Us Care.com
1,000 local brands 1 national brand
1,000 Google listings 1 website
Local operators doing outreach Central team, no local presence
Shows up in Local Pack Shows up in organic only
Community trust Corporate feel

They're a tech company. We're 1,000 local businesses powered by tech.

Moat

  1. Local SEO dominance - First mover in each city owns the rankings
  2. Operator network - Hard to replicate boots on the ground
  3. Review accumulation - Reviews compound over time
  4. Community trust - Local > national for care decisions

Domain Options

Available (as of 2026-02-05):

Top Picks - Community Focused

Domain Vibe
tendvillage.com "It takes a village" + tender care
tendtribe.com Your tribe of caregivers

Why "Tend" works:

  • Tend to children
  • Tend to your community
  • Tender, gentle care
  • Like tending a garden - nurturing
  • Soft, caring word - not corporate, not tech-bro

Other Available Options

Domain Vibe
mylocalnanny.com Clear, SEO-friendly
nanniehub.com Hub/platform feel
hellonannie.com Friendly, approachable
sitterboard.com Community board
raisedby.co "Raised by the village"

Recommendation: tendvillage.com or tendtribe.com


Tech Stack

Platform

Layer Technology
Frontend Next.js / React
Backend Node.js
Database PostgreSQL
Payments Stripe Connect
Auth JWT / OAuth
Hosting AWS

Blockchain

Layer Technology
Network Base (Coinbase L2)
Token ERC-20
Contracts Solidity
Wallet connect Wagmi / Viem

Integrations

Service Purpose
Checkr API Background checks
Twilio Local phone numbers per city
Mailgun/SES Email
Google Business API Manage listings

Financial Projections

Year 1 (10 cities pilot)

Metric Value
Cities 10
Users per city 200
Total users 2,000
Paying families (30%) 600
MRR $12,000
ARR $144,000
Operator payouts (5%) $7,200/year

Year 2 (200 cities)

Metric Value
Cities 200
Users per city 300
Total users 60,000
Paying families (30%) 18,000
MRR $360,000
ARR $4,320,000
Operator payouts (5%) $216,000/year

Year 3 (1,000 cities)

Metric Value
Cities 1,000
Users per city 400
Total users 400,000
Paying families (30%) 120,000
MRR $2,400,000
ARR $28,800,000
Operator payouts (5%) $1,440,000/year

Next Steps

Immediate (Week 1-2)

  1. Register domain (mylocalnanny.com or similar)
  2. Set up Google Business Profile for Winston-Salem
  3. Build simple landing page
  4. Create Facebook group for Winston-Salem
  5. Talk to friend about smart contract architecture

Short-term (Month 1-2)

  1. Build MVP platform (profiles, search, messaging)
  2. Onboard 50 caregivers in Winston-Salem
  3. Get first paying families
  4. Collect Google reviews
  5. Document playbook for operators

Medium-term (Month 3-6)

  1. Expand to 10 pilot cities
  2. Recruit and train operators
  3. Deploy smart contracts for revenue tracking
  4. Refine operator metrics and accountability
  5. Iterate on product based on feedback

Long-term (Year 1-2)

  1. Scale to 200+ cities
  2. Launch token redemption system
  3. Add premium features (background checks, payroll)
  4. Potentially raise funding for faster expansion
  5. Build mobile apps

Why Blockchain? The Fairness Argument

We Want To Be Fair

This isn't about crypto hype. It's about building something fair.

Fair to:

  • Local operators - Can't be fired on a whim. Democratic process.
  • Caregivers - Good reputation follows them. Bad actors can't hide.
  • Families - Complaints are permanent. Bad caregivers can't just move towns.
  • Everyone - Transparent rules. No hidden decisions. Anyone can audit.

Problem 1: Bad Caregivers Move Towns

Current system:

  • Caregiver is terrible in Winston-Salem
  • Gets bad reviews, complaints
  • Moves to Charlotte
  • Creates new profile on Care.com
  • Starts fresh. No history.
  • Hurts another family.

Blockchain solution:

Identity is permanent. On-chain record follows them.

Caregiver ID: 0x7a3f...
├── Winston-Salem reviews: 2.1 stars (47 reviews)
├── Complaints: 3 verified
├── Charlotte profile linked: YES
└── Cannot escape history

They can move. They can't hide.

Problem 2: Complaints Get Deleted

Current platforms:

  • Someone complains about a caregiver
  • Caregiver threatens to sue
  • Platform deletes complaint to avoid hassle
  • History erased

Our principle: Complaints are NEVER deleted.

  • Complaints go on-chain. Permanent.
  • Caregiver can REFUTE (add their side of the story)
  • Both the complaint AND the refutation are permanent
  • Community sees both sides
  • No one can make history disappear
Complaint #1247
├── Filed by: Family 0x8b2c...
├── Date: 2026-03-15
├── Claim: "Left children unsupervised"
├── Status: DISPUTED
├── Caregiver response: "Parent was 2 hours late. I had emergency..."
├── Resolution: Community reviewed, marked as misunderstanding
└── PERMANENT RECORD - Neither side can delete

Problem 3: Operators Have No Protection

Traditional franchise:

  • Corporate can fire you anytime
  • "Performance issues" - no specifics
  • You built up the territory, they take it
  • No recourse

Our principle: Operators can't be removed easily.

Democratic process:

  • Clear metrics (on-chain, verifiable)
  • Strike system with warnings
  • Community can vote on disputes
  • Can't just be fired because someone doesn't like you

Problem 4: Platform Can Change Rules

Uber, Airbnb, etc.:

  • Change commission from 15% to 25%
  • Change algorithm, you disappear
  • No warning, no vote, no recourse
  • "Accept new terms or leave"

Our principle: Rules are code.

  • Revenue split is in the smart contract
  • Can't be changed without governance vote
  • Operators have voting power
  • Platform can't just rug pull

Democratic Governance for Village Leaders

How Operators Get Elected

Option A: First Mover + Community Validation

Phase 1: Territory unclaimed
         ↓
Phase 2: Someone applies (stakes tokens)
         ↓
Phase 3: 30-day provisional period
         ↓
Phase 4: Local community votes to confirm
         ↓
Phase 5: Confirmed = full operator status

Community has a say. Not just whoever claims it first.

Option B: Election When Multiple Candidates

Territory opens
         ↓
Multiple people apply
         ↓
7-day campaign period
         ↓
Local users vote
         ↓
Winner becomes operator

How Operators Get Removed

Cannot be removed by:

  • Platform founders saying "we don't like them"
  • Competitor complaining
  • Single angry customer
  • Arbitrary decision

CAN be removed by:

  1. Metrics failure (automatic)

    • Response time > 48 hours for 14+ days
    • Satisfaction below 3.0 for 30+ days
    • No login for 30+ days
    • Smart contract executes removal
  2. Community vote (democratic)

    • 10% of local users petition for review
    • 7-day review period
    • 2/3 majority required to remove
    • All votes recorded on-chain
  3. Voluntary resignation

    • Operator can step down anytime
    • Territory goes to election

Operator Protections

Protection How It Works
Can't be fired on a whim Requires metrics failure OR community vote
Strike system with warnings 3 strikes before removal, each with appeal window
Appeal process Can dispute metrics, community reviews
Transition period 30 days to hand over if removed
Stake returned If removed fairly (not for fraud), stake returned

Permanent Records - Never Deleted

What Gets Recorded Forever

Record Type Details
Caregiver complaints Who filed, what happened, caregiver response
Caregiver reviews Rating, text, verified booking
Operator performance Daily metrics, strikes, warnings
Governance votes Who voted, how they voted, outcome
Financial transactions Revenue, splits, payouts
Identity verifications ID checked, background check status

What "Permanent" Means

  • Stored on blockchain (immutable)
  • Cannot be deleted by platform
  • Cannot be deleted by person it's about
  • Can be REFUTED (add context) but not erased
  • Anyone can verify at any time

Why This Matters

For families:

"I can see this caregiver's FULL history. Not just what they want me to see. Every complaint, every response, every review. Across every city they've worked in."

For caregivers:

"My good reputation follows me. If I move cities, I don't start from zero. My 200 five-star reviews come with me."

For operators:

"I can see exactly why I got a strike. I can see exactly what I need to fix. No mystery, no politics."


The Pitch: Why This Is Different

To Operators (Village Leaders)

"You're already the person everyone asks for childcare recommendations. Why not own that?

With TendVillage, you get 5% of every subscription in your city. Not 'trust us' - tracked on blockchain, you can verify every dollar.

You can't be fired on a whim. Only for clear metrics failure or if your community votes you out. The rules are public code, not someone's mood.

Build something that's yours. Your village, your reputation, your income."

To Families

"Care.com lets bad caregivers create new profiles and start fresh. We don't.

Every complaint is permanent. Every review follows them. They can explain their side, but they can't erase history.

Your village leader is elected by your community, not assigned by corporate. They answer to you."

To Caregivers

"Your reputation is your asset. On TendVillage, it's portable.

Move cities? Your 5-star reviews come with you. Your verified background check comes with you. You don't start from zero.

Bad reviews from years ago? You can respond, show how you've grown. But you can't hide - and neither can anyone else."


Why Crypto/Blockchain Makes Sense Here

The Reality Today

People are already doing this work on Facebook for free:

  • Running local childcare groups
  • Vetting caregivers informally
  • Answering questions from parents
  • Building community trust

They get nothing. No ownership. No revenue share. Facebook profits, they don't.

If we give them a platform and a cut, we're ahead. But then we have a new problem: governance.

Is Blockchain the Right Tool?

My honest assessment: Yes, for this specific use case.

Not because "crypto is cool" - because it solves real problems:

Problem Traditional Solution Why It Fails Blockchain Solution
Revenue transparency Spreadsheet/dashboard "Trust me bro" Public ledger they can verify
Operator accountability HR decisions Disputes, lawsuits, drama Rules in code, automatic execution
Territory ownership Legal contracts Expensive, slow, lawyers Smart contract, instant, cheap
Taking territory away Fire them, hope they don't sue Messy Metrics trigger automatic consequences
Proving fairness "We're fair, promise" No one believes it Anyone can audit the contract

The core insight:

We're creating a distributed network of independent operators who need to trust:

  1. They're getting their fair cut (revenue transparency)
  2. They can't be fired arbitrarily (clear rules)
  3. Others can't be fired arbitrarily (system is fair)
  4. If they do the work, they keep the territory (ownership)

Blockchain isn't about payments - it's about trust without trusting.


The Three Hard Problems

Problem 1: How Do We Take Territory Away?

Why this is hard:

  • Give someone Winston-Salem
  • They work hard for 6 months, build it up
  • Then they stop showing up
  • Revenue keeps coming in (from their earlier work)
  • They still get 5% for doing nothing

Can't just fire them:

  • "You fired me unfairly!"
  • "I was sick that week"
  • "Your metrics are wrong"
  • Lawsuits, drama, bad reputation

Blockchain solution:

Rules are code. Not decisions - executions.

IF response_time > 48_hours FOR 7_days THEN strike += 1
IF strikes >= 3 THEN territory_status = OPEN

No human decides. The contract executes. They can see the rules before they sign up.

Problem 2: Why Would We Take It Away?

Valid reasons (must be measurable):

Reason Metric
Not responding to customers Response time > 48 hours
Not active No login for 7+ days
Bad service Customer satisfaction < 3.0 stars
Not processing applications Backlog > 10 caregivers waiting
Complaints X verified complaints in Y period

Invalid reasons (too subjective):

  • "We don't like them"
  • "Someone better applied"
  • "They're not growing fast enough"
  • "Vibes are off"

If it's not measurable and on-chain, it's not a valid reason.

Problem 3: Who Gets It Next?

When a territory opens up, who gets it?

Option A: First Come First Served

  • Territory opens
  • First person to claim it wins
  • Problem: Bots, unfair advantage

Option B: Auction

  • Territory opens
  • People bid (stake tokens)
  • Highest bid wins
  • Problem: Rich people buy everything

Option C: Waitlist + Qualification

  • People apply for territories they want
  • When one opens, top of waitlist gets first shot
  • Must meet minimum qualifications (stake, reputation)
  • Problem: How to rank the waitlist fairly?

Option D: Performance-Based Assignment

  • Operators can only get new territories if current ones are performing
  • Builds empire through excellence
  • Problem: First-timers can't get started

Probably some combination:

  • New operators start with smaller/easier markets
  • Prove themselves → eligible for bigger markets
  • Existing high-performers get first dibs on openings
  • Minimum stake required to claim

What We Need From Crypto Architecture

The Token

Not for speculation. For accounting.

  • Minted when revenue comes in
  • Represents operator's earned share
  • Redeemable for USD through platform only
  • Not traded on exchanges
  • Not a security (just internal accounting)

Why bother with a token at all?

Because it creates a verifiable record. Operator can look at their wallet:

  • "I have 5,000 tokens"
  • "That means I've earned $5,000"
  • "I can see every transaction that created these"
  • "No one can dispute this"

The Territory Registry

On-chain record of who owns what:

Territory: Winston-Salem, NC
Owner: 0x1234...
Status: ACTIVE
Claimed: 2026-02-01
Stake: 500 USDC
Performance Score: 87/100
Strikes: 0

Anyone can query. Fully transparent.

The Performance Oracle

Feeds real-world data on-chain:

  • Platform tracks: response times, logins, satisfaction scores
  • Daily/weekly: data pushed to blockchain
  • Operators can verify: "Yes, that matches what I see in my dashboard"
  • Dispute window: 7 days to challenge if data looks wrong

The Consequence Engine

Smart contract that executes rules:

Every week:
  - Pull performance data
  - Calculate scores
  - Issue strikes if needed
  - Slash stakes if needed
  - Open territories if needed
  - Distribute revenue shares

No human in the loop. Rules execute automatically.


Questions for Crypto Architect

  1. Revenue tracking architecture

    • Payments come in via Stripe (fiat)
    • How do we mirror this on-chain reliably?
    • Do we convert to stablecoin first, or just log transactions?
  2. Oracle design

    • Performance data lives in our database
    • How to get it on-chain in a way operators trust?
    • What's the right dispute mechanism?
  3. Staking mechanics

    • How much stake for a territory? (Flat? Based on city size?)
    • Stake in USDC or platform token?
    • Slashing schedule - how much per violation?
  4. Territory lifecycle

    • How does claiming work?
    • How does transfer work (if allowed)?
    • How does forfeiture work?
    • Cooldown periods?
  5. Edge cases

    • Operator dies/incapacitated - what happens?
    • Operator wants to sell - allowed?
    • Two operators want same territory - resolution?
    • City boundaries overlap - how to handle?
  6. Scaling

    • 10 territories = easy
    • 1,000 territories = gas costs?
    • Do we need L2? (Base, Polygon, Arbitrum)
  7. Legal

    • Is this token a security?
    • How to structure to stay compliant?
    • Operator agreement - smart contract + legal contract?

What Success Looks Like

A system where:

  • Operators feel ownership - "This is MY territory, I earned it"
  • Operators feel secure - "I can't be fired on a whim"
  • Operators feel accountable - "I know exactly what's expected"
  • Bad actors get removed - "The rules apply to everyone"
  • Good actors thrive - "My work is rewarded fairly"
  • Everything is verifiable - "I can check the math myself"
  • No drama - "The contract decided, not some guy"

This is the hard part. The marketplace is just CRUD. The local SEO is execution. But getting the operator governance right is what makes this work at scale.


Summary

The play:

  • Care.com ignores local SEO
  • 1,000+ American cities have zero competition
  • Free organic traffic worth $2M+/year
  • Local operators do the ground work for 5% cut
  • Blockchain tracks revenue transparently
  • Everyone can verify they're getting paid fairly

We're not building another Care.com. We're building 1,000 local businesses that happen to share a platform.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment