I'm building Clipflow while also building Agape. I wouldn't recommend taking on two things of that scale at the same time.
The retreat isn't just a building project I can leave in the background. There are roads, water, power, finishes and plenty of decisions that need attention. Then there is the business of marketing and operating the place.
Clipflow needs attention too. Customers, product decisions and the work of finding people who want to use it don't pause because something on the site needs sorting out.
I started the property project before Clipflow, so I have to work with the situation as it is. There have been useful connections between them. Documenting Agape has helped me learn content, and some of that learning feeds the software business.
But I don't want those benefits to hide the cost. I could give Clipflow more attention if I had fewer competing demands. Both projects can be exciting while the combination still stretches me.
It's something I think about when another promising idea appears. A side project can look quick from the outside, particularly when you're frustrated with the current business. Then you start doing it and discover how much work it contains.
I've suggested putting those ideas on a list and giving them some time before acting. That gives you a chance to look again when the frustrating meeting or difficult week has passed.
A new opportunity deserves attention, but so does the work you've already committed to. I have enough evidence in my own calendar that another business rarely stays small just because you first called it a side project.
