Internal launch desk

Admin shell for the first measurable launch loop.

This path now covers starter-offer provisioning, first-launch analytics, refund-rate visibility, and the operating checks needed to decide whether an offer should scale, revise, or stop.

Commerce status

Starter offer activation

Database configured

No

Database reachable

No

Starter offer live

Not yet

The starter offer is still the narrowest operating path: one seeded product, one sellable offer, one order flow, one refund signal, and one delivery page.

Live offers

Plano SOS Casa Limpa

Seu cachorro voltou a fazer xixi dentro de casa?

R$ 79,00

preview

Open offer

Launch analytics

One reporting path for conversion and unit economics.

This dashboard rolls landing views, checkout progression, purchase, refunds, and payback math into one decision surface for the CEO.

gather more data

Not enough launch signal yet to scale or stop.

Collect at least 50 landing views and 3 paid orders before locking a scale decision.

Current signal: 0 landing views, 0 paid orders.

Landing views

0

Lead capture rate 0%

Checkout starts

0

Checkout completion 0%

Paid orders

0

View-to-paid 0%

AOV

R$ 0,00

Gross revenue R$ 0,00

Refund rate

0%

0 refunded orders

Max CAC

R$ 0,00

Day-0 break-even CAC after refunds, fees, and ops cost.

Current CAC

n/a

Ad spend assumption R$ 0,00

Contribution

-R$ 0,00

Net revenue R$ 0,00

Payback inputs

Tune the launch economics assumptions.

These assumptions are not persisted yet. Use them to pressure-test whether the current launch data supports a scale decision.

Estimated fees

R$ 0,00

Ops cost total

R$ 0,00

Contribution before ad spend

R$ 0,00

Source and campaign cuts

Experiment results by acquisition slice.

No attributed traffic yet. Visit the offer page with `utm_source`, `utm_medium`, or `utm_campaign` to start segmenting experiments here.

UTM validation slice

Read the latest tagged traffic path.

awaiting runtime

Database runtime is not configured yet.

Set DATABASE_URL and DIRECT_DATABASE_URL, then run the first migration before validating tagged traffic.

Landing views

0

Leads

0

Checkout starts

0

Paid orders

0

Refunded

0

Latest tagged slice

No tagged slice has been recorded yet.

Validation URL

Open a tagged offer path

/offers/primeira-oferta?utm_source=meta&utm_medium=cpc&utm_campaign=primeira-oferta-relapse-diagnostico-v1

Required environment variables

NEXT_PUBLIC_APP_URL
DATABASE_URL
DIRECT_DATABASE_URL

Recent orders

No orders yet. Once the starter offer is live, completed checkouts will appear here immediately.

Event taxonomy

Landing view

acquisition

Offer-page impression with referrer and UTM attribution.

Primary metric: Landing views

Lead captured

landing conversion

Visitor submits contact details from the offer surface.

Primary metric: View-to-lead rate

Checkout started

checkout progression

Qualified prospect enters the purchase flow.

Primary metric: Checkout start rate

Checkout completed

checkout progression

Checkout finishes and the app can redirect into delivery.

Primary metric: Checkout completion rate

Order paid

purchase

Revenue event used for AOV, CAC, and payback math.

Primary metric: Purchase conversion

Order refunded

refund

Post-purchase quality signal that reduces net revenue.

Primary metric: Refund rate

Execution queue

1

Provision PostgreSQL and run the first Prisma migration.

2

Implement Stripe checkout session creation and webhook ingestion.

3

Seed the first product and offer pair so the funnel can render from real data.

4

Track page views, checkout starts, purchases, and refunds inside the event model.

Application

Single-codebase launch loop

Public funnel pages, internal operations screens, and API handlers live together so the first engineer can ship fast without service coordination overhead.

Operations

Three environments only

Local, preview, and production provide enough separation to release safely without the drag of a separate staging tier this early.

Data

Commerce plus telemetry

Products, offers, customers, orders, and events are defined together so pricing, checkout, and measurement evolve on the same spine.

Deployment tiers

Local

localhost

Product development, route work, schema iteration, and integration spikes.

Preview

Vercel preview

Every branch gets a production-like review environment before merge.

Production

primary domain

The live funnel, checkout, fulfillment hooks, and operational monitoring.