Confidential · Client Deliverable · – Back to Client Portal
Lyviss · Engagement Synthesis

The Lyviss engagement, in one read.

A four-document plan to make Live Assist for Microsoft Dynamics 365 findable, citable, and credible across the US D365 mid-market. This is the executive synthesis – the long-form diagnostics and execution detail live in the companion documents linked below.

Horizon
12 mo
Tiers
4
Action items
30
Roles
10
ICP fit (US)
30–50K
Industries
6
Executive Summary

TL;DR

The technical foundation is functional but undersold. A separate US Targeting Strategy analysis reframed who we should actually be talking to: 200–2,000 employees on Dynamics 365 Customer Service Enterprise, across IT services, manufacturing, distribution, professional services, public sector, and mid-market healthcare – roughly 30,000–50,000 US companies, not the enterprise-insurance / Genesys-replacement segment the site currently implies. The 12-month tiered plan still applies; what changes is which industry rewrites get priority, which competitors get the compare hub, and where paid media aims. The team plan (10 roles, AIG core + specialists + Lyviss-internal) holds. Pricing lives in the SOW.

The bottom line

Lyviss is technically clean enough to rank but invisible to AI engines – 22% schema coverage, 0 AI citations, 1 blog post in 22 months. Fixing that is a four-tier, twelve-month build. The realistic US footprint is narrow – LAD365 is a Microsoft-extension add-on, not a comprehensive CX stack – and the plan below is aligned to that reality. Ten roles deliver it. Three CEO-level decisions frame the next 90 days.

The Four Documents

One engagement, four documents.

Each card opens the full report. This executive synthesis pulls from all four – read this first, then dive into the doc that matches the decision you're trying to make.

Bottom Line

What you need to know in five bullets.

  1. 1
    Lyviss is invisible to AI, not broken. The site renders cleanly. What's missing is the schema, entity graph, and content velocity that let AI engines (and the next generation of search) find and cite it. Tier 1 fixes that without rewriting anything substantive.
  2. 2
    The realistic US market is narrow – by ~30,000 companies. LAD365 is a Microsoft-extension add-on for D365 Customer Service Enterprise, not a head-to-head competitor to Genesys or NiCE. The plan is now aligned to that reality, not the comprehensive-CX-stack narrative the marketing copy currently implies.
  3. 3
    The 12-month plan still holds; the audience priority shifts. Industry rewrites (Tier 2) prioritize mid-market healthcare and add IT services / manufacturing / distribution / professional services / public sector. The compare hub drops Genesys and LivePerson as flagship comparisons – they belong to enterprise insurance, which we skip.
  4. 4
    Ten roles, no headcount increase. The team plan (5 AIG core + 5 specialists, with Lyviss-internal seats) absorbs the additional alignment work. Tier 1 Web Dev load goes up ~25% – flag if the Lyviss engineering team can support it; otherwise Tier 2 staging is the fallback.
  5. 5
    Three decisions frame the next 90 days. Sign-off on the target ICP, approval to deprioritize Anthology-as-flagship and Salesforce/Genesys comparison framing, and confirmation that the Lyviss product team can support the mid-market healthcare HIPAA work in Tier 1. None are large; all are required to start.

Who we're aiming at, honestly.

The full targeting analysis is in US Targeting Strategy. The summary:

US ICP fit (companies)
30–50K

Fits the realistic footprint of LAD365 as a Microsoft-extension add-on.

Employee band
200–2,000

Mid-market on D365 Customer Service Enterprise – the buyer profile that fits.

Industries on target
6

IT services, manufacturing, distribution, professional services, public sector, mid-market healthcare.

Buyer signal
D365 CS

Live Assist adds live chat + cobrowse on top of D365 Customer Service Enterprise. Not a replacement.

Industries – target vs. skip

IT services Manufacturing Distribution Professional services Public sector Mid-market healthcare Enterprise insurance (Genesys/NiCE) Anthology higher-ed B2C Zendesk replacement Salesforce head-to-head
Decisions for the CEO

Three questions for the next 90 days.

None are large commitments. All unblock Tier 1 kickoff and the 12-month cadence.

1

Sign off on the realistic ICP.

Do we agree that LAD365's US sweet spot is 200–2,000 employees on D365 Customer Service Enterprise – and not the broader CX-stack narrative?

Why it matters: The targeting analysis below the surface says yes. Saying it out loud commits the marketing site, the compare hub, and the Tier 4 paid campaigns to that ICP. Without it, we keep hedging into segments (Genesys-replacement, Salesforce head-to-head, B2C Zendesk) where LAD365 does not win.

2

Drop Anthology as flagship + trim Genesys / LivePerson from the compare hub.

Are we comfortable repositioning from "comprehensive CX stack" to "D365-native live chat & cobrowse extension" – even if that means fewer headlines?

Why it matters: The current copy positions LAD365 against enterprise insurance (Genesys/NiCE) and Anthology higher-ed. Neither fits. Repositioning trades reach for fit – which is what wins mid-market D365 deals and what Microsoft's co-sell motion rewards.

