Next step · What to do next

Review the first week after launch (what to look at and fix)

What you may see

The site is live, what should I check now?

Why this step

The first real visitors find things no test did; a short, structured review turns them into a fix list instead of worries.

Before you start

Do you have analytics, error logs and a way for customers to tell you what went wrong?

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
Review the first week after launch (what to look at and fix)

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
The first real visitors find things no test did; a short, structured review turns them into a fix list instead of worries.

DO THESE STEPS, IN THIS ORDER
1. Collect: visits and sources, which pages people leave, form and order numbers, errors and slow requests, emails that bounced, messages from customers.
2. Compare with what I expected, list the top 10 problems by how many people they affect, and sort them into fix now, this month, later.
3. Fix the "now" items one at a time with tests, and write the lessons into the project notes.
4. Suggest one improvement for conversions (clearer button, shorter form) and how to measure it.
Stop and tell me if what you see does not match a step. Do not skip ahead.

CHECK THAT IT WORKED
- I have a ranked fix list, the "now" items are done, and the notes are updated.
Tell me exactly what I should see on the screen when it works.

DO NOT CHANGE
- Do not make many changes at once.
- 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

Collect: visits and sources, which pages people leave, form and order numbers, errors and slow requests, emails that bounced, messages from customers.
Compare with what I expected, list the top 10 problems by how many people they affect, and sort them into fix now, this month, later.
Fix the "now" items one at a time with tests, and write the lessons into the project notes.
Suggest one improvement for conversions (clearer button, shorter form) and how to measure it.

Do not do this

Do not judge on three days of data.
Do not make many changes at once.

Try another entry