Prompt 04 — Public marketing, offerings, pricing, and trust site

Required context

• Design-system and marketing shell from prompt 03
• External wiki product, solutions, pricing, and security pages
• 09-marketing-and-content-strategy.md
• 11-offerings-pricing-and-entitlements.md
• Approved released/beta/planned feature and entitlement statuses

Prompt

Build Capablio's public marketing site from the external Experience Wiki. The site must communicate a credible enterprise product without inventing proof.

1. Build the public route set

Implement, at minimum:

• Home
• Platform overview
• Adaptive feedback
• 360 feedback
• Development plans
• Engineering leadership
• Solutions for HR/people teams
• Solutions for managers
• Solutions for technology leaders
• Enterprise solution
• Integrations
• Security
• Pricing
• Resources index
• Contact/demo
• Sign-in handoff

Hide or mark planned pages according to the feature index. Do not publish empty placeholder routes.

2. Implement the message hierarchy

Homepage must include:

• Clear category and value proposition
• Four differentiated product outcomes
• Role-based pathways
• Product workflow from program → feedback → insight → PDP → follow-up
• Enterprise governance and privacy explanation
• Pricing entry point
• Documentation and security links
• Honest CTA options: Start free only if self-service exists; otherwise Join beta or Book demo

3. Build pricing from one source

Use the entitlement/pricing configuration or a generated content source. Support:

• Free
• Individual
• Team
• Enterprise

Define active subject seats and guest rater treatment. Show plan limits and add-ons only when approved. Ensure application upgrade prompts and marketing pricing cannot drift.

4. Build trust without unsupported claims

Security page should distinguish:

• Implemented controls
• Available by plan
• Beta/limited availability
• Planned controls

Cover tenant isolation, auth, role/scope controls, aggregation/thresholds, encryption/recovery actually supported, audit, retention, support access, AI data handling, and contact for security review.

Do not display certification badges, uptime percentages, data-residency regions, or customer-managed-key claims without evidence and approval.

5. Build truthful product visuals

Use actual product screenshots or component-composed product illustrations based on released UI. Do not fabricate customer data. Use synthetic names and visibly synthetic/demo tenant data. Ensure visuals have alt text or adjacent descriptive content.

6. SEO, performance, and governance

Implement:

• Per-page title, description, canonical, social metadata
• Sitemap and robots behavior
• Structured data only where accurate
• Semantic headings and skip navigation
• Responsive images and lazy loading
• Consent-aware analytics if analytics is used
• No third-party scripts without a documented purpose and owner
• Broken-link and metadata tests
• Content last-reviewed metadata in the wiki, not necessarily visible on every marketing page

7. Conversion and handoff

• Demo/contact form has validation, spam protection appropriate to the stack, privacy notice, success/error states, and CRM/email handoff if available.
• Sign-in preserves return URL safely.
• Start-free flow checks actual entitlement and onboarding capability.
• Pricing CTAs are plan-aware and do not lead to dead ends.

Acceptance gates

• All claims map to external wiki pages and released/beta status.
• No invented customer proof or certification.
• Core pages meet accessibility and responsive gates.
• Pricing has one canonical data source.
• Contact/start flows work end to end in the target environment.
• Marketing build, sitemap, link check, and representative performance checks pass.