Positioning & ICP Review — April 2026¶
Purpose: Capture the corrected understanding of Husky Data's real business model, current constraints, and ICP — and surface the positioning decision that follows. Written after reviewing Feb 2026 Eyeota earnings report on 2026-04-20.
1. What we now know (facts, not positioning)¶
1.1 Two revenue models — only one is public¶
| Model | Public? | Revenue today | Catalog |
|---|---|---|---|
| Branded — Husky-named segments via Eyeota | Yes (site, IAB DTL app, AWS/Snowflake plan) | $0 in Feb 2026 (Partner-branded sheet empty) | 300 APAC segments in segments.json |
| Unbranded — signal contribution to Eyeota's pool (rebranded as Eyeota-branded segments) | No — operational, not customer-facing | $70,171 Net in Feb 2026 (via "UB_GLOBAL NEXT BUZZ MEDIA" supplier org) | ~1,800 segments across demos, B2B, verticals — Eyeota-named |
Implication: the site must reflect the branded business only. Exposing the 1,800-segment unbranded pipeline on the public site would conflate two different products and potentially breach the Eyeota supplier boundary.
1.2 The APAC framing is a constraint, not a strategy¶
- Husky did not choose to be APAC-only. Eyeota selected APAC as the initial scope for the branded partner initiative.
- All 300 segments currently tagged
region: Asiainsegments.jsonexist because that was Eyeota's chosen scope for the branded launch. - The underlying signal network spans 60+ countries with US Tier 1 by lifetime MAID depth (per internal analytics, see market-footprint.md).
- The APAC constraint is temporary — likely to persist only until Husky has independent distribution channels (AWS Data Exchange, Snowflake Marketplace) where Husky can list its own catalog without Eyeota curation.
1.3 Where unbranded revenue actually comes from (Feb 2026)¶
| Segment category | Net USD | % of month |
|---|---|---|
| Demographic — Age | $24,231 | 34.8% |
| B2B / Firmographic | $9,920 | 14.2% |
| Travel | $7,875 | 11.3% |
| Auto | $4,465 | 6.4% |
| Demographic — Income/Wealth | $3,072 | 4.4% |
| (other categories) | $20,121 | 28.9% |
| Total unbranded net | $69,684 | 100% |
Top-selling individual segments are generic age + B2B firmographic categories (Age 45-49 Declared, Medium-Small Employees, etc.), not APAC-specific. This is commercially significant but operationally opaque — not a story we tell customers.
1.4 Where customers discover Husky today¶
- Primarily through Eyeota marketplace (buyers already in Eyeota see Husky in branded APAC segment browse)
- Inbound via website
/contact(6 intent types, Telegram notify) - Not on AWS DX or Snowflake yet (planned, not applied)
2. Current ICP (branded product, today)¶
Given distribution is Eyeota-only and branded catalog is APAC-scoped, the realistic ICP at this stage:
Primary (best fit today)¶
- Global brands with APAC growth mandates, buying via Eyeota — targeting APAC consumers with APAC-native audience depth
- APAC-HQ agencies activating cross-market campaigns across 14 APAC markets
- Global DSPs / DMPs enriching their APAC audience inventory through Eyeota syndication
Secondary (fit today, smaller volume)¶
- APAC ecommerce brands wanting market-specific mobile audience depth
- Custom-segment clients with bespoke APAC briefs
NOT a fit today (by design or constraint)¶
- US brands targeting US consumers — we have no branded US catalog; they'd find Husky on Eyeota and be confused
- Purely demographic (age/gender) buyers — Eyeota's own catalog serves that; Husky's branded line is intent/interest-skewed
- Clean-room / identity-resolution seekers — not our product
3. Why a customer chooses Husky at this stage¶
Defensible reasons (real differentiators): 1. 14-market APAC-native signal (not global data with an APAC filter bolted on) 2. IAB Tech Lab Taxonomy 1.1 + Data Transparency Standard 1.2 compliant out of the box 3. Branded + IAB-mapped segments with declared Lifetime Days (procurement-ready) 4. Available inside Eyeota without onboarding a new vendor 5. Regulatory posture across 7 regimes (procurement unblocker)
Weak or absent reasons (gaps vs competitors): - Scale on global audience data (we don't sell global branded; Lotame / LiveRamp do) - US audience depth as a branded product (unbranded only today) - Self-serve procurement outside Eyeota (AWS/Snowflake not live) - Brand recognition (launch stage, zero paid marketing budget spent)
4. Positioning implications¶
4.1 The "APAC Mobile Audience Foundation" tagline — what it really means¶
Given the facts above, "APAC Mobile Audience Foundation" is accurate for the current branded product (the 300 APAC segments) — but it's:
- (a) A description of the current branded catalog, not the whole company
- (b) Constrained by Eyeota's choice of scope, not a strategic commitment
- (c) Likely to be revisited when AWS DX and Snowflake come online (Q3 2026 target)
4.2 What we should publicly claim today¶
Safe to claim: - 300 branded audience segments across 14 APAC markets - Distributed via Eyeota (part of Dun & Bradstreet Audience Solutions) - IAB Tech Lab Taxonomy 1.1 + Data Transparency Standard 1.2 - Husky Technology Pte Limited (Singapore HQ) + Husky Data Science Company Limited (Hong Kong) - 7-regime DSR portal, procurement-ready
Claimable but nuanced — surface carefully: - 350M MAIDs / 3.5B monthly signals — these are pipeline-level numbers including the unbranded contribution. If surfaced as "Husky branded reach," that's an overclaim. If surfaced as "underlying signal network scale," it's defensible but requires careful language. [CONFIRM with CEO] — are these branded-only or pipeline-total? - 14 markets — the branded catalog covers 13 APAC + the US is pipeline-only. The public site should either scope to 13 APAC markets OR explicitly separate branded coverage from signal-network scale.
Should NOT claim publicly: - 1,800+ unique audiences (that's the unbranded pipeline) - US as a primary market (no branded US catalog) - Revenue dominance in any region (exposes the unbranded contribution business) - "Global mobile audience data platform" (we don't sell globally-branded today)
4.3 Wiki corrections required¶
The following public-site changes I made in the last 24 hours need re-examination:
| Change | Issue | Corrective action |
|---|---|---|
| Methodology: market tiers showing US as Tier 1 | Leaks unbranded pipeline scale into public narrative | Remove US from market list OR scope page to branded catalog only |
| Methodology: "14 markets" including US | Inconsistent with branded catalog (13 APAC) | Decision: scope to 13 APAC OR separately disclose pipeline-vs-branded |
| Partners page "expansion targets AWS DX + Snowflake" | Unclear whether listings will be APAC-branded subset or broader | Clarify listing scope before publishing public commitments |
| Marketing plan — positioning section | Treats APAC as strategic choice | Update to reflect current-constraint framing + transition plan |
5. The transition plan — positioning over time¶
| Phase | Trigger | Positioning |
|---|---|---|
| Now (Q2 2026) | Current — only Eyeota-branded APAC channel | "The APAC Mobile Audience Foundation" — accurate for branded product |
| Q3 2026 (AWS DX listing live) | First branded segment live on AWS DX | Likely still APAC-focused on AWS; positioning unchanged if only APAC segments listed |
| Q4 2026 (Snowflake listing + broader catalog) | If Husky lists US-branded segments on AWS/Snowflake | Evolve positioning to "Mobile audience data platform with APAC-native depth and expanding global coverage" |
| 2027+ | If Husky-branded US catalog generates meaningful revenue | Reposition to company-level umbrella: "Global mobile audience data platform" |
Trigger for repositioning earlier than Q3 2026: if the Eyeota-branded-APAC constraint is lifted (Eyeota adds branded support for non-APAC segments, OR we launch direct-to-buyer channels ahead of AWS/Snowflake) — revisit.
6. Strategic decision framework for CEO¶
Three live options for public positioning, given the above:
Option A — Stay APAC-branded (recommended for Q2 2026)¶
- Hero, messaging, IAB DTL, AWS application all align on APAC
- Roll back the Methodology tier labels that exposed unbranded pipeline
- Scope market footprint to 13 APAC
- Trust page keeps US for regulatory coverage (CCPA) only
- Pros: honest to branded reality; aligned with current ICP; defensible in procurement; no customer confusion
- Cons: undersells underlying signal network; US buyers looking for Husky won't find themselves in the pitch
Option B — Public pivot to "Global with APAC depth" now¶
- Aligns with real internal scale
- Prepares for AWS/Snowflake expansion early
- Cons: overclaims branded product (US isn't branded yet); exposes unbranded business model; contract risk with Eyeota; competitive exposure to Lotame/LiveRamp
- Not recommended at this stage
Option C — Two-layer: "APAC brand today, broader tomorrow"¶
- Hero: "The APAC Mobile Audience Foundation"
- Tagline / sub-story: "Building the mobile audience data platform — APAC first, global next"
- Methodology: strictly branded-catalog story (13 APAC)
- Roadmap callout: AWS DX + Snowflake = "broader catalog coming"
- Pros: honest about both current state and trajectory; defends the wedge now; signals future
- Cons: "global next" is a commitment — need to actually deliver when AWS/Snowflake land
7. Open questions for CEO to answer¶
CEO began answering 2026-04-20 inline:
| # | Question | CEO answer (2026-04-20) | Impact |
|---|---|---|---|
| Q1 | 350M MAIDs / 3.5B signals — branded-catalog only, or pipeline total? | Branded-only. Overall pipeline is >1B MAIDs. | Existing numbers stay on public site. We don't reveal the larger pipeline figure. |
| Q2 | AWS DX + Snowflake: 300 APAC branded only, or broader Husky-branded catalog (rebrand of unbranded)? | Broader. Plan to list broader catalog as Husky-branded on new channels. | MASSIVE. Means public positioning should accommodate a broader catalog reveal when AWS/Snowflake go live. "APAC Mobile Audience Foundation" becomes wrong at AWS launch moment. |
| Q3 | Eyeota contract exclusivity on unbranded-rebrand? | No exclusivity. Eyeota has no control over Husky's own audience data usage. | Confirms Husky CAN rebrand broadly on AWS DX / Snowflake without contract risk. Unblocks Option C transitional framing. |
| Q4 | US branded coverage on 6-12 month roadmap? | Yes — and a clear focus. Historical success was US-based. US branded is on roadmap. Important caveat: must not dilute Eyeota brand on channels where Eyeota dominates (TTD, Google/DV360) — so channel strategy needs segmentation (Husky-branded on AWS DX + Snowflake; stay quiet on TTD/Google to protect Eyeota relationship). | Confirms Option C transitional framing. Adds channel-differentiation requirement — not all channels see the same Husky-branded story. |
| Q5 | Commercial target for 300 branded APAC segments in H2 2026? | No target — testing initiative. Not expected to match US revenue. | Major reframe: branded APAC is a low-stakes experiment, not a revenue engine. Means site positioning shouldn't over-commit to APAC (which would be anchored to a failing experiment if the test doesn't land). AWS/Snowflake broader catalog is the REAL commercial bet. |
| Q6 | Is Global Next Buzz Media Ltd the contracting entity with Eyeota? Legal relationship to Husky Technology Pte Limited? | GNB Media was the historical contracting entity. Actively migrating contracts from GNB → Husky Technology Pte Limited (Singapore). Reason: HK-based data companies face political sensitivity in current global climate (US–China tensions). SG entity is the new contracting + branded future. Deliberate brand reset — do NOT reuse "Next Buzz Media" name anywhere externally. Husky is a fresh brand. | Completely validates removing all NB Media mentions from public site (already done). Explains why HK entity matters less than SG HQ. Reinforces Singapore-first in public-facing copy. |
8. Recommended next actions¶
- Freeze public-site copy changes until Q4–Q6 are answered (Q1–Q3 now answered — Q2 answer means positioning SHOULD evolve at AWS/Snowflake launch, not stay APAC forever).
- Roll back Methodology US-Tier-1 labels — the branded catalog is 13 APAC only. Scope methodology page to branded reality.
- Update marketing plan section 2 to reflect APAC-as-constraint + broader-catalog launch at AWS/Snowflake.
- ~~Add this doc as authoritative reference in MEMORY.md index.~~ Done 2026-04-20.
- Draft new ADR — "ADR-0004: Public positioning roadmap — APAC today, broader at AWS/Snowflake launch" — once Q4–Q6 answered.
9. Direction emerging from Q1–Q3 answers¶
Given: - Q1: 350M/3.5B are branded-only (safe to keep on site) - Q2: AWS DX + Snowflake will carry broader Husky-branded catalog - Q3: No Eyeota exclusivity — rebranding unbranded as Husky is contractually OK
The Option C transitional framing is now the clear direction:
- Today (Q2 2026): "The APAC Mobile Audience Foundation" — accurate for current branded catalog on Eyeota
- Mid 2026 (pre-AWS launch): soften positioning to hint at broader coming — "APAC native, global expansion on AWS Data Exchange and Snowflake Marketplace coming 2026 H2"
- At AWS/Snowflake launch: evolve hero to "The Mobile Audience Data Platform · APAC-native, globally available"
- 2027+: potentially drop APAC qualifier entirely if US-branded revenue matures
This gives Husky the APAC wedge today (defensible differentiator), with a clean trajectory to broader positioning without a messy rebrand. Marketing doesn't need to over-commit to "APAC only forever" — it's a stage, not a destiny.
10. Singapore-first messaging requirement (from Q6)¶
CEO's Q6 answer reveals a critical constraint: the corporate identity is in active migration from Next Buzz Media Ltd (historically the Eyeota-contracting entity, HK-linked) to Husky Technology Pte Limited (Singapore-based). This is driven by:
- Political sensitivity — HK-based data companies face procurement pushback from US and EU buyers in the current US–China climate
- Brand reset — fresh Husky identity decoupled from the NB Media legacy
- Contracting clarity — future Husky-branded deals should execute under the Singapore entity
Public-site implications (already partially implemented 2026-04-19/20):
- ✓ Removed "Global Next Buzz Media Ltd" from site + schema + messaging (already done)
- ✓ Corporate attribution line updated to "Built in Singapore" (already done)
- Need to verify: HK entity
Husky Data Science Company Limitedpresence on public site - Currently on
/complianceLegal Entities as "Hong Kong (APAC operations)" - Question for CEO: should we de-emphasize or hide the HK entity given political sensitivity, and foreground Singapore even more?
- Options:
- (a) Keep both entities publicly disclosed — procurement transparency wins; HK is APAC ops, not data residency
- (b) Disclose only under NDA / on DPA request — if HK involvement raises buyer flags, avoid surfacing it in hero
- (c) Singapore-only public — treat HK as internal ops that doesn't need public mention
Recommendation: stay with (a) — transparent disclosure is defensible ("HK is APAC operations, Singapore is data residency + contracting"). But the messaging should always lead with Singapore. Double-check that current site doesn't mention HK before Singapore anywhere.
Data residency statement to consider adding to Trust page:
"Husky Data is processed and contracted under Husky Technology Pte Limited (Singapore). The Hong Kong entity (Husky Data Science Company Limited) supports APAC operational functions and does not hold primary data residency or contracting authority."
This preempts the "where's your data?" question.
Decision owner: Benjamin Wong (CEO). Draft author: Claude (Opus 4.7). Status: awaiting CEO answers to Q1–Q6 before committing to a public positioning direction.