Skip to main content

Provider & Parent Pipeline Guide

Complete pipeline strategy for managing providers and parents across launch and non-launch cities.


Overview

This document defines how we source, track, and convert providers and parents using our tool stack:

ToolPurposeUsers
AttioProvider CRMSales team
ApolloUS cold email outreachSales team
LoopsParent email marketingMarketing
Viral LoopsReferral programBoth

Provider Pipeline

Pipeline Stages

┌─────────────┐     ┌─────────────┐     ┌─────────────┐     ┌─────────────┐     ┌─────────────┐
│ Sourced │ ──► │ Contacted │ ──► │ Interested │ ──► │ Onboarding │ ──► │ Active │
└─────────────┘ └─────────────┘ └─────────────┘ └─────────────┘ └─────────────┘
│ │ │ │ │
Apollo Apollo/DM Attio CRM Attio CRM App DB
or Manual + Attio

Stage Definitions

StageDescriptionExit CriteriaTool
SourcedLead identified, not yet contactedFirst outreach sentApollo / Attio
ContactedOutreach sent, awaiting responseProvider respondsApollo / Attio
InterestedProvider engaged, evaluating JuniroAgrees to onboardAttio
OnboardingSetting up profile, listing activitiesFirst activity liveAttio
ActiveLive on platform, accepting bookingsApp DB + Attio

Tool Assignments

Apollo (US Cold Email)

Use for:

  • US providers discovered via research
  • Automated email sequences
  • Initial cold outreach at scale

Workflow:

  1. Add lead to Apollo with enriched data
  2. Enroll in email sequence (3-5 touches)
  3. If engaged → Move to Attio for relationship management
  4. If no response after sequence → Archive or retry later

Apollo Sequences:

  • us-provider-intro - Initial outreach (3 emails)
  • us-provider-follow-up - Re-engagement (2 emails)

Attio (Provider CRM)

Use for:

  • All India providers (manual outreach)
  • US providers who engage with Apollo
  • Relationship management
  • Onboarding tracking
  • Long-term pipeline

Fields:

FieldTypePurpose
nameTextContact name
emailEmailPrimary email
phonePhoneWhatsApp/call
businessNameTextProvider business name
citySelectLocation
categoriesMulti-selectActivity types
stageSelectPipeline stage
sourceSelectHow we found them
assignedToUserTeam member
lastContactDateLast interaction
notesLong textContext and history

Stage Values:

  • Sourced
  • Contacted
  • Interested
  • Onboarding
  • Active
  • Churned
  • Not Interested

Sourcing Entry Points

┌─────────────────────────────────────────────────────────────┐
│ LEAD SOURCES │
├─────────────────────────────────────────────────────────────┤
│ │
│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
│ │ Google │ │ Groups │ │ Referral │ │
│ │ Search │ │ & Blogs │ │ (Viral │ │
│ │ │ │ │ │ Loops) │ │
│ └──────┬───────┘ └──────┬───────┘ └──────┬───────┘ │
│ │ │ │ │
│ ▼ ▼ ▼ │
│ ┌─────────────────────────────────────────────────────┐ │
│ │ DECISION POINT │ │
│ │ │ │
│ │ Email sequence needed? │ │
│ │ ├── YES (US) ──► Apollo ──► Engage ──► Attio │ │
│ │ └── NO (Manual DM/Call) ──► Attio directly │ │
│ └─────────────────────────────────────────────────────┘ │
│ │
└─────────────────────────────────────────────────────────────┘

Rules:

  1. US leads needing email sequences → Apollo first → Attio when engaged
  2. India leads → Attio directly (WhatsApp/call outreach)
  3. Manual DM/call outreach → Attio directly (any country)
  4. Referrals → Attio directly (warm leads)

Multi-Channel Outreach Strategy

Always capture BOTH phone AND email when sourcing — use all channels to maximize response rate.

CountryPrimary ChannelSecondary ChannelTertiary
IndiaWhatsAppEmailPhone call
USEmail (Apollo)Phone callLinkedIn

India Outreach Cadence:

Day 0: WhatsApp (primary)
Day 2: WhatsApp follow-up
Day 3: Email follow-up
Day 5: Phone call
Day 7: Final email
Day 10: Final WhatsApp → close as "No Response"

US Outreach Cadence:

