The problem
Launch day has a hundred small jobs: watch the listing, watch the code pool, answer fast, and post a closing update that does not exaggerate. I wanted the numbers handled by something that would only report what it could verify.
The result
The launch ran on 6 October. The pool grew from 232 to 247 active codes across the day, and the closing post used only those verified numbers. The listing was never featured, and the agent told me plainly that only my own maker view could show its real state, rather than inventing a reason.
Questions about this workflow
What does this workflow do?
Live pool checks and verified numbers only, through a full Product Hunt launch day.
What prompt does this workflow use?
Read the pool live, twice, before quoting any number. Build the closing post only from launch day figures. If something about the listing looks off and you cannot verify why, say so instead of guessing.
How do I use this workflow?
Copy the prompt from this page into Muse and adjust the details to your situation. The result above is what the author got. Every workflow here is free to use; you just need access to Muse, and if you do not have an invite yet you can claim a community code on the homepage.
Report this workflow
Be one of the first to post your Muse workflow here. Add your own and become the person people follow.
Discussion
No comments yet
Sign in to join the discussion