CAJ Digital TechnologiesCustom digital growth systems
Chat
Launch kit

Prepare the CAJ Operate story before the public launch.

Use this page as the final public-website checklist before recording videos, sharing the product pages, or opening a guided pilot conversation with a customer.

Open Demo StudioOpen pilot formOpen readiness checklist
1Product messageOperations platform, not just chatbot wording.
2Demo routeAnimated feature stories with scripted customer data.
3Conversion routeFit finder, packages and guided pilot request.
Launch route guide

Keep customer pages, demo pages and internal review pages in the right order.

Use this map before recording or publishing so the product story starts simple, shows proof through the demos, then moves the right customer into a guided pilot request.

Launch QA

Check the practical details before final deployment.

These checks keep the showcase clean: safe scripted data, mobile-friendly routes, clear CTAs and no accidental live SaaS dependency.

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.
Launch checklist

Use one review path before recording or deployment.

This checklist keeps the public website focused on clear customer understanding, safe demo data and a guided sales route before the final Vercel deployment.

01

Protect the public website baseline

Ready

The website should be committed in Git before any recording or launch pass so every visual change can be reviewed, restored and improved safely.

Review website baseline
02

Use the product landing route first

Ready

Start customer conversations from the platform page, then move into demos, pricing, comparison or pilot request depending on the customer’s question.

Open platform page
03

Record the animated demo route

Ready

Use the Demo Studio and recording guide to capture the WhatsApp, voice, appointment and daily-management story with scripted demo data only.

Open demo studio
04

Check customer fit before selling a package

Ready

Use the pilot form and fit finder to decide which first workflow gives the clearest value: messages, calls, bookings, documents, finance evidence or visibility.

Open pilot request
05

Review the trust and control message

Check

Keep public wording clear: CAJ Operate is a governed operations platform with AI assistance, human control, protected data and audit-aware workflows.

Open FAQ
06

Deploy only after local build and page review

Final pass

Before the final Vercel deployment, run the full local build, open the platform routes, test the pilot form and confirm the animated demos behave on desktop and mobile.

Review launch checklist
Share kit

Keep the product message consistent across videos, pages and pilot calls.

Use these page links, phrases and short message drafts as a practical launch reference while recording and reviewing the public showcase.

SEO and social routes

Review the public routes that search engines and shared links will see.

This launch map keeps the platform pages, buyer-support pages and recording routes in one place so titles, descriptions and share intent stay consistent before deployment.

Primary public route/platform

Platform 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.
CAJ Operatebusiness operations platformAI assistant for business
Open route
Primary public route/platform/story

Product 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.
CAJ Operate product storybusiness operations demoAI business assistant
Open route
Primary public route/platform/demo

Demo 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.
CAJ Operate demoAI workflow demoWhatsApp voice booking demo
Open route
Primary public route/platform/features

Features

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.
CAJ Operate featuresbusiness workflow softwaresecure document workflow
Open route
Primary public route/platform/use-cases

Use 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.
business operations use casesAI assistant for tradessmall business workflow
Open route
Primary public route/platform/pilot

Guided 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.
CAJ Operate pilotguided demobusiness workflow platform
Open route
Buyer-support route/platform/pricing

Packages

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.
CAJ Operate pricingguided pilot packagesbusiness operations SaaS
Open route
Buyer-support route/platform/compare

Compare

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.
business operations comparisonAI assistant vs chatbotworkflow platform
Open route
Buyer-support route/platform/faq

FAQs

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.
CAJ Operate FAQAI assistant human controlguided pilot SaaS
Open route
Review and recording route/platform/recording

Recording 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.
CAJ Operate recording guideproduct video shot listdemo recording
Open route
Review and recording route/platform/launch-kit

Launch 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.
CAJ Operate launch kitproduct launchbusiness operations platform demo
Open route
Review and recording route/platform/readiness

Readiness

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.
CAJ Operate readiness checklistpublic demo reviewlaunch checklist
Open route
Review and recording route/platform/deployment

Deployment 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.
CAJ Operate deployment runbookVercel launch checklistpublic showcase deployment
Open route
Deployment handoff

Keep the final publish step simple and reversible.

Use the deployment runbook after the route, mobile, metadata and demo-safety checks pass. It keeps local checks, Git, Vercel deployment and smoke tests in one place.

Open deployment runbook
Stage 1

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.
Open related route
Stage 2

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.
Open related route
Stage 3

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.
Open related route
Stage 4

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 build

Final 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"
Source-of-truth handoff

Record the public demo system as part of the website baseline.

These notes are the practical handoff for future chats: where the demo lives, what it must not touch, and how it should be treated after deployment.

Public showcase location

The CAJ Operate animated showcase is implemented inside the public website project, not inside the live SaaS/admin platform.

Demo safety rule

Animated demos use scripted Harbour Home Services style content and must not call live tenant APIs, reveal tenant data or depend on provider credentials.

Customer understanding goal

The public routes explain CAJ Operate as a governed business operations platform that turns messages, calls, bookings, documents, follow-up and daily visibility into controlled work.

Reusable module direction

The demo system is content-driven with reusable components for demo cards, animated stages, storyboards, workflow panels, use-case journeys, trust panels, route maps and launch-readiness checks.

Use scripted data only

Public demos should never depend on real tenant records, provider credentials, private calls, protected documents or live finance data.

Explain the daily problem first

Customers should understand the pain before they see the animation: missed enquiries, messy follow-ups, document confusion and weak visibility.

Deploy after the full review

Keep Vercel deployment for the final pass after build, mobile review, pilot form testing and recording route checks are complete.

Open readiness checklist