Freelancing was going fine. That's the part people don't expect to hear. I wasn't struggling to find work, wasn't burnt out on bad clients, wasn't desperate for a change. I built Devinsol anyway, on purpose, while the freelance version of my career was still working.
The ceiling nobody points out
Freelancing has a hard ceiling built into it: you're trading hours for money, and there are only so many hours. I could raise my rate, sure. I could get more selective about clients. But the fundamental math didn't change. My income was capped by my own time, no matter how good I got.
Devinsol wasn't about escaping freelancing because it was bad. It was about building something that didn't have that ceiling baked into its structure from day one.
What actually pushed me to do it
Two things converged.
First, I kept getting the same kind of client request: not "can you fix this bug" but "can you architect and own this whole system." Bigger scope, longer relationships, more trust required. Freelance platforms and a personal invoice don't communicate that kind of capability well. A consultancy name does, even when it's still just me behind it.
Second, I wanted to build things that outlasted a single contract. Trusts Advisor, a SaaS platform I built for a client, came out of exactly this shift. That kind of project needs a business behind it that can commit to ongoing architecture decisions, not a freelancer juggling five unrelated gigs at once.
What actually changed once I did it
Not everything. I want to be honest about that, because the "I started a company and everything changed overnight" narrative is mostly fiction.
What changed: Clients treated the engagement differently. A consultancy implies process, continuity, and accountability beyond one person's calendar. I started getting asked for retainers instead of one-off projects, which is a direct result of how Devinsol was positioned, not just my skill level.
What didn't change: It was still me writing most of the code, at least at first. The name change didn't add hands. It changed how the work was framed and sold, which mattered more than I expected it to.
The mistake I almost made
I almost over-built the "agency" version of this before I had the client base to justify it. Nice branding, a services page listing things I hadn't actually delivered yet, language written for a team of ten when it was me and a laptop.
I pulled back and kept Devinsol's positioning honest to what it actually was: a focused consultancy built around real architecture experience, not a scaled agency pretending to be bigger than it was. Clients respect that more than inflated positioning, and it's easier to actually deliver on.
What I'd tell a freelancer considering this move
Don't start a consultancy to escape freelancing you're unhappy with. Fix the unhappy freelancing first, or you'll just rebrand the same problems under a company name.
Start it when you notice the shape of the work you want has outgrown what a freelance profile can credibly represent. That's the actual signal. Mine was clients asking for ownership, not just tasks. Yours might look different, but it'll be specific like that, not vague dissatisfaction.
The bottom line
Devinsol exists because the work I wanted to do needed a structure bigger than a personal invoice, not because freelancing failed me. That distinction matters if you're thinking about making a similar move. Build the thing your actual client relationships are asking for, not the thing you think a "real business" is supposed to look like.
Suggested internal links: Link to Day 10's "5 Lessons From My First Year" and Day 6's client SaaS case study.
CTA: Follow along for the real, unpolished version of building a consultancy solo.