Day 0: Email 1 (Apollo)
Day 3: Email 2 (Apollo)
Day 7: Email 3 (Apollo)
Day 8+: If reply → Call to schedule meeting

Why multi-channel?

  • Different people prefer different channels
  • Multi-channel increases response rate by 2-3x
  • Shows persistence without being pushy

Launch vs Non-Launch Cities

Launch Cities (Hyderabad, Atlanta)

Priority: High — These providers go live first

Full Pipeline:

SOURCED → CONTACTED → INTERESTED → ONBOARDING → ACTIVE
│ │ │ │ │
Day 0 Day 1 Day 1-3 Day 3-7 Launch
StageTeam ActionTimeline
SourcedAdd to Attio from Justdial/Google Maps/etcDay 0
ContactedSend WhatsApp message or callDay 1
InterestedThey said yes, schedule onboarding callDay 1-3
OnboardingCollect full details, photos, verify infoDay 3-7
ActiveProfile live on JuniroLaunch day

Exit Criteria for Each Stage:

  • Sourced → Contacted: First message sent
  • Contacted → Interested: Provider responds positively
  • Interested → Onboarding: Provider agrees to join, shares details
  • Onboarding → Active: Profile complete, verified, launched

Target: 10-15 active providers per launch city before launch


Non-Launch Cities (Bangalore, Mumbai, Delhi, etc.)

Strategy: Capture and hold — build pipeline for future expansion

Abbreviated Pipeline:

SOURCED → CONTACTED → INTERESTED → (HOLD until city launches)
│ │ │
Day 0 Day 1 Day 2+
StageTeam ActionNotes
SourcedAdd to Attio (from form or manual)Auto from inbound form
ContactedSend thank-you message"We'll notify you when we launch"
InterestedMark interested, add to waitlistNo further onboarding
(HOLD)Keep warm with occasional updatesActivate when city launches

What to tell non-launch city providers:

"Thanks for your interest in Juniro! We're currently launching in Hyderabad and Atlanta first. We'll reach out as soon as we expand to [their city]. In the meantime, we'll keep you updated on our progress."

When city launches later:

  1. Filter Attio: city = [New City], stage = Interested
  2. Reach out: "Great news! We're now launching in [City]"
  3. Move through normal onboarding pipeline

Inbound vs Outbound Lead Handling

Inbound Leads (from juniro.com/providers/onboard)

Form automatically creates Attio record with:

FieldValue
StageOnboarding (already interested)
SourceInbound
PriorityHigh (launch cities) or Medium
Launch City✅ or ❌ based on city

Team action:

  • Launch city inbound → Contact within 24 hours, fast-track onboarding
  • Non-launch city inbound → Send thank-you, mark as Interested, hold

Outbound Leads (sourced by team)

Team manually adds to Attio with:

FieldValue
StageSourced
SourceJustdial, Google Maps, etc.
PriorityHigh (launch cities) or Medium

Team action:

  • Work through full pipeline: Sourced → Contacted → Interested → Onboarding → Active

Parent Pipeline

Pipeline Stages

┌─────────────┐     ┌─────────────┐     ┌─────────────┐     ┌─────────────┐
│ Waitlist │ ──► │ Engaged │ ──► │ Launch Ready│ ──► │ Active │
└─────────────┘ └─────────────┘ └─────────────┘ └─────────────┘
│ │ │ │
Loops Loops + Loops App DB
+ Viral Loops Viral Loops + App

Stage Definitions

StageDescriptionExit CriteriaTool
WaitlistSigned up, awaiting launchFirst email openedLoops
EngagedInteracting (referrals, emails)City launchesLoops
Launch ReadyCity is live, invited to useCreates accountLoops → App
ActiveUsing product, booking activitiesApp DB

Tool: Loops

Segments:

  • waitlist-parents - All waitlisted parents
  • engaged-parents - Opened 2+ emails or made referral
  • launch-ready-parents - City is live

Email Sequences:

  • parent-welcome - Immediately after signup
  • parent-nurture - Weekly updates during waitlist
  • parent-launch - City launch announcement
  • parent-referral-success - When friend signs up

Contact Properties:

PropertyTypePurpose
firstNameTextPersonalization
emailEmailPrimary contact
cityTextSegmentation
interestsTextActivity preferences
referralLinkTextViral Loops link
referralCountNumberFriends referred
sourceTextHow they found us
userTypeTextAlways "parent"

Launch vs Non-Launch Cities

