SendGrid for Gig Economy Marketplaces

Why Lifecycle Email Is Different for Gig Economy Marketplaces

You are running a two-sided marketplace. That means every lifecycle decision you make in SendGrid has to account for two distinct user populations — workers and customers — who have completely different motivations, activation patterns, and churn signals. Most email automation guides treat this as a footnote. It is actually the central challenge.

A food delivery courier who signs up but never completes their first delivery costs you acquisition spend and leaves a gap in supply. A customer who orders once and never returns costs you demand. The email sequences that fix each of these problems look nothing alike, and SendGrid needs to be configured to treat them as separate entities from the moment they enter your system.

---

Setting Up SendGrid for a Two-Sided Marketplace

Sender Identity Architecture

Use subusers in SendGrid to separate transactional and marketing streams. A minimum viable setup for a gig marketplace looks like this:

• `transactional@` — order confirmations, payment receipts, dispute notifications
• `workers@` — onboarding sequences, earnings summaries, shift availability
• `customers@` — re-engagement, promotional, referral

This separation protects your transactional deliverability. If a promotional campaign generates spam complaints, it does not contaminate the sender reputation for your order confirmation stream.

Custom Fields That Actually Matter

Before building any automation, extend your contact schema in SendGrid Marketing Campaigns with these fields:

For workers:

• `user_type` = "worker"
• `onboarding_status` — values: started, background_check_pending, approved, first_job_complete
• `lifetime_earnings`
• `days_since_last_job`
• `city_market`

For customers:

• `user_type` = "customer"
• `lifetime_orders`
• `days_since_last_order`
• `preferred_category` (e.g., home services, delivery, design)
• `acquisition_source`

These fields drive every segment and trigger condition you will build. Skipping this step means you will eventually rebuild your entire automation stack.

---

Key Events to Track and Pipe Into SendGrid

SendGrid's Event Webhook should receive event data from your platform via your backend or a CDP like Segment. The events that matter most for gig marketplaces are:

Worker-side events:

1. `worker_signup_completed`
2. `background_check_submitted`
3. `background_check_approved`
4. `first_job_accepted`
5. `first_job_completed`
6. `payment_received`
7. `job_streak_broken` — worker has not accepted a job in 14 days after being active
8. `rating_dropped_below_threshold` — e.g., below 4.2 stars

Customer-side events:

1. `customer_signup_completed`
2. `first_order_placed`
3. `first_order_completed`
4. `repeat_order_placed` — especially the 2nd and 3rd orders, which are strong retention predictors
5. `order_cancelled`
6. `refund_requested`
7. `last_order_30_days_ago`
8. `last_order_60_days_ago`

Each of these events should trigger a SendGrid Automation or update a contact field that feeds into a segment.

---

Segments to Build

High-Priority Worker Segments

• Stuck in Onboarding: `onboarding_status = background_check_pending` AND `days_since_signup > 5`. These workers applied, hit friction, and went quiet. A targeted sequence explaining typical timelines and what to expect recovers 15–25% of this group in most markets.
• Approved But Inactive: `onboarding_status = approved` AND `first_job_complete = false` AND `days_since_approval > 3`. Approval is a high-intent moment. Three days of silence is a signal.
• At-Risk Active Workers: `days_since_last_job > 14` AND `lifetime_jobs > 5`. These are experienced workers drifting away, not new workers who never started. They respond to earnings-focused re-engagement, not tutorials.

High-Priority Customer Segments

• One-and-Done: `lifetime_orders = 1` AND `days_since_last_order > 7`. The drop-off between first and second order is where most marketplace retention strategies fail.
• Lapsing High-Value Customers: `lifetime_orders > 4` AND `days_since_last_order > 21`. These customers proved they liked your platform. Something changed.
• Post-Bad-Experience: `refund_requested = true` OR `order_cancelled = true` in the last 30 days. Do not ignore these. A well-timed recovery email with a concrete resolution offer converts at higher rates than standard win-back campaigns.

---

Automations to Build in SendGrid

Worker Onboarding Drip (8–12 Days)

