Husky Data Marketing Plan — 2026 H2¶
Status: Draft v1 — for CEO review Author: Consolidated from brand + website + launch work to date Owner: Benjamin Wong (CEO) Horizon: May 2026 → Oct 2026 (6 months), with 12-month view
This plan is opinionated. Where assumptions need your confirmation, they are marked [CONFIRM]. Where I flag a risk you should weigh, it's marked [RISK].
0. TL;DR (1-page)¶
Positioning: The APAC Mobile Audience Foundation. 14 markets, 350M MAIDs, IAB-mapped, procurement-ready.
Primary motion: Distribution-led GTM. Today's live distribution is Eyeota (part of Dun & Bradstreet Audience Solutions). 2026 H2 expansion targets: AWS Data Exchange and Snowflake Marketplace. Every marketing activity amplifies or supports these moments.
Important correction (2026-04-19): earlier drafts of this plan treated D&B as a second partner separate from Eyeota. They are the same corporate entity — Eyeota was acquired by Dun & Bradstreet in 2021 and operates as part of D&B Audience Solutions. The live marketplace surface is Eyeota; the D&B brand is relevant only as parent-company context. Don't double-count.
Secondary motion: Inbound-to-Telegram sales flow via website. Already wired.
Defer: Paid advertising, thought-leadership blog, events. Not launch-critical.
6-month focus areas (ranked): 1. Procurement enablement — Trust/Compliance page, DPA pack, regulatory matrix 2. Marketplace launch amplification — PR + LinkedIn stagger per launch 3. Methodology credibility — one deep page + IAB transparency explainer 4. Sales collateral — vertical one-pagers for top 5 verticals, segment catalog PDF 5. Partner co-marketing — each distributor has content slots; claim them
The bet: In APAC data, procurement moves before marketing does. Buyers pick you from a marketplace because the DPA clears legal, the taxonomy maps, and the lineage is defensible. Marketing removes friction from a purchase decision procurement already validated — it doesn't manufacture demand.
1. Market Context¶
Tailwinds: - APAC programmatic ad spend growing fastest globally; global advertisers need APAC-native audience depth they can't source from US-centric providers. - Cookie deprecation is extending MAID-resilient providers' runway in mobile-first APAC markets. - Privacy regime fragmentation (GDPR / CCPA / PDPA-SG / PDPA-TH / DPDP / Privacy Act AU) raises the procurement bar — rewards providers who already cleared it. - IAB Tech Lab standards (Taxonomy 1.1, Data Transparency 1.2) are becoming de-facto procurement checkboxes.
Headwinds: - Consolidation of audience data buying under a handful of DSPs — distribution gates are narrowing. - Lotame, LiveRamp, and regional incumbents have deeper brand equity. - Marketplace ecosystem revenue share models compress margins vs. direct sales.
Strategic read: We're in a 12–18 month window where APAC-native depth + IAB compliance + marketplace distribution is a specific, defensible wedge. After that, either consolidators absorb the category or regulation reshapes it. Move now.
2. Positioning & Competitive Frame¶
Core claim: The APAC Mobile Audience Foundation.
Supporting pillars (from messaging.js):
1. APAC-Native Methodology
2. Flexible Procurement
3. Custom Segment Builds
4. IAB-Compliant Transparency
Who we are: - 14-market APAC native provider - 350M MAIDs, 3.5B monthly behavioral signals - Branded audience segments with IAB Taxonomy 1.1 mapping - Distribution across 40+ platforms through marketplace partners
Who we are NOT (important — reduces positioning noise): - ✗ Global panel data provider (Nielsen, GWI) — we're signal-based, not survey - ✗ Identity resolution service (LiveRamp, ID5) — we sell audiences, not graphs - ✗ PII processor — no names, emails, phones, government IDs - ✗ First-party data custodian — we enrich; we don't hold the relationship - ✗ Generalist global provider — APAC is the whole company, not a region
Competitive frame:
| Competitor | Their strength | Our counter |
|---|---|---|
| Lotame | Global scale, DSP integrations | APAC depth + marketplace breadth + IAB transparency |
| Eyeota (as source) | Incumbent APAC footprint | We distribute through Eyeota but also 3 other marketplaces |
| Cross Mobile Audience | APAC mobile specialty | Multi-vertical coverage, IAB 1.1 mapping, procurement-ready compliance |
| First-party/clean room providers (LiveRamp, Habu) | Identity resolution | Audiences don't require customer data; we ship activation-ready segments |
[CONFIRM] Is Cross Mobile Audience actually a competitor we see in deals, or did I overweight them? Swap in whoever you see in pitches.
3. ICP & Buyer Personas¶
Primary ICP: - Global brands with APAC growth mandates (auto, finance, travel, CPG, tech) - Regional agencies with APAC HQ activating cross-market campaigns - DSPs/DMPs/CDPs sourcing APAC audiences for their buyers
Secondary ICP: - APAC ecommerce marketplaces and retailers - Telco-adjacent data consortia - Enterprise analytics teams loading APAC signals into Snowflake
Personas (who does what in a deal):
| Persona | What they care about | What we give them |
|---|---|---|
| Programmatic trader | Scale, lift, CPM, platform reachability | Segment catalog, reach estimates, platform list |
| Strategic planner | Segment definitions, insight, audience sizing | Methodology page, vertical one-pagers |
| Procurement / legal | IAB membership, DPA, regulatory posture, data lineage | Trust page, DPA pack, regulatory matrix |
| Data engineer (marketplace) | Schema, refresh cadence, taxonomy | Methodology page, AWS DX + Snowflake listings |
| CEO / VP Marketing (champion) | Differentiation story, competitive edge | Website narrative, case-study collateral |
Deal shape: Procurement + data engineer gate; strategic planner champions; trader activates. Marketing content needs to unblock all three.
4. Go-To-Market Motion¶
Primary channel — Distribution-led: Marketplaces reach buyers where they already shop. We trade margin for reach and procurement pre-clearance.
| Marketplace | Audience | Our lever |
|---|---|---|
| Eyeota | Global agencies sourcing APAC audiences | Branded segment exclusives |
| AWS Data Exchange | Cloud-native data buyers, analytics teams | Snowflake/Redshift-ready delivery |
| Snowflake Marketplace | Data-warehouse-first buyers | Native Snowflake schema, zero-copy activation |
Secondary channel — Direct: - Inbound: website → contact form (6 intent types) → Telegram instant notify → sales reply - Outbound: CEO LinkedIn + whatever sales headcount we have [CONFIRM headcount] - Partner referrals: warm intros from NB Media network
Tertiary — Custom segment builds:
- Bespoke briefs → custom segment → higher margin, deeper account
- Already a core pillar in messaging; needs a dedicated intake process (contact form interest=custom already wired)
Channel prioritization for H2 2026: 1. Marketplace launches (80% of marketing effort) 2. Direct inbound optimization (15%) 3. Partner co-marketing asks (5%)
5. Messaging Architecture¶
Already in place (src/content/messaging.js V3):
- Hero messaging
- Proof stacks (350M / 3.5B / 14 / 40+)
- 4 value pillars
- Corporate attribution (NB Media parent)
Gaps to close:
- Competitive one-liners — "Why not Lotame?" / "Why not just Eyeota direct?" — sales needs these
- Vertical narratives — Auto, Finance, Travel, Retail, Tech (top 5 by branded segment count from segments.json)
- Objection handling — "You're small" / "You're new" / "Why trust APAC-only?" → a slide or page per objection
[CONFIRM] What objections do you hear most in sales calls? Prioritize messaging against those.
6. Channel Strategy¶
Owned¶
- Website (huskydata.io): launched on Cloudflare Pages. Priority adds: Trust/Compliance page, Partners page, Methodology page, Newsroom scaffolding.
- LinkedIn (@huskydata): underutilized [CONFIRM follower count]. CEO personal + company page should post in tandem around each marketplace launch.
- Telegram lead flow: already instrumented; CEO gets instant pings.
Earned¶
- Industry trade press: AdExchanger, The Drum, Campaign Asia, Mumbrella APAC, ExchangeWire.
- Pitch angle: APAC audience data category maturation via marketplace distribution.
- Cadence: one earned placement per marketplace launch (4 total).
- Podcast / speaker slots: Campaign Asia, AdTech APAC, MarTech Asia. Low effort per appearance, high compound value.
Paid — deprioritize¶
- Skip for now. ROI unclear, team bandwidth low, organic channels not yet saturated.
- Revisit Q4 2026 once launch dust settles and we have attribution data.
Partner co-marketing¶
- Eyeota: webinar slot, marketplace spotlight, co-branded PR.
- D&B Audience Solutions (via Eyeota): newsletter inclusion, quarterly partner spotlight — leverage the D&B parent brand where it helps with enterprise procurement.
- AWS: launch blog post on AWS Data Exchange blog, partner solution brief.
- Snowflake: Snowflake Marketplace newsletter, Data Cloud Summit 2026 pitch [CONFIRM dates].
Ask-for-each-partner checklist (chase at launch): - Joint press release - Partner blog post - Newsletter inclusion - Co-branded one-pager - Event panel slot
7. Launch Sequencing (The Spine)¶
Four marketplace launches are the 2026 H2 story. Stagger ~4 weeks apart so each gets its own news cycle — no overlap, no dilution.
[CONFIRM] Actual launch dates per marketplace — the spacing above assumes you have some flex on timing.
Playbook per launch (repeatable):
T-14 days: - Draft press release (internal + partner alignment) - Brief partner PR contact - Prepare LinkedIn announcement posts (company + CEO) - Update website Partners page + Newsroom post - Brief sales team on talking points
T-0 (launch day): - Press release distribution (wire service or partner-owned) - LinkedIn posts go live (company → CEO reshare) - Email announcement to prospect list - Newsroom post live on website - Update Home page launch ticker/banner
T+7 days: - Partner co-marketing asks delivered (webinar, newsletter, blog) - Earned media follow-ups
T+30 days: - Launch retrospective: sessions, leads, deals influenced - Case study attempt (first customer who signed via marketplace)
8. Content Plan (90-day)¶
Month 1 (May) — Launch-stabilize: - [ ] Trust & Compliance page - [ ] Partners page - [ ] Newsroom scaffolding + L1 launch post - [ ] Company one-pager PDF - [ ] LinkedIn cadence set (CEO 1 post/week, company 2/week)
Month 2 (June) — Credibility build: - [ ] Methodology page - [ ] IAB compliance transparency explainer (LinkedIn + blog-style page) - [ ] First vertical one-pager (Auto — highest branded coverage [CONFIRM]) - [ ] Eyeota seasonal catalog refresh post (marketing moment, not a new-partner launch)
Month 3 (July) — Demand enablement:
- [ ] Vertical one-pagers × 3 (Finance, Travel, Retail)
- [ ] Segment catalog PDF export (from segments.json)
- [ ] Sales objection-handling brief (internal)
- [ ] Speaking slot pitch: Campaign Asia / AdTech APAC
Month 4–6 (Aug–Oct): - [ ] L3 launch (AWS DX) + partner webinar - [ ] Remaining vertical one-pagers - [ ] First case study (if any customer agrees) - [ ] L4 launch (Snowflake) + Data Cloud Summit pitch - [ ] 2027 H1 plan drafted
9. Sales Enablement¶
Already in place: - Contact form with 6 intent routing - Telegram instant notify - Opt-out / DSR portal (procurement trust signal) - 300 branded segment catalog
Gaps to close (priority order):
1. Company one-pager (PDF) — for outbound email attachments, event handouts
2. Standard DPA template — procurement unblocker; legal drafts once, sales sends forever
3. Segment catalog PDF export — for buyers who want to review offline
4. Pricing sheet (tiered or volume-based) — [CONFIRM] are you ready to standardize pricing or stay custom per deal?
5. Vertical one-pagers × 5 — top branded verticals
6. Competitive battle card — internal only; sales reference for "why not X"
7. Custom-segment intake form — expanded /contact?interest=custom with brief template
[RISK] Standardizing pricing too early locks in margins. Staying fully custom scales poorly. Middle ground: published "starting at" pricing, custom quotes on volume.
10. Metrics & Targets¶
Leading indicators (weekly review)¶
- Website sessions (GA4) — segmented by page, source, landing
- Contact form submissions — by intent type
- LinkedIn engagement — impressions, followers, post engagement rate
- Marketplace listing views — where available per partner
Conversion indicators (monthly review)¶
- Qualified leads (sales-accepted)
- Demo requests → first meeting held
- Vertical one-pager downloads (if gated)
- Newsroom post reach
Lagging indicators (quarterly review)¶
- Pipeline created (value + count)
- Closed-won revenue
- Marketplace-sourced deals vs. direct
- Segments licensed per deal (upsell indicator)
- Net revenue retention (once we have repeat customers)
North Star¶
Qualified inbound from marketplace-originated leads per month. This single metric validates whether the distribution-led thesis is working.
Targets for H2 2026 — set by CEO with sales:
| Metric | Jul target | Oct target |
|---|---|---|
| Website sessions/mo | [CONFIRM] | [CONFIRM] |
| Qualified leads/mo | [CONFIRM] | [CONFIRM] |
| Marketplace-sourced deals | ≥ 1 | ≥ 5 |
| Pipeline value | [CONFIRM] | [CONFIRM] |
11. Resource Requirements¶
Current assumed state: CEO + small team, minimal dedicated marketing headcount.
Role coverage needed:
| Role | Who owns it now | Ideal state |
|---|---|---|
| Strategic comms, LinkedIn thought leadership, press | CEO | CEO + fractional PR |
| Website content, SEO, newsroom | CEO (unsustainable) | Marketing ops hire or agency |
| Content production (vertical one-pagers, collateral) | CEO + freelancers? | Fractional content specialist or contractor |
| Partner co-marketing coordination | CEO | Marketing lead once hired |
| Sales response (inbound) | CEO (unsustainable post-launch) | Sales hire by end of Q3 |
Budget envelope — rough shapes (annualized): - Fractional PR agency: $2–5k/mo (APAC trade-press specialist) - Marketing ops / content lead hire: $80–120k/yr (SG/HK market rate) - Paid media (optional, defer): $1–3k/mo LinkedIn - Events/travel (APAC conferences): $10–15k/yr - Tool stack (analytics, email, design): $500/mo
[CONFIRM] What's the actual budget envelope for H2 2026? Everything above scales to whatever you allocate.
12. Risks & Open Questions¶
Strategic risks¶
-
[RISK] Marketplace launches slip. If one or more marketplaces delay, the launch-sequenced plan loses its spine. Mitigation: have one evergreen content thread (methodology, trust) that runs independently so momentum doesn't die.
-
[RISK] Competitive response from incumbents. If Lotame or LiveRamp announce an APAC push, we lose the "APAC-native" narrative air. Mitigation: lean harder into "14-market native from day one" and IAB compliance depth — table stakes they can't retrofit quickly.
-
[RISK] Parent company (NB Media) entanglement. Messaging currently positions Husky as independent with NB attribution. If NB faces PR or regulatory issues, blowback affects us. Mitigation: keep corporate attribution minimal; ensure Husky's own legal/compliance story stands alone.
-
[RISK] Regulatory tightening (GDPR / DPDP enforcement). Procurement bar rises — which is a tailwind if we're ahead, a cliff if we're not. Mitigation: Trust page + DPA pack + IAB transparency are the moat. Don't skimp.
-
[RISK] Team bandwidth. CEO doing this alone is unsustainable past launch. Mitigation: hire or contract before bandwidth breaks, not after.
Open questions for you¶
- Q1 — What's the H2 2026 marketing budget envelope?
- Q2 — Any hiring plans (marketing / sales) confirmed for H2?
- Q3 — NB Media relationship: can we leverage their PR/comms or are we standalone?
- Q4 — Customer references: any signed or implicit we can legitimately reference? Logos with permission?
- Q5 — Awards / certifications in progress I should factor in (SOC 2, ISO 27001, industry awards)?
- Q6 — Actual marketplace launch dates per partner (for scheduling)?
- Q7 — Pricing posture: standardize with published "starting at" or stay fully custom?
- Q8 — Sales headcount: who answers the Telegram ping at 2am Jakarta time when a lead lands?
13. 180-Day Rollup¶
| Month | Launch | Website | Content | Sales enablement |
|---|---|---|---|---|
| May | Eyeota (L1) | Trust page | L1 newsroom post, CEO LinkedIn ramp | Company one-pager |
| Jun | Eyeota catalog refresh | Partners page | Eyeota refresh post, methodology teaser | DPA template |
| Jul | — | Methodology page | Vertical 1-pager × 1 (Auto), IAB explainer | Segment catalog PDF |
| Aug | AWS DX (L3) | Newsroom expansion | L3 newsroom, vertical 1-pagers × 2 | Competitive battle card |
| Sep | — | Case study template | First case study (if available) | Custom segment intake |
| Oct | Snowflake (L4) | 2027 plan | L4 newsroom, 2027 preview | Pricing sheet |
14. What this plan is NOT¶
- Not a brand plan. Brand emerges from consistent execution; this is execution.
- Not a product roadmap. Segment expansion, new verticals, platform additions = product's lane.
- Not a PR plan in isolation. PR supports launches; launches drive the plan.
- Not aspirational. Every line item maps to a real asset, a real partner, or a real procurement blocker.
15. Decisions needed from you before execution¶
In order of blocking impact:
- Budget envelope (Q1) — determines hiring vs. agency vs. DIY
- Launch dates per marketplace (Q6) — sets the entire calendar
- Pricing posture (Q7) — unblocks sales collateral
- Headcount plan (Q2, Q8) — determines what CEO does vs. delegates
- Customer references (Q4) — unblocks case study pipeline
- NB Media leverage (Q3) — affects PR strategy
- Awards/certs in flight (Q5) — affects Trust page content
Get me answers to Q1, Q2, Q6, Q8 and I can sharpen this from plan to executable roadmap with real targets.
End of plan. Revisions welcome — strike, redline, or comment inline.