A year into running Devinsol, the lessons that actually stuck aren't the ones I expected going in. I thought the hard part would be technical. It mostly wasn't. Here's what actually taught me something.
1. Client trust is built on communication, not just code quality
I assumed good work would speak for itself. It doesn't, not on its own. Clients who couldn't fully evaluate my technical decisions judged the relationship on something else entirely: how clearly and consistently I communicated progress, risk, and tradeoffs.
The clients who renewed and referred me weren't necessarily the ones who got the most technically impressive builds. They were the ones who always knew where their project stood, without having to ask. That's a communication discipline, not a coding one, and I underrated it badly at the start.
2. Saying yes to everything early was a mistake I had to unlearn
In the first few months, I took on projects outside my actual strengths because turning down revenue felt reckless as a new consultancy. Some of that work stretched me productively. A meaningful chunk of it stretched me thin and produced mediocre results I wasn't proud of.
The lesson wasn't "be pickier from day one," because you genuinely don't have the leverage to be selective that early. It was learning to recognize, faster, when a project was outside my real strengths, and either passing or being upfront with the client about the learning curve involved.
3. Pricing confidence takes real reps to build, not just decide to have
I wrote about the shift from hourly to value-based pricing separately, but the emotional part deserves its own mention here. Quoting a flat fee based on business value, instead of hours, felt uncomfortable for longer than I expected, even after I intellectually understood why it was the better model.
Confidence in pricing came from doing it repeatedly and seeing clients accept value-based quotes without pushback, not from reading about the concept. If you're earlier in this transition than I was, expect the discomfort to outlast your understanding of the theory.
4. Scope creep is a relationship problem disguised as a technical one
Every scope creep situation I ran into in year one traced back to an unclear written boundary at the start, not a client acting in bad faith. Clients weren't trying to get free work. They genuinely didn't know where the line was, because I hadn't drawn it clearly enough upfront.
Fixing this wasn't about being stricter with clients. It was about being more specific in proposals about what's included and what isn't, so the conversation about scope happens before the project starts, not defensively in the middle of it.
5. The work that compounds isn't always the most exciting work
The projects that mattered most for Devinsol's growth in year one weren't always the technically flashiest ones. A client relationship built on solid, unglamorous ongoing maintenance work led to a much bigger architecture project later, once trust was established. I nearly deprioritized that maintenance client early on in favor of more "interesting" new work, and I'm glad I didn't.
Consistency and reliability on smaller engagements often opens bigger doors than chasing the most technically impressive project on your plate at any given moment.
What I'd tell myself starting over
Communicate more than feels necessary, price based on value from the start even when it's uncomfortable, write scope boundaries into every proposal without exception, and don't underestimate the "boring" client relationships. None of this is technical advice. That's the actual surprise of year one: the business of consulting is a different skill set than the engineering, and it deserves the same deliberate practice.
The bottom line
Nobody warns you that the hardest part of running a software consultancy is rarely the software. It's the communication, the pricing, the boundaries, and the patience to let the right relationships compound. Year one taught me that the technical skills got me in the door. Everything else is what keeps clients coming back.
Suggested internal links: Link to Day 2's pricing mistake article, Day 4's Devinsol founding story, and Day 18's scope creep piece.
CTA: Building your own consultancy? Follow along, I share the unfiltered version, not just the wins.