This sequence runs from `worker_signup_completed` to `first_job_completed`. Structure it as:

1. Day 0 — Welcome + what to expect during background check. Include specific timeline (e.g., "Most checks complete in 3–5 business days").
2. Day 3 — Status check if background check is still pending. Acknowledge the wait, provide support link.
3. Day 1 post-approval — "You're approved" with a concrete first-job guide specific to your category (e.g., how to read a delivery route, how to price a home cleaning job).
4. Day 3 post-approval — Social proof email. Show average earnings in their city market for workers in their first 30 days.
5. Day 7 post-approval, no job taken — Urgency signal. Show current demand in their area using dynamic content blocks populated from your platform data.

Customer First-Order to Retention Sequence

The goal here is getting a customer from 1 order to 3 orders. Research across marketplace categories consistently shows that a customer who has placed 3 orders has 60–70% higher 12-month retention than a customer who has placed 1.

1. 1 hour post-first-order-complete — Thank you + how-it-works reinforcement. Keep it short.
2. Day 3 — Category recommendation email based on `preferred_category`. If they ordered home cleaning, show them handyman services. Cross-category exposure increases LTV.
3. Day 7, no second order — Soft re-engagement with a time-limited incentive. $5 off, not 50% off. Train customers on value, not discounts.
4. Day 14, no second order — Last-touch before moving to lapsed segment.

Worker Win-Back (At-Risk Active Workers)

Trigger: `days_since_last_job > 14` AND `lifetime_jobs > 5`

• Email 1: Personalized earnings summary — "In your first [X] jobs, you earned $[Y]." Frame it as momentum to recapture.
• Email 2 (Day 5): Market demand update for their city. Show that demand exists. Workers who drifted often did so due to perceived low availability, not lack of interest.
• Email 3 (Day 10): Direct ask with a low-friction re-entry point (e.g., "There are 12 jobs available near you this weekend").

---

Industry-Specific Deliverability Challenges

Gig economy platforms send at high volume across a wide geographic footprint. Three issues come up repeatedly:

Transactional email misclassification. Payment receipts and onboarding confirmations sometimes get flagged as promotional by Gmail because they contain incentive language. Audit your transactional templates and strip promotional copy. If you need to cross-sell, do it in a separate send.

Inconsistent worker engagement rates. Workers in saturated markets (urban centers) open emails at lower rates than workers in emerging markets. Segment by `city_market` and test send times separately for each cluster. A 10am send in Chicago is not the same as a 10am send in a smaller metro.

High churn creating list decay. Gig platforms see significant worker churn in the first 60 days. Suppress unengaged contacts (no open or click in 90 days) before they damage your sender score. Set this up as an automatic suppression rule in SendGrid.

---

Frequently Asked Questions

How should I handle workers who are also customers on my platform?

Tag them with both `user_type = worker` and `user_type = customer` using a multi-value field or two separate boolean fields. Keep them in separate lists and suppress customer promotional emails when they are in an active worker onboarding sequence. Mixing messaging types at critical activation moments reduces conversion on both sides.

What send volume justifies moving to SendGrid's dedicated IP?

If you are sending more than 100,000 emails per month consistently, a dedicated IP gives you full control over your sender reputation. Below that threshold, shared IPs with strong pool management perform adequately. When you do move to dedicated, warm the IP over 4–6 weeks by ramping volume 20–30% per week.

Can SendGrid handle real-time transactional triggers like job completion notifications?

Yes, via the SendGrid SMTP API or v3 Mail Send API. Job completion, payment received, and rating notifications should all be triggered programmatically from your backend, not from Marketing Campaigns automations. Marketing Campaigns is designed for scheduled and segment-based sends, not sub-minute latency transactional events.

How do I measure whether my worker onboarding sequence is actually working?

Track activation rate — the percentage of approved workers who complete their first job within 14 days — as your primary metric, not open rate. Pull this from your platform data and compare cohorts who entered the sequence against historical cohorts who did not. Open rate tells you the email got read. Activation rate tells you the sequence worked.