What we're doing & why

One unified 30-day sprint across both Temu apps and both affiliate programs — for Krishna and the team at a glance.

We're running a single go-to-market motion that unifies four Temu initiatives — Temu US affiliate, Temu UK affiliate, the Temu Importer app, and the custom Temu Connector app — into one funnel instead of four disconnected campaigns. The same seller is acquired onto Temu via the affiliate program, then adopts our app to run Temu from Shopify.

The hook is something no marketplace can match: sell on Temu at 0% commission, forever, for sellers onboarded through us — plus a free app trial.

The Power of Zero

Zero commission
0% Temu selling commission, ongoing, for sellers onboarded through us.

Zero to start
Free app trial — nothing upfront to get running.

Zero hassle
Import, sync inventory & price, manage orders from Shopify.

The goal (read this, Krishna)

Targets are anchored on real history, not optimism: prior cadences produced ~50 UK affiliate signups over 6–7 months (~8/month). The sprint's real job isn't a big number — it's to prove the 0% hook beats that historical run-rate. If it does, we scale; if not, we've spent 30 days, not another seven months.

~35

Affiliate onboards target (UK 8–12 · US 15–25)

~8/mo

Historical run-rate (the bar to beat)

~10+

App installs (scales with warm list)

5–12

App-store reviews (from 0 today)

Status

Plan ✓ approved-ready Content library ✓ drafted Zoho setup — pending 0% terms — confirm wording

Cadences send from Yashwita's handle · Campaigns send from Hrithik's handle.

Funnel & routing

The flow is one line: get them a Temu account first → then get them on the app. App adoption is the goal; the affiliate account is the step that creates an install candidate.

The engine (account-first): all US / UK / EU sellers → 1) onboard onto Temu via affiliate (0% hook) → 2) push the free Importer to run Temu from Shopify → 3) choose the app by intent (Importer to manage, Connector to create listings). Store installs aren't in CRM, so we drive + reconcile manually; we don't wait on install events that don't arrive.

The lifecycle spine

1 · Acquire

All US/UK/EU sellers not on Temu → affiliate, 0% hook. Get the account.

2 · Activate

On Temu → push the free Importer. Get the install = the goal.

3 · Expand

Tier upgrade / Connector cross-sell. Parked — needs order data.

4 · Advocate

Reviews, from 0. Manual for now.

Routing decision tree

Account first: are they on Temu? No → affiliate (US/UK/EU). Once on Temu → which app, by intent: manage existing = Importer; create listings = Connector. Unsure → default to Importer.

Targets & tracker

Your targeting funnel: DB cohorts → email → apply / onboard on Temu → install the app → adopt the marketplace. Edit the blue numbers and everything recomputes, split US / UK.

Who you're targeting: sellers in your DB who are not on Temu, active in the last 12 months, and using other apps. Put your real CRM counts in each cohort (the numbers below are examples to show how it works). Some will already be on Temu — they'll tell you when you email; the rest are who you convert.

1 · Your audience — DB cohorts

How many sellers in each. Replace with your CRM segment counts.

Cohort	US	UK
Paid on other apps
Shopify high-plan sellers
Other (not on Temu, last 12mo)

2 · Conversion rates

Email → want to apply (%)

Apply → onboarded on Temu (%)

Onboarded → app install (%)

Install → adopted / selling (%)

Your funnel

Stage	US	UK	Total
Addressable (DB, filtered)	—	—	—
Want to apply (email interest)	—	—	—
Onboarded on Temu	—	—	—
App installs — the goal	—	—	—
Adopted — selling on Temu	—	—	—

Reality check: last run made ~50 UK onboards in 6–7 months (~8/mo). If your funnel predicts far more, lower the rates until it feels honest.

Plan timeline & yield — when it started, what it yielded

The one place to record when each stage went live and what it produced. Fill in the date and the yield as you go — this is your running scorecard for Krishna.

Stage (in order)	Owner	Target
Campaigns — drive traffic	Hrithik	Clicks → CRM leads
1 · Affiliate onboard (US/UK/EU)	Yashwita	~35 onboards (8–12 UK · 15–25 US)
2 · Install-push (Importer)	Yashwita	App installs (north star)
Store follow-up (manual)	Yashwita	Welcome / win-back sent
Trial → paid	Yashwita	25–35% of activated
Reviews (manual)	Yashwita	5–12 seeded

Parked (needs order data): tier-upgrade Expand & usage-based reviews — run manually or once app events flow to CRM.

The full tracker (Excel)

Segments, 30-day calendar, cadence matrix, KPI dashboard and the parking lot live in the workbook. Host it alongside this page and the button works.

Download tracker (Excel)

Content library

Everything Yashwita needs to build campaigns — branching cadences, subjects, replies, campaigns, punchlines. Click any subject to copy it; use the Copy button on emails.

Where & how this plugs into Zoho

