My Experience Shutting Down a Side Project After 6 Months

Yesterday, I quietly archived a side project I started last winter. It got to around 200 users, but growth completely stalled there.

The problem was that it didn't cost money, but it took a lot of time. I spent 4–5 hours every weekend, so over 6 months that easily adds up to more than 100 hours.

I definitely learned something. Running everything solo from planning to deployment finally made me understand what other teams at work do. Next time, I'm going to build it assuming paid checkout from the start.

by 취준생김씨140

4 answers

The experience of running the whole thing solo from planning to deployment is what stays with you. Facts.

by 초보개발자323 · ▲0

200 users in 100 hours isn’t bad efficiency-wise. But the “next time, with paid conversion in mind” part is a bit iffy. If you’re going to charge, you should have first validated whether this was a problem people would actually pay for. Regretting it six months later is already too late, isn’t it? I think most side projects get shut down because people start by building what they can build, not what would actually sell.

by 궁금한사람239 · ▲0

I wrapped things up similarly. But I didn’t archive it and left the code in place, and later those pieces were really helpful. Don’t delete it completely.

by 호기심천국923 · ▲0

Honestly, isn’t 200 people pretty good? Mine launched and stalled at 12 acquaintances lol. It does feel like a shame that I archived it.

by 호기심천국881 · ▲0