Launch Playbook for Freelancers: A Product Beside Client Work
A freelancer should launch a product in the gaps between client projects and build it from something clients keep asking for. Schedule the public launch for a lighter month, tell clients only what you are free to tell, check your contracts for who owns the work, and judge the product by whether it earns what your slowest freelance months do.
Where do a freelancer’s launch hours come from?
Your calendar is set by client deadlines, and those move. Instead of promising a fixed number of weekly hours, read your pipeline, and choose the launch stance that matches it. The mistake to avoid is launching in the middle of a deadline-heavy fortnight, then answering a first visitor three days late.
| Pipeline right now | What to do with the product | What not to do |
|---|---|---|
| Full, with deadlines in the next fortnight | Keep it private; write the page and test with one friendly user | Publish and then disappear for days |
| Normal, with a gap coming | Publish on a free board and reply daily for the first week | Add a second launch place in the same week |
| Light, between projects | Run the full two-week push: post, reply, fix, measure | Spend the gap polishing features nobody asked for |
A side-project checklist is useful here, because a freelancer’s product is a side project in the literal sense: it gets whatever time the paid work leaves.
How do you find the product inside your client work?
Look for the thing you build or explain for the third time. A freelance designer who writes the same onboarding email for every client has a template. A developer who sets up the same booking calendar integration has a small tool. The signal is repetition combined with a client who would pay to skip it.
- List the last five jobs and underline any step you did almost identically each time.
- Ask two past clients whether they would use a ready-made version, and what they would want changed.
- Offer the manual version first at a clear price. If someone pays for the hand-made version, you have learned what to automate, and you have your first customer.
The ideas that other people post but will not build can also seed this: skim the jobs and careers ideas and productivity ideas for problems that match what you already know how to solve.
What must you check before you use client work as raw material?
Three checks, before any public post, because each can turn a good idea into an argument:
- Who owns what you made? Many contracts assign the finished work to the client. Reusing a pattern you invented is usually different from reusing their code, their data or their design. If you are not sure, ask the client in writing, or ask a lawyer. We cannot give legal advice.
- Is anything confidential? Do not use client names, screenshots or numbers in your launch material without permission. Build your examples from invented data.
- Does the product compete with a current client? Tell them early, kindly and plainly. A client who hears it from you stays; one who finds out from a launch post may not.
How do you keep the launch from hurting paid work?
Separate the two clearly. Use a different email address for the product, and put a stated response window on the page, such as “I reply on weekdays.” Block two short slots in the day for product replies and keep them. A client email and a product comment are both urgent in the moment, and treating them equally is how a launch eats a billing week.
Resist the pull to promise support you cannot give. Free users do not hold a contract with you, and the page should say what you will and will not answer. When you publish on the free launch board you state a pricing model in the form, and because a published launch is final, choose the model you are ready to honour for a while.
What does a four-week plan look like around billable weeks?
- Week one, a billable week: write the one-sentence description and the page, in short evening sessions. Nothing public yet.
- Week two, a light week: publish, and reply daily. Message your two past clients and one new person who fits.
- Week three, a billable week: reply twice a day, fix the single most reported problem. No new channels.
- Week four: compare visits, replies and anyone who paid. Decide whether next month is another push or a pause. The thirty-day launch plan shows a version with more detail.
When should the product replace the services?
A workable decision rule is to compare against your own history. When the product has earned about what your two slowest freelance months earned, for three months running, you have a base to reduce client work against. Before that, treat it as a second income stream and keep both. The guide to making money from an app covers models, and the first paying customer playbook covers the first sale.
Frequently asked questions
Can a freelancer launch a product while taking client work?
Yes, if you launch in a lighter stretch of your pipeline and set a stated reply window on the page. Use a separate email, block two short daily slots for product replies and avoid adding new channels during a deadline-heavy fortnight. The product gets whatever time the paid work leaves.
Who owns a product built from client work?
It depends on your contracts, and we cannot give legal advice. Many contracts assign finished work to the client, though reusing a general pattern differs from reusing their code or data. If you are unsure, ask the client in writing or consult a lawyer before you publish.
Should I tell my clients about my product?
Yes, particularly if it competes with something they pay you for. Tell them early and plainly, and do not use their names, screenshots or numbers in launch material without permission. A client who hears it from you is likelier to stay than one who finds it in a public post.
When can I stop freelancing for my product?
A reasonable test is when the product has earned roughly what your two slowest freelance months did, three months in a row. Before then, keep both. The point is to reduce risk, not to prove commitment, and the rule uses your own history instead of someone else’s numbers.
Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.