The Point Where a Side Project Stops Being a Side Project

There wasn't a single moment we can point to. No launch, no revenue milestone, no decision meeting where we said this is real now. What we have instead is a rough sense that somewhere between the second product and the fourth, ShellRick Tech stopped being something we did after work and started being something we scheduled work around. Neither of us noticed the switch while it was happening.

That's worth being honest about, because most of what gets written about side projects treats the transition as a deliberate choice: you decide to go all in, you pick a date, you make the leap. Ours didn't look like that at all. It looked like six months of small decisions that quietly added up to something we hadn't planned for.

Looking back, there were markers. We started saying no to weekend plans without discussing it, because Saturday morning had become the block where Sorted Nexus actually got built. We started keeping a shared list of what needed doing next, not because we decided to run it like a real company, but because we kept forgetting what we'd agreed to the week before. Neither of those felt significant when they happened. They just felt like the practical thing to do.

The clearest marker, in hindsight, was that we stopped asking each other whether we still wanted to keep going. Early on, that question came up naturally every few months: is this still worth the weekends. At some point it stopped coming up, not because we'd answered it, but because the answer had become obvious enough that asking it felt strange.

The honest shift wasn't in how much time we spent. Plenty of hobbies eat a full weekend without becoming anything more than a hobby. What changed was that other people started depending on the outcome. A customer on Sorted Nexus expecting an invoice feature to keep working. A KeyForge user who'd bookmarked it as part of their actual workflow. Once someone else's Tuesday depended on something we'd built, the project had a kind of weight a side project doesn't carry, whether or not we'd formally decided to take it seriously.

That's a different definition than the one most advice assumes. Most guidance about "knowing when to go full-time" is about revenue thresholds and runway. Ours was less about the number and more about the fact that stopping had stopped being a neutral option. Walking away from a product with paying customers isn't the same as shelving a project nobody's using yet, and we crossed that line before we'd consciously registered it.

Part of it is that each individual step looked small enough to not require a decision. Adding a second product wasn't a strategic bet, it was Quiz Bru doing well enough that a second idea seemed worth trying while the first one was stable. Adding a third followed the same pattern. None of those felt like the moment things got serious, because each one, taken alone, was genuinely low stakes.

The other part is that we were both still working full time throughout, so the external signals that usually mark this kind of shift, quitting a job, announcing a launch, were never going to happen for us the way they do for someone going all in on one product. Without those markers, there was nothing forcing either of us to stop and name what had already happened.

If we were doing this over, the thing we'd pay attention to isn't hours spent, it's whether stopping has become costly to someone other than us. That's a cleaner signal than revenue or time invested, because it shows up early and it's hard to rationalize away. The first time a decision gets made with a customer's dependency in mind rather than our own convenience, that's the real transition point, even if it doesn't feel like one at the time.

We'd also pay more attention to the quiet disappearance of the question "do we still want to do this." Losing that question isn't necessarily a bad sign, in our case it wasn't, but it's worth noticing when it happens rather than only realizing months later that you stopped asking.

We hear a version of this from people we talk to through consulting fairly often: a project that started as an experiment has quietly become load-bearing for their business, and they're only now deciding how to resource it properly. That gap between when something becomes real and when it gets treated as real is common, and it's usually not because anyone was careless. It's because the transition genuinely doesn't announce itself.

If that sounds like where you are with something you've been building on the side, it's worth a real conversation rather than continuing to treat it as still informal by default. Our contact page is the direct way to reach us if you want to talk through what that next step should actually look like.

None of this reads as a complaint. We're glad we didn't wait for a clean, deliberate moment to decide ShellRick Tech was real, because we're not sure that moment would ever have arrived on its own. Waiting for certainty before taking something seriously is a good way to never take it seriously at all. Ours just became real the way most things actually become real: gradually, then obviously, with the obvious part arriving well after the gradual part had already finished.

If you're in the gradual part right now, the honest answer is you probably won't know exactly when it tips over either. You'll just notice, at some point, that you've stopped asking whether to keep going.