--- title: "Talex Positioning & Messaging" type: concept tags: [positioning, messaging, brand, ICP, copywriting] sources: [imported-from-conversations] created: 2026-04-13 updated: 2026-04-13 --- # Talex Positioning & Messaging Source: Q2 Marketing Plan (April 3, 2026), Copy Master Document, Moat V5.3. --- ## 2026 External Position > ⚠️ Updated 2026-06-29 — supersedes framing 12/06 (source: [[2026-06-29-evolved-odc-framework]]): > **"Evolved ODC — The development centre you virtually own from day one"** > Keyword pháp lý bắt buộc: "virtually own" (VN không cấp EOR cho IT, nhân sự ký với Talex không phải khách). > 4 levels: (1) Remote + client culture, (2) Client infrastructure, (3) Dedicated office (open-book), (4) Transfer-ready (2 năm, fee 1 tháng). > Talex = babysitter + facilitator, không phải outsourcer. Cung cấp: sourcing, HR/payroll, team governance (AM + Fingertips), legal compliance. > KHÔNG BAO GIỜ nói "EOR" hoặc "nhân sự thuộc về bạn". LUÔN nói "virtually own your team". > Xem chi tiết: [[2026-06-29-evolved-odc-framework]] > ⚠️ Scoped 2026-07-13 — Hailee correction (talex.co SEO copy task, this session): > **"Virtually own" là INTERNAL / sales-conversation language, KHÔNG dùng trong external SEO/web copy.** > Public-facing copy (website title/meta, SEO, LinkedIn, ads) dùng ngôn ngữ đơn giản hơn: "own your dev team", "build offshore like in-house", "full control from day one", "your culture, your process, your IP" — không có chữ "virtually". > "Virtually own" vẫn đúng cho sales deck/proposal/1:1 conversation với buyer — chỉ loại khỏi public web/SEO copy. > Vẫn giữ nguyên: tránh "outsource/outsourcing" như claim tích cực, tránh banned words (staff augmentation, seamless, flexible, fast/speed, talent marketplace). > ⚠️ Superseded 2026-06-12 (source: [[2026-06-12-weekly-update-odc-pivot]]): > ~~"Private ODC operator — The only ODC you own from day one"~~ > Client owns headcount, infra, culture from day 1. Talex = operator only. Staff augmentation không còn là sản phẩm. Daily rate thay monthly rate. **"Extended delivery arm"** — Talex is not a staffing vendor, not a talent marketplace. It is the operator that sits between the SI firm and the engineering team, providing governance and information continuity. > ⚠️ Updated 2026-04-21 — Thông điệp external mới được xác nhận từ [[2026-04-21-secondtalent-competitive-framing]]: > **"Scaling Machine cho SI"** — sẽ là headline message khi rebuild website talex.co. "Extended delivery arm" vẫn dùng trong nội bộ/conversation với SI buyer; "Scaling Machine" là external brand statement. Governance Moat là proof point bên dưới cả hai framing. Roadmap: 2027+ internal target = "delivery intelligence layer" once data accumulates. This is **not public in 2026**. --- ## ICP — Ideal Customer Profile ### Primary Buyer (LinkedIn target) - **Title**: Head of Delivery, CTO, COO - **Company**: Singapore fintech and IT consulting firms - **Size**: 51–200 headcount - **Situation**: Managing extended engineering teams or preparing to expand - **Role**: Decision-maker, not procurement ### Buyer Segments by Moment | Moment | Situation | Content Angle | |---|---|---| | **Just lost someone** | Mid-project exit or bad hire. Asking why it happened. | Reframe: governance/information problem, not talent problem. Do not offer the solution — let the pain land. | | **Hiring in AI era** | Reviewing CVs. Every candidate claims "uses AI." | Distinguish three real tiers via observable behavior. Give them a self-assessment tool, not a Talex pitch. | | **Managing blind** | Project running, low-grade anxiety, no real visibility into team morale or blockers. | Articulate the information asymmetry: both sides manage an incomplete version of reality. Do not offer solution. | Source: Moat V5.3 §01 (PAM), §02 (Assessment Intelligence). Meeting 25/3 (Kiên × Hà × Khôi) framed three pain points: tuyển sai (wrong hire), tuyển chậm (slow hire), người bỏ giữa chừng (mid-project exit). --- ## Brand Voice — Rules ### What Talex writes like - An **operator with real track record** reporting what they see in the field — not a vendor pitching. - Standard: Kiên's About section — calm, factual, no large claims, no hype. - Short sentences. No em dash. No parallel three-part structure. ### By surface: - **Client-facing (Portal, Playground)**: No "Talex" branding — fully whitelabeled. Tone: professional, action-oriented, C-level readable. - **LinkedIn (Talex Main EN)**: Voice of someone observing from inside the field. Not marketing hype. Not educational lecturing. Zero mention of Talex in April 2026. ### Kiên's personal page style (reference standard) From Kiên Tran's April 1, 2026 LinkedIn post, five patterns to apply to the Talex page: 1. Specific client situation — "A client came to us after losing a project..." (not abstract) 2. Counter-intuitive fact, stated quietly — "Good engineers. The project failed anyway." (let the fact speak) 3. Short closing line that hangs — "The wrong hire is not a setback. It is the project." (no further explanation) 4. Talex mentioned only as context, not as subject — "A client came to us" (not "at Talex we see...") 5. No hashtags, no CTA, no emoji — confidence through restraint --- ## Tone of Voice — 6 Rules (LinkedIn) 1. **Observer, not vendor.** Write from inside the field, not from behind a sales desk. "A client came to us" not "at Talex, we see this often." In April: no "we," no "Talex." 2. **Fact first, not emotion.** Hook with a real fact or specific situation — not "Hot take:" or "Unpopular opinion:" 3. **Counter-intuitive without shouting.** Let the fact do the work. "In a two-person AI-augmented team, the wrong hire is not a setback. It is the project." Nothing more needed. 4. **No moral conclusion.** End at the last fact, not at wisdom. No "the lesson here is..." No "remember that..." Let it hang. 5. **Short sentences. Short paragraphs.** 1–3 sentences per paragraph. Blank line between. No wall of text. No parallel three-part structure. No em dash. 6. **Zero mention of Talex in April 2026.** Zero. Not "we at Talex," not "in our experience at Talex," not a link to talex.co. Write as an independent observer sharing what they see in the field. --- > ⚠️ Updated 2026-05-12 — Full copy ruleset (capitalization, char limits, status labels, CTA hierarchy, cross-platform conflicts) đã được chốt và document tại [[copy-system]]. Positioning concept này vẫn là source of truth cho strategic messaging; [[copy-system]] là source of truth cho UX writing và product copy. --- ## Approved Vocabulary (external-facing) | Approved | Instead of | |---|---| | Delivery governance | Staffing | | AI-augmented engineers | AI engineers / AI-native engineers (when speaking to SI buyers) | | Extended delivery arm | Talent marketplace | | Information asymmetry (describing the problem, not the solution) | — | | Governance and information problem | Talent problem | --- ## Banned Words (Marketing) - Speed / fast / rapid / nhanh - Flexible / agile (as a marketing claim) - Staff augmentation - Talent marketplace - "We deliver" / "we execute" - "Top talent" / "best engineers" (unverified claim) - "Seamless" / "world-class" / "cutting-edge" --- ## Two-Layer Vocabulary System **Layer 1 — Internal vocabulary** (team communications, strategy docs, briefs — never in published content): - Delivery governance / delivery intelligence - Extended delivery arm - Information asymmetry - AI-augmented pool / pool system - Trust Graph / PAM / Moat - Category building - SI buyer / Tier 2/3 SI **Layer 2 — LinkedIn vocabulary (April 2026)** (appears in real posts — no Talex terms, only the SI buyer's own language describing their problem): - "The silence was the problem." - "Both sides were managing a version of reality the other side could not see." - "The wrong hire is not a setback. It is the project." - "It accumulates." - "The questions that actually reveal the difference are about what the engineer does when the AI is wrong." --- ## LinkedIn Page Setup (Before First Post) > ⚠️ Updated 2026-04-15 — từ [[2026-04-inbound-marketing-strategy]] (Copy Master document) - **Tagline:** ⚠️ "We govern the people. You manage the work." — AI-generated, KHÔNG phải tài liệu công ty chính thức. Không dùng trong bất kỳ output nào. - **About section** (draft ~400 words): Adapted từ Kiên's About — operator voice, not vendor pitch. Không claim "top/best/fastest." Số liệu: 500+ assessments. Kết: "What we share on this page comes from what we see operating every day." Full draft có trong `raw-sources/talex-inbound-marketing-strategy-apr2026.md` - **First post draft:** "We're opening this page because there are things happening at the project level... No hiring pitches. No culture posts. Just what we see on the ground." (~90 words, không hashtag, không CTA) - **Specialties** (LinkedIn search): Engineering governance, AI-augmented teams, Vietnam engineering talent, IT consulting delivery, managed engineering teams, talent assessment, delivery intelligence --- ## Category Strategy (Internal Frame) April 2026 is a **mental model building** phase — not a product introduction phase. Three failed approaches (and why): - **Introduce the product** → Product incomplete → No trust → Ignored. Terms not finalized, policy not built, product not complete. - **Educate the category** → Requires brand recognition with SG SI buyers that doesn't exist yet. Education requires trust. Cognitive burden on a reader with no reason to care. - **Talk about buyer's pain** → SI buyer reads their pain → Recognition → Trust. This is the chosen approach. Works because 6 years of PAM data, 500+ assessments, 30+ projects exist now. No product completion required. Frame: When the buyer reads their own problem articulated precisely, trust builds. The category establishes itself in their mind without being named. "Talex appears after the mental model is built — as the natural answer, not as a vendor pitching." --- ## Homepage vs. Internal Positioning (Gap Alert) As of Apr 13, 2026, the live homepage (`talex.co`) uses language that **contradicts** internal brand rules from Moat V5.3: - Homepage uses: "seamless," "flexibility," "resource scaling," "ramped up in days" - Internal rules ban: seamless, flexible, speed framing, "talent marketplace" framing - Homepage tone = product-introduction mode; internal strategy = mental model building phase Source: [[2026-04-13 Talex.co Homepage]] > Homepage may have been written before Moat V5.3 was finalized. Needs alignment review. --- ## Anchor Article 1 — Content Notes The first anchor article (draft Apr 14, 2026) targets query: *"how to evaluate AI skills in engineers"*. It uses Tier 1/2/3 (Output-dependent/aware/governing) labeling — **not** the internal Moat AI-Enabled/Integrated/Native labels. Key alignment checks before publishing: - Article mentions "15–20% are Tier 3" — verify this stat is PAM-sourced or mark as estimate - Article uses first-person plural ("we found", "our dataset") — confirm Kiên is co-author or this is Talex org voice - Article does NOT mention "Talex" in body, only in footer attribution — consistent with April LinkedIn rules, but confirm if `talex.co/insights` publication changes this Source: [[2026-04-14-anchor-article-1-ai-engineer-evaluation]] --- ## Related Pages - [[talex]] — Company overview and product details - [[gtm-strategy]] — Channel execution and sales motion - [[q2-2026-plan]] — April 2026 plan