Launch Playbook for Career Changers: Make a Launch Double as Proof
A career changer’s launch has two audiences: users and the people who might hire you. Choose a project in the field you are leaving, because you know its real problems, ship something small that strangers actually use, and document what you decided and changed. A case page with real replies reads as proof of skill, and no launch can promise a job.
Who is your launch really for?
A maker with a decade of experience in the new field can launch a product and let the work speak. You cannot lean on a CV in that way, so your launch has to carry a second job: it is evidence that you can take something from nothing to strangers’ hands. That changes what you build and how you write about it.
Decide at the start which result matters more. If it is a job, optimise for a clear case page and a small, finished product. If it is a business, optimise for users and revenue, and let the case page be a side effect. Most career changers want the first and quietly hope for the second, which is fine, but your plan should name the one you are protecting when time runs short.
Why should the project come from your old career?
Because you know the daily irritations that outsiders do not. A former nurse knows which handover step gets lost, a former teacher knows what a Sunday evening of lesson planning feels like, and a former accountant knows what is retyped between two spreadsheets. That knowledge is the one asset a newcomer holds that a seasoned developer cannot copy.
- Write down ten annoyances from your last role, each in one line, starting with “I had to…”
- Circle the ones you could fix with a small tool that one person can use alone, without a company signing up.
- Check each against the board. Browse education ideas and jobs and careers ideas to see whether others have already described the same problem and how they phrased it.
- Pick the smallest. A finished small tool teaches more than a half-built platform.
If building is the new skill, an AI coding tool can shorten the climb; the guide on building an app with an AI coding agent shows how, and portfolio project ideas lists project ideas that show a range of skills.
What goes on the case page?
Keep it to what a stranger can read in two minutes. Use plain facts you can show, and leave out adjectives. If your numbers are small, say so. The outline below works for most small products; replace the brackets with your own details.
[Product name]: [one sentence on what it does and for whom] The problem: [what I saw in my previous job, in two sentences] What I built: [the single main task, with a screenshot] How I decided: [one decision, the option I rejected and why] Who used it: [number of real people, where they came from, one quote with permission] What changed after feedback: [one fix, what I noticed, what I did] What I would do next: [two honest items] Tools and skills used: [list] Link to try it: [URL]
The strongest line is “what changed after feedback,” because it shows you can listen and act, which is what a team hires for. Collect those moments as you go; the launch retrospective template gives a structure for the notes.
How do you run a launch beside a job hunt or a current job?
| Weeks | Product work | Career work |
|---|---|---|
| 1 to 4 | Build the one main task; test with three people from your old field | Update your profile; list the skills the project will show |
| 5 | Publish on a free board such as the launch board; reply daily | Start applying with the live link, even if it is small |
| 6 to 8 | Post in one community of your old field; fix the top issue | Send the case page to two people who might forward it |
| 9 to 11 | Write the case page; tidy the README or product page | Apply with the case page attached; ask for feedback on it |
| 12 | Review what users and interviewers asked about | Decide the next project from those questions |
The ninety-day launch roadmap covers the product side of this schedule in more detail. Do not wait until the case page is perfect before you apply; a live link early is worth more than a long-planned portfolio.
What undermines a career changer’s launch?
- A tutorial clone. The to-do list and the weather app are easy to recognise and say little about you. A project from your own field is not generic.
- Overclaiming. Say what you built and what the tools did. If you used an AI assistant, say so and say what you checked yourself.
- An unfinished platform. One finished tool with real users beats three that almost work.
- Silence after posting. Replies show how you work with people, which is part of what you are proving.
Frequently asked questions
Can a launched project help me get a job in tech?
It can be evidence, but nobody can promise a job. A small finished product with real users and a case page that shows decisions and changes after feedback gives a hirer something concrete to discuss. Use it alongside applications, not instead of them, and keep claims modest and checkable.
What project should a career changer build?
Pick a problem from your previous field, since you know it better than a newcomer to that field could. List ten annoyances from your last role, choose a small one that one person can use alone, and build only the main task. Specific, domain-based tools stand out from tutorial clones.
Should I mention that I used AI tools to build it?
Yes, briefly and factually. Say which tools helped and what you reviewed or decided yourself. Hirers usually care about judgment: what you chose, what you rejected and what you fixed after feedback. Overclaiming is the real risk, so describe the process accurately.
How many users do I need for the project to count?
No threshold exists. A handful of real users, a quote you have permission to use and a visible change you made because of their feedback is enough for a case page. State the actual number plainly, even when it is small, because honesty reads better than an inflated figure.
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.