3

Confirm the Lyviss engineering + product team can support Tier 1.

Tier 1 adds 7 concrete tech deliverables (industry schema, LocalBusiness, HIPAA block, VideoObject, CF7 GA4 mapping, og:image rebuild, support-lifecycle FAQ) – does the Lyviss side have bandwidth in months 1–3?

Why it matters: Tier 1 is the foundation everything else stacks on. If Lyviss engineering is constrained, we stage the Local Schema Sprint into Tier 2 – no quality loss, just a different timeline.

90-Day Next Steps

What happens in the first 90 days.

Mapped against Tier 1 (Months 1–3 · Plug the leaks). Each step has a defined owner and a measurable outcome.

Week 1

AIG core seats onboard. Lead Writer drafts the editorial calendar for 36 posts. Web Dev starts the schema architecture (SoftwareApplication, FAQPage, AboutPage).

Week 2

Designer delivers OG + logo variants. Senior Writer #1 starts Tier 2 blog output. The 5 critical metadata bugs (/library/, /blog/, /pricing/, /generative-ai/, /contact/) ship.

Week 3

Senior Writer #2 + Analytics Specialist come online. GA4 + Clarity + GSC + Bing live. CF7 form IDs (#4821, #1607, #6341, #6332, #6291) wired to GA4 events.

Week 4–8

Local Schema Sprint – LocalBusiness + 15-country Organization.address. Industry-specific schema for target ICP verticals (MedicalOrganization for mid-market healthcare, plus GovernmentOrganization / ProfessionalService variants).

Week 6–10

HIPAA compliance block + BAA subpage on /healthcare/. Microsoft AppSource listing submitted. G2 / Capterra / Crunchbase / SaaSHub / AlternativeTo profiles claimed.

Week 9–12

/end-of-support-policy/ rewritten as Microsoft-style support lifecycle FAQ + HowTo schema. Lighthouse + Core Web Vitals fixes land. Tier 1 KPI report delivered.

What's At Risk

If we don't move.

Lyviss has a defensible product and a real install base. The risks below are about visibility, not viability.

  • AI engines won't cite Lyviss in D365 live-chat answers. As more buying happens in ChatGPT / Copilot / Perplexity, an entity graph that's one link wide (YouTube-only) means the brand disappears from the conversation. Tier 1 is the cheapest fix; tier 4 the most expensive.
  • Microsoft co-sell stays gated until the AppSource listing and Partner customer story ship. Co-sell is the highest-leverage channel for a Microsoft-extension add-on – losing another 6 months of co-sell readiness means losing another 6 months of pipeline.
  • Compare-hub framing keeps converting wrong-fit leads if Genesys-replacement and Salesforce-head-to-head pages stay flagship. They generate traffic but rarely convert, because the buyers don't fit the D365 mid-market profile.
  • The 22-month content gap compounds against Lyviss. One blog post since Feb 2024, while competitors ship 2–4 per month, means topical authority gaps widen every month Tier 2 is delayed.
Channels & Investment

How the money flows.

No dollar amounts on this page – all financial detail lives in the SOW. The shape of the spend is below.

Where the engagement spends

  • 5 AIG core seats (week 1, stable across all 4 tiers)
  • 5 AIG specialist seats (activate at tier: PR + Reviews at Tier 2, Paid Media + LinkedIn at Tier 4)
  • Tier 4 paid media: Google Ads + Microsoft Ads + LinkedIn Lead Gen (budget paced in SOW)
  • Tool stack: Ahrefs / Semrush, Screaming Frog, HARO, GA4, Clarity
  • Conference sponsorship (DynamicsCon or D365 Summit, Tier 4)
  • Web Dev full-time, months 1–3; fractional Tier 2 onward

Where it doesn't

  • Enterprise insurance segments (Genesys / NiCE / LivePerson replacements) – wrong ICP
  • Anthology higher-ed positioning – not a paying LAD365 customer
  • B2C Zendesk-replacement marketing – wrong segment
  • Salesforce head-to-head comparison content – wrong competitor set
  • Tier 5 (months 13–18) handoff authoring – optional line item in SOW
  • Conference-as-Lyviss-led participation – flexible model in SOW
Sources

Where the numbers come from.

A consolidated list of the data behind this synthesis. Full source notes are in each companion document.

Visibility Report & 12-Month Tiered Plan: live site audit (Sep 2026) – 8 layers (meta, schema, entity, content, reviews, E-E-A-T, multi-region, perf). 30-row recommendation matrix. Four-tier execution plan.

Team & Assignments: 10-role org chart; RACI matrix covering 50+ tasks; in-house/outsourced split; staffing timeline; 15 second-pass deltas applied.

US Targeting Strategy: sized US mid-market D365 Customer Service Enterprise footprint (~30–50K companies), target industries, hard conversation on stack framing, four GTM tiers, three CEO questions.