Mandala Chart for Launching a Side Project
Side projects rarely die from bad ideas. They die from a scope that keeps growing, evenings that run out, and a launch that keeps moving to “next month”. A Mandala Chart keeps the whole project on one page, so you can see what is really needed for version 1 – and what isn’t.
This example aims to launch a small, useful product and reach the first 100 users, working a few hours a week next to a job. It fits apps, websites, newsletters, small tools and digital products.
The order of the themes matters. Start with the people you are building for and keep version 1 small; design, building and launch come after. If you only have one evening this week, spend it talking to potential users.
The eight themes, and why they are there
1. Problem & users
A side project that solves a real problem for a specific person is easier to build, explain and launch. Talking to a handful of users is the cheapest way to find that problem.
- One-sentence value proposition
- Interview 5 potential users
- Describe one specific target user
- List how they solve it today
- Pick a problem I have myself
- Find 3 places online where they gather
- Collect their exact words
- Check if people search for it
2. Scope
Limited evenings are the biggest constraint of a side project. A small, fixed scope and a launch date are what get it shipped.
- Max 3 must-have features
- Write a “not now” list
- Fixed launch date in the calendar
- Use templates and existing tools
- Version 1 in six weekends
- No new ideas until launch
- Define “done” for version 1
- Cut whatever takes over a week
3. Validation
Sign-ups, a prototype and honest reactions tell you whether to keep going before you spend months building.
- Clickable prototype before code
- Landing page with a sign-up form
- 20 email sign-ups before building
- Show the prototype to 5 users
- Watch someone use it without helping
- Ask what they would pay
- Beta group of 10 people
- Change course if nobody cares
4. Design
You don’t need to be a designer. Simple, consistent and readable on a phone is enough for version 1.
- Sketch on paper first
- One clear action per screen
- Ready-made UI kit
- Works well on a phone
- Clear button labels
- Test with someone non-technical
- Two fonts and a few colors
- Pages that load fast
5. Building
Familiar tools and short, regular build sessions keep momentum. Deploying early means launch day is not the first time the thing runs live.
- Use tech I already know
- Weekly milestones
- Deploy from the first week
- Automatic backups
- All tasks on one board
- Fix bugs before adding features
- Short README for future me
- Two fixed build sessions a week
6. Launch
Nobody finds a product by accident. Plan where the first users will come from before launch day, not after.
- Post in 2 relevant communities
- Launch on a product launch site
- Email the waitlist on launch day
- Write a launch blog post
- Share the build story on social media
- Ask 5 friends to share it
- Submit to relevant directories
- Personal message to every beta user
7. Pricing
Even if the project starts free, deciding how it could pay for itself early shapes what you build and who you build it for.
- Decide: free, paid or freemium
- Look at what alternatives charge
- Start with one simple price
- Take payments via an existing provider
- Free trial or free tier
- Ask early users to pay
- Cover running costs first
- Raise prices for new users later
8. Metrics
After launch, a few honest numbers tell you whether people use what you made, and what to improve – or when to stop.
- Track sign-ups weekly
- Measure weekly active users
- One metric that matters most
- Feedback button inside the product
- Monthly review: keep, change or stop
- Find where users drop off
- Privacy-friendly analytics
- Public changelog
Tips for making it your own
- Put your project name in the center once you have one – it makes the chart feel real.
- Review the “Scope” block every week. If something new gets in, something else has to go out.
- When the side project starts earning money, look at the starting-a-business chart for the next stage.
Questions
How long should a side project take to launch?
Aim for six to eight weeks for a first version. If it will take much longer, the scope is probably too big for a first launch.
Do I need to validate a side project before building it?
A little validation saves a lot of time: a few user conversations and a landing page with a sign-up form show whether anyone cares before you build.
How do I find time for a side project?
Fixed sessions work better than “when I have time” – for example two evenings a week and one weekend morning, protected in your calendar.
Related templates
New to Mandala Charts? Read how to make a Mandala Chart, or browse all templates.