{"slug":"business/54-landing-pages","title":"54 — Landing Pages","section":"business","sectionLabel":"Business","status":"unclassified","type":"document","path":"business/54-landing-pages.mdx","bytes":6746,"description":null,"updated":null,"source":"integratewise/Integratewise-docs-wiki","content":"\nStatus: CANONICAL · Commercial OS\nOwner: PMM hat\nLast verified: 2026-07-21\n\n---\n\n## Purpose\n\nThe campaign-specific landing pages beyond the core site ([53](53-website-copy.md)): each with a single job, a single audience, a single CTA, and complete copy. Landing pages are arguments, not brochures.\n\n**Target audience:** PMM, whoever builds pages; sales (for send-able links).\n\n---\n\n## LP-1: The Manifesto / Category Page (`/manifesto`)\n\n**Job:** convert the intellectually curious into believers and subscribers. Traffic: founder content, PR, launch ([51 Layer 1](../09-gtm/51-launch-strategy.md)).\n\n# Work is leaving the apps.\n\nSoftware unbundled work into a hundred silos — and people became the glue. Then AI arrived, bolted onto each silo, and made it worse: a copilot per app, a chat tab per task, memory that guesses. Most people quietly demoted AI to writing emails.\n\nThe next era doesn't add another tool. It gives work a home.\n\n**A workspace for human and AI collaborative work** is a system where people and governed AI counterparts do work together on shared surfaces, over canonical operational state the organization owns, with human approval on every consequential action.\n\nFive requirements define it — grade any vendor, including us:\n\n1. **Shared work surface** — human and AI on the same live work, not a chat beside it.\n2. **Owned canonical state** — truth across all tools, held by the organization, with provenance.\n3. **Governed collaboration** — AI proposes; humans approve; everything audits.\n4. **Persistent continuity** — context survives sessions, tools, people, and model swaps.\n5. **Capability execution** — approved actions actually run in connected systems.\n\n[Full essay follows — the four-act narrative from [04](../01-foundation/04-long-term-narrative.md), 1,500 words.]\n\n**CTA:** _Get the weekly essay_ → newsletter ([60](../11-marketing/60-newsletter-strategy.md)) · secondary: _See the workspace →_\n\n---\n\n## LP-2: The Demoted-AI Page (`/second-chance`)\n\n**Job:** convert the burned. Traffic: demotion-story content, retargeting, sales sequences (T2 asset [37 Play 1](../07-sales/37-sales-playbook.md)).\n\n# You didn't stop believing in AI. You stopped believing in _that_ AI.\n\nSix months ago you rolled it out. Today your team uses it to write emails. Not because the models are bad — because it forgot what you told it, stopped halfway, and invented things. You demoted it. Quietly. Everyone did.\n\nHere's what the demotion actually proved: **AI without shared context, memory you control, and approval on actions cannot be trusted with real work.** Your team's instinct was right.\n\nIntegrateWise is AI built for the day after the demotion:\n\n- **It starts in context** — it shares your workbench and your organization's assembled truth.\n- **It remembers what you approve** — and nothing else. Ever.\n- **It acts only with your approval** — and leaves a receipt every time.\n\n**Give AI its second chance — with supervision this time.**\n\n**CTA:** _See the morning →_ (demo) · secondary: _Read how the approval gate works_\n\n---\n\n## LP-3: The CS Leader Page (`/customer-success`)\n\n**Job:** the wedge persona's dedicated conversion page — deeper than the solutions page, built for outbound and event follow-up. Copy: extends the CS solution page ([53](53-website-copy.md)) with: the wound-story block (\"When did a churn last surprise you? The signals were there — in four different tools\"), the ROI calculator embed (H × C × N, interactive, defaults per [29](../05-value-pricing/29-roi-framework.md)), design-partner metrics band, and the POV offer explained (30 days, your tools, three criteria, a decision).\n\n**CTA:** _Run your numbers_ (calculator → email gate) · _Start a proof of value →_\n\n---\n\n## LP-4: The Security Page (`/security`)\n\n**Job:** let a CISO self-serve to \"yes-able.\" Copy: public rendering of [42 Security FAQ](../07-sales/42-security-faq.md) §1–2 verbatim (architecture five answers, data handling table), compliance status with honest dates (§3), the shadow-AI argument (§4), and the packet-request CTA.\n\n**CTA:** _Request the security packet_ · _Book an architecture review_\n\n---\n\n## LP-5: The Comparison Pages (`/vs/copilots`, `/vs/cs-platforms`, `/vs/assistants`)\n\n**Job:** capture comparison-intent search ([55](55-seo-strategy.md)) without naming competitors (advertising rule [09](../02-category-market/09-competitive-battle-cards.md) preserved — pages compare _categories_).\n\nTemplate (each ~600 words):\n\n1. **Respect block:** what that category is genuinely good at (documents / CS workflow / drafting).\n2. **The boundary:** the job it structurally can't do — the silo, the rules engine, the amnesia — told through one concrete scenario (the Meridian pattern).\n3. **The rubric:** the five category requirements, self-graded honestly.\n4. **The one-liner:** the canonical kill line for that category ([18 §4](../03-positioning-messaging/18-terminology-guide.md)).\n\n**CTA:** _See the difference in one morning →_\n\n---\n\n## LP-6: The POV Application Page (`/proof`)\n\n**Job:** convert high-intent evaluators into scoped POVs — self-qualification built in.\n\n# Thirty days. Your tools. Three numbers. Then you decide.\n\nA proof of value, not a free trial: up to 10 seats, full capability, your real stack (HubSpot, Salesforce, Zendesk, Stripe…), three success criteria we agree in writing — like _morning prep under 10 minutes_ and _one documented catch on a real account_ — and a decision date.\n\n**Form fields:** name · work email · company · CS team size (dropdown: <5 / 5–15 / 15–50 / 50+) · CRM (HubSpot / Salesforce / other) · \"what surprised you last quarter?\" (free text — discovery starts here).\n\n**CTA:** _Apply for a proof of value_\n\n---\n\n## Landing Page Standards\n\nOne job, one CTA per page (secondary CTA allowed only if it serves the same visitor) · headline names the visitor's state, not our product · every page passes the terminology checklist ([18 §8](../03-positioning-messaging/18-terminology-guide.md)) and claims register ([79](../14-appendix/79-appendix.md)) · UTM-instrumented; conversion tracked per page in [73 Marketing Metrics](../13-operations/73-marketing-metrics.md) · pages that convert < 2% for two months get rewritten or retired.\n\n**KPIs:** conversion per LP (targets: LP-1 subscribe ≥ 8% · LP-2 demo ≥ 5% · LP-3 calculator ≥ 10%, POV ≥ 3% · LP-6 application completion ≥ 40%) · ICP share of conversions ≥ 60% · sales usage of LPs in sequences.\n\n---\n\n**Related:** [53 Website Copy](53-website-copy.md) · [55 SEO](55-seo-strategy.md) · [52 Website Strategy](52-website-strategy.md) · [29 ROI](../05-value-pricing/29-roi-framework.md)\n"}