Go-Live Research: What Actually Worked
We pushed lucidhive.com to be complete and live — services running, payment processing, real transactions rolling in. This is the post-mortem on what held us back, what unblocked us, and what the next team should know before they start their own go-live sprint.
The Site Was “Live” But Couldn’t Transact
On August 8, 2026, the front page returned 200 OK. The shop, cart, checkout, and login pages all returned 200. WooCommerce was active at v11.0.0, Subscriptions at v9.1.0, Payments at v11.0.0. We had 584 published posts. The Cloudflare tunnel was running. The Docker Swarm stack was healthy at five services, 1/1 replicas. Domain and TLS were solid. The content pipeline was actively publishing — 578 posts with a target of 678 via the SECTOR9 50+50 series push.
But the payment gateway was disabled. WooCommerce Payments: enabled: no. PayPal: enabled: no with a placeholder email ([email protected], never configured). Apple Pay and Google Pay wallet toggles were yes but useless without a connected Stripe account. A customer could add to cart, reach checkout — and then hit a wall. The site looked live but could not transact. This was the rolling in numbers killer.
The research verified this against the live database: woocommerce_woocommerce_payments_settings returned enabled: no. woocommerce_paypal_settings returned enabled: no with the placeholder email. The Apple Pay / Google Pay toggles were enabled but they are child features of the parent gateway — without Stripe connected, they are dead switches.
Blocker #1: No Active Payment Gateway — The #1 Go-Live Killer
The fix was straightforward but required human action: connect a real payment processor. We evaluated three options:
- Option A (recommended): WooCommerce Payments → Stripe account connect. Needs business details, bank account, ~15–30 minutes admin. Most integrated for a WooCommerce stack.
- Option B: PayPal. Needs real email + API keys. Less integrated, more friction for subscription billing.
- Option C: Stripe plugin directly. API keys only, no account link flow. More manual configuration.
After connect: set enabled: yes, turn on test mode, run a $1 test order end-to-end, then flip live. The key insight: you cannot test the checkout flow until the gateway is connected. Everything else in the critical path waits on this. The research showed this as priority #1 because it is a hard dependency — no amount of content, infrastructure, or schema work can compensate for a missing payment gateway.
Blocker #2: Zero Subscription Products
WooCommerce Subscriptions was active (v9.1.0) but unused. Zero products with subscription/service/plan/retainer keywords in the catalog. The entire business model — AI-employee retainers, Lucid Studio plans, T1–T5 tiers — had no sellable catalog entry. The plugin was installed and licensed but the product layer was empty.
Required: create subscription products for the actual offers (Lucid Studio plans, retainers, consulting) with prices. This is not a technical task — it’s a product definition task. The prices, billing intervals, and tier benefits must be decided by the business owner before any code can implement them.
Blocker #3: Products Are Placeholder/Demo Content
Existing products were demo theme content: “Minimal Chair,” “Cup 1/2Oz,” “Dark Watch,” “Wooden Bar Stool,” “Red Chair,” ISSUE#50–53 (magazine). These came with the theme and were never replaced. They are not LucidHive services.
Required: replace/curate the catalog to match the business. This means removing demo products and creating real service products. The catalog is the storefront — if it sells chairs, customers will buy chairs. If it sells AI retainers, customers will buy retainers.
Blocker #4: Checkout Flow Untested End-to-End
Checkout redirected to cart for empty cart (correct behavior), but no test order had ever completed — impossible without a gateway. The flow existed in code but had never been exercised with real payment data.
After gateway connect: full E2E test order with test mode. This means: add to cart → checkout → fill billing/shipping → choose payment method → complete order → verify order confirmation email → verify admin order appears → verify subscription created (if subscription product) → verify customer account created. Only then flip live.
Blocker #5: Registration Flow Unverified
“Complete Registration” page exists (200 OK) but account creation + email verification + WooCommerce account sync was untested. The page renders but the funnel has never been validated. A user could register but the account might not link to WooCommerce correctly, or the verification email might not send, or the password reset flow might be broken.
This is a lower priority than payment but blocks the “rolling in numbers” goal — you cannot have recurring customers if they cannot create accounts reliably.
Blocker #6: Schema/SEO Gap (From Editorial Audit)
Published posts have ZERO JSON-LD. A grep for ld+json returned 0 hits across the corpus. Schema score 0–1 across smoke-tested posts. This hurts search visibility — Google cannot extract structured data, rich snippets don’t appear, the content is invisible to the semantic web.
This one is agent-doable NOW, in parallel — inject JSON-LD Article schema on all published posts. The template exists in the editorial audit; the pipeline can batch-apply it. No owner decision needed, just execution.
The Critical Path to Live (In Priority Order)
- Connect payment gateway (Stripe via WooCommerce Payments) — human action required (business/bank details). Everything else waits on this for actual transactions.
- Create subscription/service products matching the real offers (Lucid Studio plans, retainers, tiers).
- Enable gateway → test order $1 → flip live.
- E2E registration → account → purchase flow test.
- Schema injection (JSON-LD Article) on all published posts (parallel, agent-doable).
- Curate/remove demo products.
What Wasn’t a Blocker (Already Live)
- Cloudflare tunnel (
lucid-cloudflare-tunnelcontainer running) - Domain + TLS (front page 200 over HTTPS)
- Docker Swarm stack healthy (5 services, replicas 1/1)
- Content pipeline actively publishing
- Forum, testimonials, account pages exist
The infrastructure was solid. The content was flowing. The stack was healthy. The gap was purely commercial: the ability to accept money for what we were selling.
Owner Decisions Required
- Which payment processor? (WooPayments/Stripe recommended)
- What are the actual service products + prices? (Lucid Studio plans, retainers, tiers)
- Live launch date target?
The Lesson: Go-Live Is Commercial, Not Technical
Go-live isn’t a technical milestone — it’s a commercial one. A site that returns 200 on every page but cannot process a $1 payment is not live. It’s a demo. The difference between “looks live” and “is live” is one Stripe connection and one test order. Everything else — schema, catalog curation, registration flow — is optimization. The gateway is the gate.
We had the infrastructure. We had the content. We had the stack. We just needed to turn on the cash register.
The research also revealed a meta-pattern: the team knew the gateway was disabled but treated it as a “later” task while publishing 500+ posts, hardening security, building the mesh, and designing the visual language. The hard commercial work was deferred while the comfortable technical work proceeded. The go-live sprint reverses that priority: money first, everything else serves the transaction.
What the Next Team Should Know
- Start with the payment gateway. Not the design system. Not the content pipeline. Not the schema. The gateway.
- Define your products before you build the catalog. Prices, intervals, tier benefits — these are business decisions, not technical ones.
- Test the full funnel with a real (test mode) payment before declaring victory. The redirect-to-cart-on-empty-cart behavior is correct; the payment-completes-and-order-appears behavior is what you must verify.
- Schema is a parallel track. Do it while waiting for Stripe approval. It’s agent-doable and high ROI for search.
- The infrastructure will be ready before the business logic. Plan for that — don’t let perfect infrastructure mask missing commerce.
The universe keeps printing. The cash register just needed to be plugged in.
## Semantic Relationships
– [[lucidhive-com]] — creative system for
– [[woocommerce]] — creative system for
– [[stripe]] — creative system for
– [[go-live-gap]] — creative system for
– [[docker-swarm]] — creative system for
– [[cloudflare-tunnel]] — creative system for
