Final launch runbook

Deploy the CAJ Operate public showcase only after the full local review.

This runbook keeps the final website launch disciplined: verify the Git baseline, build locally, review the animated demo routes, confirm the pilot conversion path, then deploy to Vercel when the public showcase is ready.

Open readiness centre Open launch kit Open Demo Studio

6launch stages

0live SaaS dependencies

1final deploy command

Final launch runbook

Follow this order before publishing the public platform showcase.

The final launch path is deliberately simple: clean Git state, local checks, route review, production environment values, deploy, smoke test and rollback readiness.

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.

Stage 5

Deploy and verify the live site

Deploy after the local build and route review succeed. Once deployed, perform a short live smoke test before sharing the product pages or recording public video clips.

Deploy to Vercel from the committed public website state.
Open the production /platform route and follow the product story, demo, pricing and pilot paths.
Submit a safe test pilot enquiry if the contact route is enabled.
Confirm sitemap, robots, metadata and social image routes work on the deployed domain.

Open related route

Stage 6

Keep a rollback path

A public website launch should be reversible. Keep the last known good commit visible and use Vercel rollback if a production-only issue appears.

Tag or note the final launch commit.
Keep the previous Vercel deployment available for rollback.
If a production bug appears, patch narrowly and redeploy from Git rather than editing live settings blindly.
Do not patch the SaaS/admin app to solve public website copy or animation issues.

Start the customer storyUse this route for a connected one-take product walkthrough.Choose a feature demoUse this route to open the animated feature demos and recording controls.Check buyer clarityUse this route to explain the usual way against the CAJ Operate way.Collect pilot interestUse this route for guided pilot enquiries and customer fit context.Review public readinessUse this route before recording or deployment.

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"

Vercel deployment

Use this when you are ready to publish the public website. If the project is already connected to Git in Vercel, pushing to main may be enough instead.

pnpm dlx vercel@latest deploy --prod
# Or, when the Vercel project is connected to Git:
git push origin main

Live smoke test

Open these routes on the production domain after deployment.

/platform
/platform/story
/platform/demo
/platform/pricing
/platform/pilot
/platform/readiness
/platform/opengraph-image
/platform/twitter-image
/sitemap.xml
/robots.txt

Route guide

Keep customer, demo, conversion and review routes separated.

The launch navigation keeps the public customer journey clean while still giving you internal recording, readiness and deployment support routes.

Start here

Understand the platform

Use these pages first when a visitor needs the plain-English product story before watching detailed feature demos.

Platform overviewWhat CAJ Operate does and why it exists.Product storyA connected working-day walkthrough for demos and sales calls.CompareShow the difference between scattered tools and governed operations.FAQsAnswer common buyer questions without overloading the main page.

Show it

Watch and record demos

Use these routes when presenting the product, recording videos, or showing a customer how daily work moves through the platform.

Demo StudioChoose the right animated demo for a customer or video.FeaturesBrowse each capability and open the matching demo page.Use casesExplain the product by customer type and daily work pattern.Recording guideFollow shot lists, narration prompts and safe recording rules.

Convert

Help the customer choose a path

Keep the public sales route clear: explain fit, package direction and the guided pilot route without pretending the product is fully self-serve for every tenant yet.

Pricing and packagesExplain package direction, support and guided onboarding.Guided pilotCapture a serious enquiry with the right business context.Trades routeA practical path for appointment-led local service businesses.Owner-managed routeA practical path for owners who need daily visibility and control.

Before launch

Review and publish safely

Use these pages internally before recording or deploying so route links, copy, safety notes and share previews stay consistent.

Launch kitShare copy, route map, launch checklist and product wording.Readiness centreFinal route, mobile, conversion and demo-safety checklist.Deployment runbookFinal local checks, Git handoff, Vercel deployment and smoke-test order.

Source-of-truth handoff

Add these notes to the active project source set after deployment.

These points record what changed in the public website and how the animated demo system should be treated in future chats.

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.

Launch routes added

The public website now includes platform overview, features, animated demos, product story, use cases, comparison, FAQ, pricing, pilot, recording guide, launch kit, readiness centre and deployment runbook routes.

Deployment rule

Run pnpm lint and pnpm build locally before deploying. Vercel deployment should happen after final route, metadata, pilot-form and social-image smoke checks.