05e — Email Marketing (v2 — Events-First Adjustments)

The Pixel Hues | Revised June 2026

v2 adjustment: Added WhatsApp Business as the primary Lane A outreach channel (event agencies live on WhatsApp). Email is now the secondary channel for Lane A and primary for Lane B+C (govt formal RFPs + RFP alerts).

A. Tooling

• Recommended: Brevo (formerly Sendinblue) Free / Starter tier — free for <300 emails/day, has automation workflows. ₹1.5K/mo Starter unlocks automation + landing pages.
• Alternative: Mailchimp Free (limited automations), ConvertKit (free <1K subs), Instantly.ai for cold outreach (separate).
• Why Brevo over HubSpot here: Free tier is more generous for India-based senders; integrates well with WordPress via plugin.

B. List Architecture

Total target subscribers (12-mo): ~3,300.

C. Welcome Sequence (7-email, for any new opt-in)

Email 1 (immediate) — Confirmation + delivery

Subject: Your [Buyer's Guide / ROI Calculator] is here + what to read first
Body: Deliver lead magnet. Set expectation: 1 email/week with sharp immersive-tech insights. Sign off: Ajay.

Email 2 (Day 2) — Founder POV

Subject: Why we built Pixel Hues (3 minutes)
Body: Ajay's founder story, what they care about. CTA: Reply with what you do.

Email 3 (Day 4) — Flagship case study

Subject: How we projected a BMW onto a 30m façade
Body: BMW case study, with visuals. CTA: See all case studies.

Email 4 (Day 7) — Free resource

Subject: The 2026 India Immersive Tech Buyer's Guide
Body: Cross-sell the whitepaper.

Email 5 (Day 10) — Social proof

Subject: What [client X] said about working with us
Body: Testimonial / quote / short case.

Email 6 (Day 14) — Soft pitch

Subject: "Are you planning an immersive install in the next 12 months?"
Body: One-question survey + soft CTA for a 30-min consult.

Email 7 (Day 21) — Calendar link

Subject: Book a 30-min consult (no pitch, just ideas)
Body: Calendar link. Sign off: Ajay.

D. Cold Outreach Sequences

Sequence A — AV Integrator (Channel Partner)

5 emails over 14 days.

• E1 (Day 1): Subject: "Quick question on partner motion"

  Hi [First Name], noticed [Integrator] has been winning the [venue / sector] AV scope in [geo]. We design + build the immersive-content layer (projection mapping, interactive installations, museum exhibits) and partner with integrators who want to extend their scope. We did [recent project]. Worth a 15-min call to compare notes? — Ajay

• E2 (Day 3): Subject: "Re: Quick question on partner motion — case study attached"

  Hi [First Name], in case useful — attached is our [BMW / HCL] case study. Happy to share the technical breakdown (projector model, pixel count, content pipeline) if it would help on your next bid.

• E3 (Day 7): Subject: "How we split revenue on partnered projects"

  Hi [First Name], quick one — when we partner with an AV integrator, we do a 70/30 (integrator/content) revenue split on the immersive-content scope. We bring the design, content, and install. You bring the integrator relationship and AV scope. Works smoothly.

• E4 (Day 12): Subject: "Re: How we split revenue — partner deck attached"

  Hi [First Name], sharing the one-page partner programme we use. No pressure — if there's a project on the horizon, would love to be in your back pocket.

• E5 (Day 14): Subject: "Closing the loop"

  Hi [First Name], I'll assume the timing's off and stop here. If a museum / corporate / airport project crosses your desk in the next 6 months where you'd want a creative-tech partner, my line's open. — Ajay

Sequence B — Museum Director

5 emails over 18 days.

• E1 (Day 1): Subject: "Saw the [Museum Name] [exhibition name] — quick idea"
• E2 (Day 4): Subject: "Re: Saw [exhibition] — what ASI's ₹1,481 Cr means for you"
• E3 (Day 9): Subject: "3 museums that modernised and what footfall did"
• E4 (Day 14): Subject: "Discovery doc attached (10 questions to scope your interactive exhibit)"
• E5 (Day 18): Subject: "Closing the loop"

Sequence C — Corporate Experience Centre Head

5 emails over 14 days.

• E1 (Day 1): Subject: "Loved what [Company] did with [specific centre or refresh]"
• E2 (Day 4): Subject: "Re: Loved what you did — here's a 3-min case study"
• E3 (Day 8): Subject: "ROI of a corporate experience centre refresh (data from 7 projects)"
• E4 (Day 12): Subject: "Discovery doc + 30-min calendar"
• E5 (Day 14): Subject: "Closing the loop"

E. Newsletter (Bi-weekly)

Format: Plain text + 3 visuals, ~400 words.

Sections:
1. One project update (case study or install).
2. One technical tip (Alok's POV on projection / interactive tech).
3. One industry news reaction (relevant tender, award, or sector shift).
4. One job / partnership ask (we're hiring X / seeking Y partner).
5. One CTA (download the latest guide / book a call).

F. Re-Engagement Sequence (for leads that go quiet)

• Trigger: No engagement for 90 days.
• Sequence: 3 emails over 10 days.
• E1: Subject: "Still thinking about the [museum/corporate/...] project?"
• E2 (Day 5): Subject: "What changed in immersive tech in the last 3 months"
• E3 (Day 10): Subject: "Should I close your file?"
• Result: Either re-engagement or mark as cold / clean list.

G. Compliance & Deliverability

• Sender domain: Use a custom subdomain (mail.pixelhues.com or hello.thepixelhues.com). Improves deliverability.
• Authentication: SPF + DKIM + DMARC records configured at DNS.
• Consent: Only email opted-in contacts; cold outreach via Instantly.ai (separate sending).
• Suppression list: Honor all unsubscribes within 24h.
• Bounce management: Auto-clean hard bounces.
• Frequency cap: Max 1 email/week per subscriber.

Next: 05f_pr_strategy.md

H. v2 ADDITIONS — Event-Agency Sequences

Sequence Lane-A-1 — Event Agency Founder (WhatsApp + Email)

Channel: WhatsApp first, then email if they don't engage.

• WA #1 (Day 1, WhatsApp): "Hi [Name], this is Ajay from Pixel Hues in Delhi. We do immersive tech for event agencies. Saw your work on [event]. Worth a 15-min call?"
• E1 (Day 2, email): Subject: "Quick question on immersive-tech partner motion"

  Hi [Name], following up on my WhatsApp. We design + build the immersive-tech layer for event agencies — projection mapping, interactive installations, hologram, content production. We did [BMW / HCL / Whirlpool]. Worth a 15-min call this week? — Ajay

• WA #2 (Day 5, WhatsApp): "Hey [Name], one more follow-up — sharing our partner programme 1-pager. 10–30% off standard rates based on volume. Worth a chat?"
• E2 (Day 8, email): Subject: "Re: Quick question on immersive-tech — case study"

  Hi [Name], attached is our [BMW / HCL] case study. If you have an event brief on the horizon where you'd want a creative-tech partner, I'd love to be in your back pocket.

• E3 (Day 14, email): Subject: "How we split scope on partnered events"

  Hi [Name], quick one — when we partner with an event agency, we own concept + tech + install + on-site run. The agency owns brand relationship + overall event. Clean.

• E4 (Day 18, email): Subject: "Re: How we split scope — partner programme attached"

  Sharing the partner programme 1-pager. No pressure.

• E5 (Day 21, email): Subject: "Closing the loop"

  Assuming timing's off. Can I check back in next month? — Ajay

Sequence Lane-A-2 — Brand-Side Activation Lead (NEW — Lane A direct)

5 emails over 14 days.

• E1 (Day 1): Subject: "Saw [Brand] at [Event] — immersive angle you might like"
• E2 (Day 4): Subject: "Re: Saw [Brand] — here's a 3-min case study"
• E3 (Day 8): Subject: "Why brand-side teams hire us directly (skip the agency layer)"
• E4 (Day 12): Subject: "Discovery doc + 30-min calendar"
• E5 (Day 14): Subject: "Closing the loop"

Sequence Lane-A-3 — Creative Director (NEW — Lane A, secondary)

5 emails over 14 days.

• E1 (Day 1): Subject: "Saw your concept for [event] — quick tech idea"
• E2 (Day 4): Subject: "Re: Saw [event] — here's a Pixel Mapper teaser"
• E3 (Day 8): Subject: "How our install timeline works for tight event dates"
• E4 (Day 12): Subject: "Discovery doc + 30-min calendar"
• E5 (Day 14): Subject: "Closing the loop"

Sequence Lane-B/C — Government (post-ISO)

5 emails over 18 days, formal tone. Use v1 Sequence B above (Museum Director) — still valid.