Explains CAJ Operate as a governed business operations platform, not only as an AI chatbot.
Review landing pageCheck the public product showcase before recording or publishing.
Use this page as the final review board for the CAJ Operate public website. It keeps the platform story, animated demos, conversion route, safety notes and recording assets in one place before the final Vercel deployment.
Review the public showcase like a customer will see it.
The goal is not only that the pages build. The public website must explain the product clearly, use safe scripted data and guide the visitor towards a sensible pilot conversation.
Product story
The platform should be easy to understand before a visitor opens any animated demo.
Shows one joined-up day in a business: enquiry, call, booking, lead, documents, finance evidence and owner visibility.
Open story routeExplains the product through customer types such as trades, professional services, ecommerce, hospitality and owner-managed operations.
Review use casesAnimated demos
Feature demos should use scripted data only and show clear operational outcomes.
Groups all animated demos and gives a recommended first playlist for customer calls and product videos.
Open Demo StudioEach demo includes play controls, click sounds, captions, transcript, workflow board and customer-friendly before/after explanation.
Open first demoPresenter controls, keyboard navigation, captions and transcript support are in place for safer public presentation.
Check controlsConversion route
Visitors should know what to do next after watching the product story.
Collects business type, main channel, operational problem, preferred workflow and contact preference without touching the SaaS admin app.
Open pilot formShows practical package direction and a fit planner so customers can understand the right starting point.
Review packagesKeep the guided pilot message honest while provider self-service and wider onboarding continue to mature.
Review FAQTrust and safety
The public pages should show control, privacy and governance without exposing internal implementation details.
Compares the usual scattered way of working with CAJ Operate's controlled operational workflow.
Open comparisonTrust panels explain protected data, human control, audit visibility and review-first behaviour in customer language.
Review trust featurePublic demos must stay scripted and must never depend on live messages, provider credentials, protected documents or real finance data.
Recording and launch assets
Use the public website as a reusable video-recording and sales-call toolkit.
Shot lists, narration prompts and route links are available for the first product video and deeper demo recordings.
Open recording guideShare copy, SEO phrase guide and route map are available for final public launch preparation.
Open launch kitRun lint/build locally and manually review mobile layouts before the final deployment pass.
Review customer, recording and launch-support pages separately.
Use this guide to move through the product area in the same order a customer or presenter will see it. The final deployment pass should not start until these route groups have been reviewed on desktop and mobile.
Final checks for navigation, mobile, customer clarity and safety.
These checks are deliberately practical. They focus on whether the public product story is understandable, safe to publish and easy to record before the final deployment bundle.
Navigation and route review
Open the platform route set from the header, footer, Demo Studio, Launch Kit and Readiness Centre on desktop and mobile.
- Every /platform route opens without a dead link or missing asset.
- Primary customer routes are visible without relying on internal launch-only pages.
- Footer links do not overwhelm the customer with duplicate labels.
- All Next.js links added in this pass keep prefetch={false}.
Mobile and recording review
The pages must work as public landing pages and as video-recording surfaces without cramped controls or hidden CTAs.
- Animated demo controls are reachable on phone, tablet and desktop widths.
- The 16:9 recording area does not force sideways scrolling on mobile.
- Reduced-motion and muted playback remain understandable through captions and transcripts.
- Presenter-only pages are clearly labelled as review or recording support.
Customer understanding review
A non-technical customer should understand the daily problem, what the platform does, and which pilot path to choose.
- The product is described as an operations platform, not only as an AI chatbot.
- Each demo starts with the daily business problem before showing the workflow.
- Pricing and pilot pages explain guided onboarding honestly.
- The final CTA always points towards a guided demo or pilot conversation.
Safety and trust review
The public showcase must avoid real tenant data and must not imply uncontrolled finance, payroll, tax or protected-data actions.
- Demo pages use scripted Harbour Home Services data only.
- No real WhatsApp numbers, call transcripts, provider secrets or tenant records are shown.
- Finance, documents, HMRC and protected-data messages stay review-first and audit-aware.
- The public demo pages do not call the live SaaS/admin APIs.
Open the important public routes before the final deployment pass.
Use this route map for desktop and mobile review. Keep deployment until the final bundle after the remaining metadata, navigation and launch cleanup work is complete.
Public platform route map
Before the last deployment pass
- Run pnpm lint and pnpm build from the public website root.
- Open every /platform route on desktop and mobile widths.
- Record at least one pass through /platform/story and the WhatsApp demo page.
- Confirm click sounds only start after the user enables them.
- Confirm the pilot form submits through the existing public contact flow.
- Confirm .env.local is ignored and .env.example is safe to commit.
- Deploy only after the final deployment bundle and route review are complete.
Use the final runbook once this readiness page is clean.
The deployment runbook keeps the last step disciplined: clean Git state, local checks, Vercel deploy, live smoke test and rollback path.
Confirm the Git baseline is clean
The public website should already be initialised under Git before the demo system is applied. Do not deploy a tree with untracked patches, local secrets or unresolved build fixes.
- Run git status and confirm the expected WD patches are committed.
- Confirm .env.local is ignored and .env.example is tracked as the safe template.
- Keep the public website separate from the CAJ Operate SaaS/admin platform.
- Keep generated demo pages scripted and free from live tenant data.
Run the local verification pass
The launch should not rely on Vercel to discover avoidable errors. Check linting, production build, social image routes, the pilot form, and the core public routes locally first.
- Run pnpm lint and pnpm build from the public website root.
- Open /platform, /platform/demo, /platform/story, /platform/pilot and /platform/readiness locally.
- Open /platform/opengraph-image and /platform/twitter-image to confirm social images prerender cleanly.
- Check the animated demo player with sound off, sound enabled, keyboard controls and reduced-motion settings.
Review customer clarity
The public showcase must explain the everyday business problem first, then show how CAJ Operate turns communication, documents and follow-up into controlled operational work.
- Start the walkthrough from /platform/story for a connected business-day narrative.
- Use /platform/demo for feature-specific animations only after the story is understood.
- Use /platform/compare and /platform/faq to answer common buyer objections.
- Keep the pilot CTA visible and honest: guided setup first, wider rollout later.
Confirm production environment values
Production environment values should live in Vercel, not in committed files. The public site needs only website-safe variables and contact-form credentials.
- Set NEXT_PUBLIC_SITE_URL to the production domain.
- Set contact, WhatsApp and reCAPTCHA values only where they are actually used.
- Keep RESEND_API_KEY and RECAPTCHA_SECRET_KEY server-side in Vercel environment settings.
- Do not upload or commit SaaS runtime keys, provider credentials, OAuth tokens or tenant secrets.
Final local checks
Run these commands from the public website root before the deployment command.
pnpm install
pnpm lint
pnpm buildFinal Git commit
Commit the final deployment/runbook bundle after the local checks pass.
git status
git add .
git commit -m "Add CAJ Operate public launch runbook"Check every platform route before the final deployment.
These are the routes that now carry consistent Open Graph imagery, platform descriptions and route intent. Primary routes are customer-facing; review routes support recording and launch checks.
/platformPlatform landing
Explain CAJ Operate as a governed business operations platform for customer messages, calls, bookings, documents, workflow routing and daily visibility.
- Search intent
- Primary product discovery route for new visitors.
- Audience
- Owners and managers deciding whether the platform fits their business.
/platform/storyProduct story
Show the product as one connected working day before sending customers into individual feature demos.
- Search intent
- Best route for a one-take sales walkthrough or investor recording.
- Audience
- Customers, investors and partners who need the whole product explained quickly.
/platform/demoDemo Studio
Animated, scripted feature demos that show the problem, the workflow and the result without using live tenant data.
- Search intent
- Main video-recording and customer demonstration hub.
- Audience
- Prospects who want to see practical workflows before booking a pilot.
/platform/featuresFeatures
Feature-by-feature explanation for WhatsApp, voice, appointments, leads, documents, finance evidence, routing, security and business health.
- Search intent
- Explains product capabilities without overwhelming visitors with admin detail.
- Audience
- Visitors comparing the platform with ordinary CRMs, chatbots or booking tools.
/platform/use-casesUse cases
Show how different businesses can start with the right first workflow: trades, professional services, ecommerce, hospitality or owner-managed operations.
- Search intent
- Helps customers recognise themselves in the product story.
- Audience
- Business owners looking for examples close to their daily work.
/platform/pilotGuided pilot
Collect the visitor's business type, main channel, current problem and first workflow so CAJ can shape a sensible guided pilot.
- Search intent
- Primary conversion route for serious platform enquiries.
- Audience
- Businesses ready to discuss a guided setup or pilot.
/platform/pricingPackages
Explain package direction, guided setup and the practical route from pilot to wider rollout.
- Search intent
- Helps buyers understand what they are paying for and why onboarding is guided first.
- Audience
- Decision makers checking commercial fit.
/platform/compareCompare
Compare scattered communication and manual follow-up against a governed operating workflow.
- Search intent
- Turns objections into clear before-and-after explanation.
- Audience
- Buyers who already use several disconnected tools.
/platform/faqFAQs
Answer common questions about AI assistance, human control, guided pilots, safe demos, WhatsApp, voice, documents and finance evidence.
- Search intent
- Reduces confusion before a prospect submits the pilot form.
- Audience
- Visitors who need trust and practical detail before contacting CAJ.
/platform/recordingRecording guide
A practical recording guide with product video shot lists, narration prompts and safe demo rules.
- Search intent
- Internal public-site route for preparing sales and investor videos.
- Audience
- CAJ team and trusted reviewers.
/platform/launch-kitLaunch kit
A launch reference for route links, product copy, share messages, SEO phrases and checklist items.
- Search intent
- Keeps launch messaging consistent before final deployment.
- Audience
- CAJ team and trusted reviewers.
/platform/readinessReadiness
Final public-route review checklist before deployment, recording or customer sharing.
- Search intent
- Checks route quality, demo safety, conversion path and metadata readiness.
- Audience
- CAJ team and trusted reviewers.
/platform/deploymentDeployment runbook
Final local checks, Git handoff, Vercel deployment order, smoke-test routes and source-of-truth notes for the public platform showcase.
- Search intent
- Keeps final publication, rollback and source-of-truth handoff disciplined after the public demo build.
- Audience
- CAJ team and trusted reviewers.
