Next step · What to do next

Plan launch day and the first week

What you may see

I am going live soon and want a calm plan

Why this step

A small, planned launch (a few friendly customers first) finds the surprises when they are cheap to fix.

Before you start

Is the production checklist finished?

The prompt for this step

What you type here never leaves your browser. The search runs on this page, and nothing is sent to a server or to an AI.

Any error or warning you see now

What you have now (tool, framework, where it is hosted)

Kept only in this browser, on this device. Keys and passwords are removed before anything is saved.

Prompt language

You are a senior engineer and careful product advisor who builds small business websites and apps, and explains every step to people who are not developers. I am not a developer, so explain every step in plain words and tell me exactly which button, menu or command you mean. If you are not sure about something, say so; do not guess.

WHAT I WANT NEXT
Plan launch day and the first week

ANY ERROR OR WARNING I SEE NOW (write "none" if there is none)
[paste the exact error here]

WHAT I HAVE NOW (the tool I used, the framework, where it is hosted)
[write in a few words what you did before it happened]

WHY THIS STEP
A small, planned launch (a few friendly customers first) finds the surprises when they are cheap to fix.

DO THESE STEPS, IN THIS ORDER
1. Write a launch plan: a soft launch to 5 to 10 friendly people with a short feedback form, a list of what to watch (errors, forms, payments, speed), and who is on call.
2. Prepare the announcement texts in English and Arabic, with the correct link and the share preview checked.
3. Plan the first week: daily check of logs, orders and messages for 7 days; a list of quick fixes; a day to review analytics.
4. Prepare a rollback plan and a simple "we are fixing something" page.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- The soft launch finishes with a short fix list, and the public announcement goes out only after those are fixed.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not announce widely on the first day.
- Anything I did not ask about: the design, the text, other pages, other settings or the data.
- Do not delete files, data or branches, do not reset or force-push, and do not rewrite history, unless you first show me exactly what would be lost and I say yes.
- Do not paste, print or ask me to paste a password or secret key into this chat. If one is needed, tell me which settings page of the right service to store it in.

WHEN YOU FINISH
Explain in simple words what you changed (file by file or setting by setting), why you changed it, and how I can undo it.

Paste it into Claude, ChatGPT, Gemini or Cursor, then follow what it says.

After you tried it, did it work?

Steps

Write a launch plan: a soft launch to 5 to 10 friendly people with a short feedback form, a list of what to watch (errors, forms, payments, speed), and who is on call.
Prepare the announcement texts in English and Arabic, with the correct link and the share preview checked.
Plan the first week: daily check of logs, orders and messages for 7 days; a list of quick fixes; a day to review analytics.
Prepare a rollback plan and a simple "we are fixing something" page.

Do not do this

Do not make big changes during the first days without a rollback.
Do not announce widely on the first day.

Try another entry