Launch Cities (Hyderabad, Atlanta)

Actions:

  • Normal nurture sequence
  • Launch announcement when ready
  • Convert to active users

Non-Launch Cities

Strategy: Nurture and keep warm

Actions:

  • Accept signups (data collection)
  • Add to waitlist-parents segment
  • Send nurture emails: "We're not in your city yet..."
  • Track category interest for supply planning
  • Activate referral (skip-the-line positioning)

Messaging:

"Thanks for joining! We're not in [City] yet, but we're working on it. In the meantime, share Juniro with friends — the more interest, the sooner we'll launch in your area."


Sourcing Playbook

Provider Sources

SourceMethodEntry Point
Google SearchSearch "[city] kids activities"Apollo (US) / Attio (India)
Google MapsSearch by category + locationApollo (US) / Attio (India)
Facebook GroupsJoin parent/provider groupsAttio (manual DM)
InstagramSearch hashtags, local accountsAttio (manual DM)
Yelp/SulekhaCategory listingsApollo (US) / Attio (India)
ReferralsProvider refers providerAttio (warm lead)
InboundProvider finds usAttio

Search Queries

Google:

  • [city] kids soccer classes
  • [city] children art classes near me
  • [city] swim lessons for kids
  • [city] STEM camps summer

Instagram Hashtags:

  • #[city]kidsactivities
  • #[city]momlife
  • #[city]parenting

Outreach Templates

Cold Email (Apollo - US):

Subject: Quick question about [Business Name]

Hi [Name],

I found [Business Name] while researching kids activities in [City] — looks like you're doing great work with [activity type].

I'm building Juniro, a marketplace to help families discover activities like yours. We're launching in [City] soon and looking for quality providers to partner with.

Would you be open to a quick chat about how we can help you reach more local families?

Best,
[Your name]

WhatsApp (India):

Hi [Name], I'm [Your name] from Juniro.

We're building a platform to help parents find kids activities like [activity type]. Found [Business Name] and thought you'd be a great fit.

Would you be interested in learning more? Happy to share details over a call.

Metrics & Reporting

Provider Metrics

MetricTargetTracked In
Leads sourced / week20Attio + Apollo
Response rate>15%Apollo
Interested rate>30% of responsesAttio
Onboarding completion>80%Attio
Time to active<7 daysAttio

Parent Metrics

MetricTargetTracked In
Waitlist signups / week50Loops + Posthog
Email open rate>40%Loops
Referral rate>20%Viral Loops
Conversion to active>50% at launchApp DB

Attio Views

Create these saved views in Attio:

  1. My Pipeline - assignedTo = me, stage != Active
  2. Needs Follow-up - lastContact < 7 days ago
  3. Launch City Ready - city in [Hyderabad, Atlanta], stage = Interested
  4. Non-Launch Pipeline - launchCity = false, stage in [Sourced, Contacted, Interested]

Post-Launch Handoff

When Product Launches

Providers:

  1. Active providers migrate to app database as source of truth
  2. Attio remains for:
    • Pipeline management (pre-active stages)
    • Relationship notes and history
    • Churned provider re-engagement
  3. Sync: App DB → Attio for active provider updates

Parents:

  1. Active parents live in app database only
  2. Loops remains for:
    • Marketing emails to non-users
    • Re-engagement campaigns
    • Announcement broadcasts
  3. Transactional emails move to Resend

Reducing External Tools

Goal: Minimize tool sprawl as product matures

ToolKeep?Reason
AttioYesCRM for provider relationships, sales pipeline
ApolloYes (US only)Cold outreach at scale
LoopsYesMarketing email to non-users
Viral LoopsYesReferral program
ResendYesTransactional email
GupshupYesWhatsApp notifications

What moves to app:

  • Active user data
  • Booking/transaction data
  • User preferences
  • Communication preferences

Summary

PipelinePre-Launch ToolPost-Launch Tool
Provider PipelineAttio + ApolloApp DB + Attio
Parent PipelineLoops + Viral LoopsApp DB + Loops
Transactional CommsResend + Gupshup

Key Principles:

  1. Attio is the provider CRM — all provider relationships live here
  2. Apollo for US cold email only — engaged leads move to Attio
  3. Loops for parent marketing — transactional moves to Resend
  4. Non-launch cities = actively recruit — build pipeline early
  5. Post-launch = app database is truth — external tools for sales/marketing only