01 / Offer
What evidence says the offer is ready to meet customers?
Write one sentence naming the customer, the problem, the offer, the price and the outcome you can actually deliver. Then put it in front of people who match the intended customer. Record objections in their own words. Interest from friends and impressions on a launch post are weaker than a buyer asking for a quote, making a reservation or paying under stated terms. The level of evidence needed rises with the cost and risk of the promise.
Launch a narrow version if that is the honest way to learn. A limited city, product range or service window lets the team observe real behaviour while keeping operations manageable. Tell customers what is available now. Never label an unfinished capability as live just because the roadmap includes it.
02 / Transaction
Can the team complete one transaction end to end?
Run a rehearsal using a test customer or a carefully controlled first order. Begin at the discovery channel and follow the journey through enquiry, quote or checkout, payment, confirmation, production or service delivery, support and refund or resolution. Name a person for each handoff. Record where data is copied manually and where a customer could be left waiting without an owner.
Reconcile the transaction after delivery. Does the cash received match the price, taxes, fees and refunds recorded? Does inventory or service capacity reflect what was committed? Do support messages reach a monitored inbox? A polished landing page can conceal a failed payment, an unstaffed phone line or a supplier who has not accepted the specification.
| Gate | Evidence to inspect | Stop condition |
|---|---|---|
| Offer | A buyer understands price, scope and timing | Material terms are still ambiguous |
| Transaction | Test order or enquiry reaches an owner | Payment or lead disappears |
| Delivery | Supplier or team meets the stated promise | Capacity or quality is unproven |
| Support | A failed case receives a response and resolution path | No accountable responder |
| Money | Cash, fees, tax treatment and refunds reconcile | Unexplained difference remains |
03 / Permissions
Which approvals and claims must be checked before launch?
Identify the legal entity, place of operation, product or service category, workforce and sales channel. Those facts determine which registrations, licences, tax obligations, labelling rules, data practices and advertising claims may apply. Assign each requirement an owner, a source, a status and a date. Do not copy a generic internet list as though it covers every Indian state, category or cross-border transaction.
For India, the National Single Window System offers a 'Know Your Approvals' route for central and state approvals. Its own FAQ says the output is indicative and should be independently assessed. Use it to build the question list, then verify the actual requirement with the relevant authority or qualified adviser before making a regulated offer.
04 / Launch control
How do you decide when to expand or pause?
Set a small number of launch measures before opening the channel: successful transactions, delivery on the promised date, unresolved complaints, gross margin after direct costs, and time to resolve an exception. Choose a threshold at which the team will pause promotion or new orders. A stop rule protects customers and keeps the first week useful as research rather than an unbounded stress test.
Hold a daily review during the initial window. Separate a demand problem from a fulfilment problem. If buyers do not understand the offer, improve the proposition and language. If they buy but delivery fails, slow acquisition and repair the operating chain. Document the decision and owner after each review. Expand only after the business can repeatedly honour the narrow promise.