ROUNDTABLES ★ 23 upvotes 2018

Ask HN: Building a side project that makes money. Where to start?

The Founder's Submission

Direct narrative and submission text authored by @throwaway8891 on Hacker News:

I want to build a side project. Especially, one that makes money. Even if it brings in $100, I feel that it will provide more satisfaction than my current job.

I can code in python with some help.

Can you provide some ideas on where to start? What are some simple things I can build by myself? Any ideas?

Retrospective Overview & Key Insights

Distilled analysis of the business dynamics, operational challenges, and strategic takeaways:

An open Ask HN community consultation from 2018 where @throwaway8891 convened hundreds of developers and bootstrappers to share real experiences, hard numbers, and tactics.

Core Principles for Independent Builders:
1
Participants share raw revenue figures, churn rates, and stack decisions that corporate PR never publishes.
2
Recurring answers reveal that distribution, not coding skill, is almost universally the rate-limiting step in developer businesses.
3
Practical recommendations on bookkeeping, payment gateways (Stripe vs Paddle), and freelance-to-product transitions.
Community Debate Themes:

Hundreds of active indie hackers contributed case studies, pricing heuristics, and pitfalls to avoid when moonlighting on side projects.

Community Discussions & Critical Reviews

High-signal perspectives, counter-arguments, and peer founder insights debated on Hacker News (8 total discussions):

MI @mindcrime Peer Contributor

The archive[1] of the video content from YC's "Startup School" is freely available. There's some really good content there that would probably help you a lot. I'd suggest go through those, and just skip the ones that obviously aren't relevant to where you're at (like the ones on fundraising, hiring staff, etc.). The ones about "product" issues would likely answer a lot of your questions.

The other thing I'd suggest is to read The Four Steps to the Epiphany by Steve Blank - or the follow-on / 2nd Edition, which was re-titled as The Startup Owner's Manual. They're the same book in a sense, but they're different enough that I'd actually recommend reading both eventually. But personally I'd still start with TFSTTE.

[1]: http://startupschool.org/library

SO @soulchild37 Peer Contributor

https://indiehackers.com/products has a list of apps that earns money. If you want to skip through those market research work, you can clone some of the profitable apps there, maybe with your own little twist.

If you are willing to do the market research work, pick an audience (say, python developer, since you are one and understand it most), find out whats their problem (maybe setting ENV? maybe setting up a server to deploy to?) , and start from there.

AR @aregsarkissian Peer Contributor

Start by finding a small group of people that have a problem that you might be able to solve by writing python scripts or a simple web app perhaps built with flask. Joining a few meetups or online forums or looking for problems in your current job may give you an idea of how to connect with these people. Then it is a matter of throwing together the simplest possible app that could address the main issues these people are having and going and talking to them to see if they would pay for it and adjust your product based on their feedback

TM @tmaly Peer Contributor

I would recommend finding an existing market. By that find something that already exists and has paying customers. If they have hundreds of reviews or if there is a forum where the product or service is actively discussed go there. Look for one or two common problems that paying customers have that is not being addressed. Try to make a product that is similar but solves those one or two problems.

Then work your way nicely into the forum and be helpful. Only after some time, suggest your product as a solution.

IN @invalidusernam3 Peer Contributor

This doesn't really answer your questions directly, but it's something that I've learned the hard way over the years: start small and fail early.

Don't spend hundreds of hours on ideas before you know if it will work or not. If your intention is to make money, make the smallest MVP you can to start testing if it has real potential. If it clearly doesn't work, move onto the next idea.

HISTORICAL ERA Cloud & Mobile Era (2014–2019)
COMMUNITY SCORE ★ 23 points
TOTAL DISCUSSIONS 8 comments
TOPICS & TECH STACK: