Call coaching

Live · Commit

↩
Alpha ↗View site ↗

Live lane

Live venture — request a change cycle to reopen the Refinery.

Change request open — continue in the linked Refinery project.

Live · 100% of journey

Idea → Live
✓Idea Capture
✓Build Plan
✓Refinery
✓Tools & DB Prep
✓Git Prep
✓Prebuild Review
✓Build Run
✓Beta / Progress Testing
✓Deep DB Review
✓Subsystem Readiness
✓Go Live Review
✓Live Management

Your next step

Live operations

A live venture needs an active feedback and iteration loop to stay healthy.

Chief of Staff

A live venture needs an active feedback and iteration loop to stay healthy. Keep post-launch monitoring active. Keep the user feedback loop running. Maintain the next-iteration backlog.

How to do it

  1. 1.Keep post-launch monitoring active.
  2. 2.Keep the user feedback loop running.
  3. 3.Maintain the next-iteration backlog.
All steps & checklists

Operational Flow

Guided delivery path from idea to live operations. Current lane: Live.

Idea → Refinery

Idea Capture

Capture the idea, intent, and measurable outcome.

Done
  • North star statement is clear
  • Success metrics are defined

Build Plan

Turn idea into an implementation path and milestones.

Done
  • Phase 1 scope is defined
  • Milestones and dependencies captured

Refinery

Finalize the guided pass before handoff to build lane.

Done
  • Review gate is complete
  • Push-to-testing rationale recorded

Testing / Beta Build Ops

Tools & DB Prep

Prepare data model, services, credentials, and operational tooling.

Done
  • Dedicated Supabase project provisioned (Dewey)
  • Database schema/migrations are ready
  • Service credentials and env vars are configured
  • External integrations are staged (APIs, webhooks)

Git Prep

Provision the project repository, then set branch strategy and PR checks.

Done
  • Dedicated project repository provisioned (GitHub Gary)
  • Branch and merge strategy agreed
  • Preflight checks pass (format/lint/test gates)
  • Release notes or change log started

Prebuild Review

Final review before entering build execution.

Done
  • Scope lock confirmed (no new feature creep)
  • Acceptance criteria are frozen
  • Owner sign-off captured for full build run

Build Run

Execute the full build and integration pass.

Done
  • Build run initiated
  • Build and automated checks complete successfully
  • Build artifacts are published and accessible

Beta / Progress Testing

Validate the build on the designated beta URL.

Done
  • Beta URL is assigned (e.g. example.pufu.ai)
  • Smoke tests pass on beta URL
  • Operator acceptance testing is complete

Deep DB Review

Verify migrations, integrity, and performance before live.

Done
  • Migration integrity verified
  • Backfill and data integrity reviewed
  • Rollback and restore plan is documented

Subsystem Readiness

Confirm every critical subsystem is release ready.

Done
  • Dashboard layer readiness confirmed
  • Backend/services readiness confirmed
  • Frontend/UI readiness confirmed
  • Stripe/payment readiness confirmed
  • User/auth management readiness confirmed
  • Marketing/comms readiness confirmed

Go Live Review

Final go/no-go gate for production launch.

Done
  • Risks and mitigations reviewed
  • Monitoring/alerts are configured
  • Final launch approval is captured

Live Management

Live Management

Operate, observe, and iterate post-launch.

Done
  • Post-launch monitoring cadence active
  • User feedback loop is active
  • Next iteration backlog is maintained

Full Lifecycle Map

✓ Idea Capture

✓ Build Plan

✓ Refinery

✓ Tools & DB Prep

✓ Git Prep

✓ Prebuild Review

✓ Build Run

✓ Beta / Progress Testing

✓ Deep DB Review

✓ Subsystem Readiness

✓ Go Live Review

✓ Live Management