Prelaunch operating system

The exact process MenuEdge should run before public launch.

This page is the company playbook in public form. It shows prospects how MenuEdge works and gives the team a concrete sequence for capture, qualification, pilot setup, proof, and expansion.

Capture

Owner: Founder or growth lead

Review every new pilot request daily.

Tag the submission by urgency, order volume, and the core operating pain.

Reject generic or low-context leads quickly to protect time.

Target SLA

24 hours

Keep this stage tight. Long gaps make pre-launch momentum collapse.

Qualify

Owner: Founder + operator

Prioritize teams launching within 30 days or actively firefighting menu ops.

Confirm they run multiple brands or meaningful delivery volume.

Prepare a launch-fit call only when the workflow problem is obvious.

Target SLA

48 hours

Keep this stage tight. Long gaps make pre-launch momentum collapse.

Pilot setup

Owner: Product + ops

Load the first 1 to 3 brands, current menu structure, and pricing assumptions.

Create the first launch board and competitor watchlist.

Define the decision-makers and weekly review rhythm before kickoff.

Target SLA

10 business days

Keep this stage tight. Long gaps make pre-launch momentum collapse.

Prove value

Owner: Founder + customer lead

Track launch preparation time, launch errors avoided, and pricing issues found.

Use one weekly readout with clear next actions.

Convert proof into rollout scope, not vague enthusiasm.

Target SLA

First 2 weeks of pilot

Keep this stage tight. Long gaps make pre-launch momentum collapse.

Convert and expand

Owner: Founder

Turn the pilot into a broader rollout with named brands and dates.

Use the same launch system for the next wave of brands.

Archive weak-fit leads and protect the early product roadmap.

Target SLA

Immediately after proof

Keep this stage tight. Long gaps make pre-launch momentum collapse.

Qualification scorecard

What makes a lead worth piloting?

Launch urgency

High score if a menu or price change is already scheduled in the next 30 days.

Operational complexity

High score if the team runs several brands, ghost kitchens, or multiple platform menus.

Commercial upside

High score if pricing discipline or launch speed has clear revenue impact.

Access to proof

High score if the team can provide menus, prices, and a real launch calendar quickly.

Launch checklist

What was built in this repo

Lead capture form is live and storing qualification fields in PostgreSQL.

Public homepage explains the launch problem and the pilot outcome clearly.

Public playbook exists so prospects understand the process before a call.

Database migration adds company, monthly volume, priority, stage, and timeline fields.

A CLI summary script exists to review the funnel every week.