54 — Landing Pages
Status: CANONICAL · Commercial OS
Owner: PMM hat
Last verified: 2026-07-21
Purpose
The campaign-specific landing pages beyond the core site (53): each with a single job, a single audience, a single CTA, and complete copy. Landing pages are arguments, not brochures.
Target audience: PMM, whoever builds pages; sales (for send-able links).
LP-1: The Manifesto / Category Page (/manifesto)
Job: convert the intellectually curious into believers and subscribers. Traffic: founder content, PR, launch (51 Layer 1).
Work is leaving the apps.
Software 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.
The next era doesn't add another tool. It gives work a home.
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.
Five requirements define it — grade any vendor, including us:
- Shared work surface — human and AI on the same live work, not a chat beside it.
- Owned canonical state — truth across all tools, held by the organization, with provenance.
- Governed collaboration — AI proposes; humans approve; everything audits.
- Persistent continuity — context survives sessions, tools, people, and model swaps.
- Capability execution — approved actions actually run in connected systems.
[Full essay follows — the four-act narrative from 04, 1,500 words.]
CTA: Get the weekly essay → newsletter (60) · secondary: See the workspace →
LP-2: The Demoted-AI Page (/second-chance)
Job: convert the burned. Traffic: demotion-story content, retargeting, sales sequences (T2 asset 37 Play 1).
You didn't stop believing in AI. You stopped believing in that AI.
Six 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.
Here'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.
IntegrateWise is AI built for the day after the demotion:
- It starts in context — it shares your workbench and your organization's assembled truth.
- It remembers what you approve — and nothing else. Ever.
- It acts only with your approval — and leaves a receipt every time.
Give AI its second chance — with supervision this time.
CTA: See the morning → (demo) · secondary: Read how the approval gate works
LP-3: The CS Leader Page (/customer-success)
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) 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), design-partner metrics band, and the POV offer explained (30 days, your tools, three criteria, a decision).
CTA: Run your numbers (calculator → email gate) · Start a proof of value →
LP-4: The Security Page (/security)
Job: let a CISO self-serve to "yes-able." Copy: public rendering of 42 Security FAQ §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.
CTA: Request the security packet · Book an architecture review
LP-5: The Comparison Pages (/vs/copilots, /vs/cs-platforms, /vs/assistants)
Job: capture comparison-intent search (55) without naming competitors (advertising rule 09 preserved — pages compare categories).
Template (each ~600 words):
- Respect block: what that category is genuinely good at (documents / CS workflow / drafting).
- The boundary: the job it structurally can't do — the silo, the rules engine, the amnesia — told through one concrete scenario (the Meridian pattern).
- The rubric: the five category requirements, self-graded honestly.
- The one-liner: the canonical kill line for that category (18 §4).
CTA: See the difference in one morning →
LP-6: The POV Application Page (/proof)
Job: convert high-intent evaluators into scoped POVs — self-qualification built in.
Thirty days. Your tools. Three numbers. Then you decide.
A 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.
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).
CTA: Apply for a proof of value
Landing Page Standards
One 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) and claims register (79) · UTM-instrumented; conversion tracked per page in 73 Marketing Metrics · pages that convert < 2% for two months get rewritten or retired.
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.
Related: 53 Website Copy · 55 SEO · 52 Website Strategy · 29 ROI