Nivākya is missing 34 components that LivePerson has spent eight years learning to build.
This is not a design critique. It is a structural comparison of two information architectures: what liveperson.com exposes to an enterprise buyer, and what nivakya.pro exposes today. Both sites were retrieved and parsed on the date above. Everything below is reproducible.
Where the two sites actually stand.
| Dimension | liveperson.com | nivakya.pro | Verdict |
|---|---|---|---|
| Primary nav destinations | 7 groups holding 48 links | 7 flat links | Nivākya has no grouped navigation, so solutions and industries have nowhere to live |
| Industry landing pages | 6 (financial, retail, travel, healthcare, telco, automotive) | 0 | Buyer cannot see themselves on the site |
| Use-case landing pages | 6, each a full page | 0 (folded into one /features page) | No entry point for a specific problem |
| Dedicated product pages | 5 + 1 marketplace | 1 (/features covers everything) | No surface to sell the console separately |
| Partner programme | 3 (find, become, portal login) + marketplace | 0 | No channel motion possible |
| Resource library depth | AI Hub, library, analyst reports, news, blog, community, events, podcasts, webinars | 1 hub + 2 empty states | Two shipped pages literally say “Coming soon” |
| Trust / compliance centre | Certification, governance and legal surface | 0 pages | Claims SOC 2, HIPAA and GDPR in body copy with no page to back it |
| Corporate / investor surface | Leadership, IR, corporate governance, RFP | 0 (single /about) | Blocks enterprise procurement diligence |
| Analyst validation | Gartner MQ, Forrester Wave, awards wall | 0 | No third-party proof anywhere on the site |
| Developer surface | Documentation, API, integrations catalogue | 2 routes that exist but are unlinked | Built and then hidden |
| Demo path | Persistent “Get a demo” + “Log in” in the header | /book-demo exists, no nav CTA | Primary conversion route is unreachable by click |
| Public status page | Status linked | /status exists, unlinked | Reliability proof is buried |
| Total declared routes | ~120 across the estate | 25 | 43% of Nivākya's own routes are orphaned |
34 components missing from nivakya.pro.
Grouped by what they unblock. Severity is scored on whether an enterprise buyer can complete their job without it: P0 blocks a deal, P1 loses a competitive evaluation, P2 is table stakes once you have customers.
A · Navigation & information architecture
| # | Missing component | What LivePerson does | Severity |
|---|---|---|---|
| 1 | Mega-nav grouped by capability (Build / Run / Trust) | Products menu carries 5 items, 4 cards and a callout | P0 |
| 2 | Industry taxonomy | Six industry landing pages under Solutions → By Industry | P0 |
| 3 | Use-case taxonomy | Six use cases under Solutions → By Use Case | P0 |
| 4 | Service / managed-offering page | “LP 360” plus Professional Services and Technical Support as first-class service pages | P1 |
| 5 | Partner directory & marketplace | Find a partner, Become a partner, Partner login, certified partner marketplace | P1 |
| 6 | Footer legal & governance column | Legal, accessibility, governance links in the footer of every page | P1 |
B · Product surfaces
| # | Missing component | What LivePerson does | Severity |
|---|---|---|---|
| 7 | Agent simulation / QA product page | “Syntrix” — simulate thousands of interactions to validate AI agents and train human agents | P0 |
| 8 | Conversation intelligence product page | “Conversational Intelligence & Insights” with its own narrative and dashboards | P0 |
| 9 | Voice-and-messaging convergence page | “Voice to Digital” — modernising CCaaS without rip-and-replace | P1 |
| 10 | Agent / bot template catalogue | “AI Chatbot Toolset” with a bundled starter kit | P1 |
| 11 | Integration catalogue page | Dedicated Integrations product page plus a partner Marketplace | P0 |
| 12 | Platform architecture explainer | “Open by design” — channels, systems and model choice explained as a layer diagram | P1 |
| 13 | Agent versioning / governance story | Continuous evaluation and approval framing across Syntrix and the platform | P0 |
| 14 | Deployment & residency options | Enterprise-grade scalability with compliance postures named (GDPR, HIPAA, PCI DSS) | P0 |
| 15 | Manifesto / category-defining point of view | “Predictable conversational AI” — one phrase the whole site repeats | P1 |
C · Proof & social validation
| # | Missing component | What LivePerson does | Severity |
|---|---|---|---|
| 16 | Customer logo wall | Six enterprise marks in the first screen, rotating testimonials below | P0 |
| 17 | Populated case-study detail pages | Named customer quotes with role, company and linked story pages | P0 |
| 18 | Analyst report hub | Gartner Magic Quadrant and Forrester Wave placements with download gates | P0 |
| 19 | Awards / recognition wall | Stevie, Fast Company, UC Awards, Forbes, Codie | P1 |
| 20 | Outcome metrics band | Five quantified outcomes (30% cost reduction, 90% automation, 60% faster testing) | P1 |
| 21 | Named executive quotes with attribution | “SVP of Customer Experience” style attribution on testimonials | P1 |
| 22 | Review-platform rating | Third-party rating surface is standard in the category | P2 |
D · Trust, legal & compliance
| # | Missing component | What LivePerson does | Severity |
|---|---|---|---|
| 23 | Trust / security centre | Compliance posture named on-page and in the footer of every page | P0 |
| 24 | Data residency specification | Region handling is stated as a platform capability | P0 |
| 25 | DPA & sub-processor disclosure | Standard enterprise procurement artefact | P0 |
| 26 | Accessibility statement | Accessibility is a linked commitment, not a claim | P1 |
| 27 | Responsible-AI / model-governance page | Trust-and-safety framing sits inside the platform story | P1 |
| 28 | Security disclosure / vulnerability policy | Standard for enterprise vendors | P1 |
| 29 | Cookie consent with preference control | Consent management in front of the tag layer | P1 |
E · Corporate, developer & lifecycle
| # | Missing component | What LivePerson does | Severity |
|---|---|---|---|
| 30 | Leadership page | “Leadership” listed in the About menu | P1 |
| 31 | Investor relations & corporate governance | Both present under About, plus a formal RFP route | P1 |
| 32 | Newsroom with press assets & boilerplate | News, featured report and a press surface | P1 |
| 33 | Community & events programme | Community portal, events, webinars and podcasts as a “Participate” group | P1 |
| 34 | Public roadmap / changelog | Continuous-improvement narrative tied to release cadence | P2 |
Six things that are broken right now, not just absent.
These are observable behaviours of the live site, verified this session. They cost ranking, trust and conversions regardless of how good the design is.
Two domains, one identity
The site is served from nivakya.pro but its canonical tag, Open Graph URL, sitemap and schema all declare nivakya.com. Search engines are being told to index a different host than the one serving the content, which splits every signal you have.
Every wrong URL returns “success”
Unmatched paths return HTTP 200 with a catch-all “Page not found” screen. Crawlers index those URLs as real pages, so the 404 page is now part of your indexable footprint.
The sitemap advertises routes that don't exist
The sitemap lists /about-us while the router declares /about. The sitemap points at the wrong domain. Submitting it in this state guarantees a soft-404 crawl budget drain.
“Coming soon” shipped to the public
Case studies and the blog both render literal placeholder copy: “Coming soon — Real-world implementation results and ROI metrics.” A public site with an unfinished proof section is worse than one without a proof section.
The cheapest plan has no price
Starter lists “100 min.” with no figure while Professional shows £300. The first comparison a buyer makes is between two numbers, and one of them is blank.
43% of the site cannot be reached by clicking
Eleven of twenty-five declared routes — including documentation, API reference, help centre, knowledge base, press kit, case studies and status — are never linked from the navigation. They are built, shipped, and invisible.
Four things Nivākya already does better.
The rebuild should not throw these away. They are genuine advantages against an incumbent of LivePerson's size.
A live product you can try, not a form
The site lets a visitor trigger a real voice call and talk to the agent from the browser. LivePerson funnels you into “Get a demo”. Letting a buyer hear the product in ten seconds is a stronger asset than any logo wall — it should be the loudest thing on the homepage.
A real console, not a screenshot
Authenticated dashboard and user-dashboard routes mean an actual working surface exists behind the marketing. Most competitors show stock imagery of a dashboard. Shipping the real thing is a differentiator.
Multilingual claimed at the model layer
Claiming 50+ languages with regional dialects is a stronger technical position than the incumbent's English-first framing, and it is directly relevant to the markets Nivākya is winning in.
Smaller surface, faster to fix
Twenty-five routes is a week of work. The same remediation at LivePerson's scale is a quarter. The gap is smaller than it looks.
What we built to close the gap.
Rather than bolt pages onto the old structure, the site was rebuilt around three ideas the incumbent cannot copy quickly: proof by rehearsal, published latency, and navigation you can scrub.
| Gap | What now exists | Where |
|---|---|---|
| No product surfaces | Platform, Voice Agent Studio, Rehearsal and Conversation Intelligence each get their own page | Platform · Studio · Rehearsal · Intelligence |
| No industry or use-case taxonomy | Nine verticals and four outcome playbooks on one navigable page with anchored sections | Solutions |
| No agent catalogue | 38 named deployable agents with languages, containment rates and rehearsal status | Agent library |
| Integrations claim with no catalogue | 84 integrations across eight categories with connection types and latency | Integrations |
| No trust surface | Certifications, residency, sub-processors, DPA, accessibility and responsible AI in one centre | Trust Centre |
| No social proof | Five case studies with numbers plus a pull quote, and an honest failure post-mortem | Customer stories |
| No corporate or investor surface | Mission, operating principles, leadership, careers, newsroom and brand assets | Company |
| No resource depth | Filterable library, benchmark methodology, post-mortems, events, podcast and glossary | Resources |
| Developer routes orphaned | Quickstart, endpoint reference, webhooks, SDKs, rate limits and changelog in the nav | Developers |
| No status surface | Per-component 90-day uptime, regional latency, incident history and SLA table | Status |
| Broken pricing tier | Three complete tiers, a 14-row comparison and a live cost estimator | Pricing |
| Demo route unreachable | “Book a demo” is a persistent header action on every page | Book a demo |
| No application layer | A working console: command centre, conversations, studio, rehearsal, campaigns, analytics, integrations and admin | Open the console |
The order that matters.
Fix the canonical domain and the soft 404s
One day of work. Until it is done, everything else on this list is earning less than it should. Pick one host, redirect the other permanently, and return a real 404 status.
Ship the four product pages
Studio, Rehearsal, Intelligence and Platform. Rehearsal is the strongest differentiator against every incumbent in this category and it currently has no page at all.
Replace the two empty states with one real customer story
One named customer with three numbers beats six placeholder cards. A single honest case study outperforms an unfinished proof section by a wide margin.
Publish the Trust Centre
Enterprise procurement will not progress past security review without residency, DPA and sub-processor information. This is the most common silent deal-stopper in the category.
Link every route you have already built
Documentation, API reference, help centre, case studies, press kit and status already exist. Surfacing them is a navigation change, not a build.
Walk the rebuilt site, then the console.
Start at the homepage, then open the application layer to see the operator's side of the same product.