From Engineer to Operator: A Field Note on Building DevOne Net

I started DevOne Net in 2020 the way most engineers start consultancies — by accident. A handful of organisations needed work done, I could do that work, and 'consultant' was a more honest job title than 'freelancer'. What I did not understand for the first eighteen months was how different the job of running the consultancy was from the job of doing the engineering.

The first lesson was the unit of work. As an engineer, the unit is the ticket — a discrete change, shipped, reviewed, merged. As an operator, the unit is the outcome — did the customer's business actually get better, and can I prove it. That shift sounds obvious in the abstract and is brutal in practice. It means every engagement now starts with a written outcome and a measurement plan, before any tools are picked, before any code is written. If we cannot agree what success looks like on day one, the engagement does not happen.

The second lesson was that scope is the product. Engineers think the product is the deliverable; operators know the product is the boundary around the deliverable. What we will do, what we will not do, what changes when reality shifts. DevOne Net engagements run on a one-page scope that fits on a screen, gets re-read at every status meeting, and gets formally amended (not silently expanded) when something changes. That single discipline has saved more relationships than any technical decision.

The third lesson was about hiring. The instinct as a technical founder is to hire other technical people first. The reality is that what scales a consultancy is not a second senior engineer; it is a project lead who can hold a conversation with a CFO, write a clear status report, and protect the engineers from scope creep. We did this in the wrong order for our first two years and paid for it in churn.

The fourth lesson was about saying no. The single best business decision I made in 2024 was turning down three engagements that, on paper, looked great. They were well-paid, with respectable logos, and exactly the kind of work we could do in our sleep. The problem was that we could do them in our sleep — which meant they were not stretching the practice, not building new capability, not compounding. Saying no created room to take on the work that actually moved the firm forward. That trade-off does not feel rational until you make it, and then it feels obvious.

Five years in, DevOne Net is still a small firm by design. I do not think the goal is to grow into a 200-person consultancy. I think the goal is to be the operator African organisations call when the engagement matters, when the deck has run out of road, and the work has to actually happen. That is a different ambition. It is the one worth building toward.