Subjects & Punchlines → building blocks. Drop into any email or campaign; rotate so no two sends share a subject.
Cadences (Affiliate, Activate, Expand, Advocate, Win-back) → set up as Zoho CRM email cadences from Yashwita's handle. Each step is timed and branches on behavior. The main sequence IS the no-response path — if a seller doesn't engage, they keep getting the next timed touch until they convert, opt out, or the sequence ends.
Campaigns → Zoho Campaigns broadcasts from Hrithik's handle to the wider US/UK pools. They feed qualified leads into the chatbot and Yashwita's cadences.
Reply templates → manual responses Yashwita sends the moment a lead replies (automation pauses).

Pick a cadence below to see its audience, trigger, timing, exit, and the full email sequence.

Build in Zoho

Step-by-step so the team can build this without hunting through Zoho docs. Two tools do the work: Zoho Campaigns (broadcasts) and Zoho CRM Cadences (nurture).

Build order (the engine): Campaigns drive traffic → Affiliate cadence gets US/UK/EU sellers a Temu account → Install-push cadence gets them onto the free Importer → app choice by intent. Store installs aren't in CRM, so the store welcome/uninstall/review templates are sent manually. Parked (needs order data): tier-upgrade Expand & usage-based reviews.

Which tool for what

Use…	For	Why
Zoho Campaigns (Hrithik)	The cold 15k US/UK pools — broadcast announcements	Built for bulk. Cadence emails count against CRM workflow-email limits, so don't pour 15k into a cadence — blast via Campaigns, then enroll the people who engage.
CRM Cadences (Yashwita)	Structured, branching nurture of enrolled/engaged leads	Zoho's own guidance: bulk = Campaigns, nurturing series = Cadences.
SalesIQ chatbot	Qualify & route website visitors	Asks the two questions, tags the lead, enrolls them in the right cadence.
In-app (minimal)	Only the review prompt & upgrade nudge	Limited customization — keep it light; everything else runs via email.

How CRM cadences actually work (read before building)

Key constraint: Zoho cadences branch on the previous email being Sent, Opened, Clicked, or Replied — there is no “Not Opened” trigger (confirmed in Zoho's docs). So the non-responder backbone is built on “N days after previous email = Sent”, which fires for everyone regardless of opens. Opens are unreliable anyway (Apple Mail auto-loads pixels), so lean on Sent (spine) + Clicked (engaged branch) + Replied (exit).

Condition in the builder	How we use it
Sent + delay	The backbone — every timed touch. This is the no-response path (15 touches for Affiliate).
Clicked	Engaged branch → send the high-intent “set it up with you” email.
Replied	Exit / un-enroll → Yashwita takes over manually (use Reply templates).
Opened	Optional only — unreliable, never the backbone.

Other rules baked in: one action per condition per follow-up · the cadence auto-stops when the lead converts or unsubscribes · sender is selectable (set Yashwita) · each email = a saved CRM email template.

Build a cadence (steps)

Setup → Automation → Cadences → Create Cadence. Module: Leads (or Contacts).
Enrollment: pick a Custom View (e.g. “US · Not on Temu · engaged”) for auto-enroll, or Manual for hand-picked leads.
First email = Enrollment step (“immediately after enrollment”). Pick the template (e.g. Temu Aff US — T1 Hook), set From = Yashwita.
Add each follow-up: “N days after previous email is Sent” → its template. Use the day-gaps shown on each email in the Content Library.
Add the engaged branch: “when previous email is Clicked” → the “set it up with you” template.
Set Un-enroll properties: on Replied, on Onboarded = Yes, and on Unsubscribe. Add an unsubscribe link in the template.
Publish. Keep a draft version for edits — editing a live cadence won't disrupt already-sent steps.

Build a campaign (Zoho Campaigns)

Campaigns → Email Campaigns → Create Campaign → Regular email. Name it.
Add Recipients → choose the mailing list / segment (US pool, UK pool).
Set From = Hrithik (verified sender).
Create Content → choose the Plain-text editor for deliverability (text-forward; one image max if any). Paste the campaign copy + subject + preheader.
Send now / Schedule / Stagger in batches. Then route everyone who clicks into CRM and enroll them in the matching cadence.

SalesIQ chatbot flow

SalesIQ → Bots → build a bot on the site / landing page. Greeting = a Power-of-Zero opener.
Q1: “Already selling on Temu?” — No → capture email, push to CRM as a Lead tagged region + “Not on Temu”, share the affiliate link, enroll in the Affiliate cadence.
Yes → Q2: “Create new listings, or manage what you sell?” — Manage → tag Importer-intent, send install link, enroll Activate. Create → tag create-intent (Connector) and route.
Each answer writes the lifecycle field so only one cadence owns the lead at a time.

Template naming convention

Name CRM templates so they match this library and the cadence references line up: Temu Aff US — T1 Hook, Temu Aff US — T2 Bump, … Temu Activate — Welcome, etc. Mirror for UK.