Why this matters
Once a small shop has a website, the same questions arrive every day: how much is shipping, how long does it burn, can I pick it up, my order arrived broken, do you sell wholesale. Typing each answer from memory takes over an hour a week, and one tired answer can promise a policy you do not have.
Runable writes a help page and paste-ready DM replies from one brief, for a few credits. The two things that make it safe: give it only your real policies with a rule not to guess, and after every edit open the file to check the change is really there. In our run the agent said Done and listed five changes; the file had one.
Practice
Do every step yourself in a practice copy of the real tool. It checks your work, and “Do it for me” finishes any step you get stuck on.
What you’ll build

You help Maya Chen turn Harbor & Pine's repeat customer questions into a one-page help page and five DM replies, with the gaps listed instead of guessed.
You type her policies into Runable's prompt box with a "do not guess" rule, read the help page and the replies, and look at the 11 questions her facts do not cover. You fix a typo and answer three of the questions in one message, catch that the "Done" summary does not match the file, tell it exactly what did not change, check the file again, and export. The screens are real Runable screens from the Free plan, captured October 2026.
What you need
- Nothing to start the practiceThe lesson is a practice copy built from real Runable screens. Harbor & Pine is made up.
- The brief and the messages we sentThe policies, the brief, the fix and the follow-up, ready to swap your own details into.
- A Runable account, to do it for realThe Free plan showed 1,500 credits a day in October 2026. This whole job used 19.
Concepts
Make the agent say "I don't know"
Asked for a help page, an agent fills every gap with something that sounds right: free returns, worldwide shipping, open every day. On a help page that is a promise. Give it only your facts and tell it to list what they do not cover. Ours listed 11 questions, from delivery times to gift wrap, instead of inventing answers.
Check the file, not the summary
After our first fix, Runable said Done and listed five changes. The file had one: the pickup reply. Asked again, it explained that its edits had run in parallel and overwritten each other, rewrote the file, and this time it matched. After every edit, open the file and find each change yourself. If one is missing, name it exactly and ask the agent to quote the new lines back.
Do it for real
Now repeat it in your own account. Tick each step as you go.
Downloads
- Help page brief, fix and follow-up (.txt)The exact brief and messages we sent on 23 October 2026, with what happened after each one.
- The help page Runable wrote for us (.md)The final version after both fixes: 8 answers, 5 DM replies and the open questions.
Quick check
3 questions to check you’ve got it.
1. Your facts say nothing about who pays return shipping. What should the help page do?
- Say returns are free
- List it as a question for you to answer
- Leave returns out
Show the answer
List it as a question for you to answer. A guessed policy is a promise. The brief told Runable to list gaps instead of guessing, and it did.
2. Runable says Done and lists five changes. What do you do next?
- Export it
- Open the file and find each change
- Start a new chat
Show the answer
Open the file and find each change. In our run the file had only one of the five changes until we pointed out the rest.
3. One change is missing. What is the best follow-up?
- "It didn't work"
- Name the exact lines that did not change and ask it to quote the new lines back
- Paste the whole brief again
Show the answer
Name the exact lines that did not change and ask it to quote the new lines back. Specific feedback gets a specific fix, and quoted lines let you check in the chat.
Turn a Messy Client Brief into a Finished Proposal Deck using Runable
Next, a second business and a different Runable tool: turn a messy client email into a finished proposal deck with Slides.
Start module 7 →