Projects AGo · VitaCRM · BestRoute
The products I build start from concrete processes: a sale that has to be invoiced, a support request that has to be answered, a field job that has to reach the right person. Here I describe the problem each one solved, the decisions I made as CTO and where the real scope ends.
All three grew in stages, with each round of work leaving something running in production. That is the thread: architecture built to hold up the operation, written criteria, and teams using the system every day.
How they connect
Three products, one principle: the data is entered once and moves between areas with traceability intact.
Case studies
Each case is written in three parts: the problem that existed, what I decided as CTO, and how far the real scope goes. No metrics and no promises: only what the product does in the operation.
Business management
The management system that supports the daily operation of a company that sells, buys, stores and collects.
Customer care and CRM
A care platform for teams that talk to customers all day across different channels.
Field service
Coordination of work that happens outside the office, between the person requesting it, the person assigning it and the person doing it.
Architecture and collaboration
What holds these products together is not an isolated metric but a set of decisions the team can maintain without me: understandable architecture, written criteria and deliveries that leave something working.
I work on systems that already exist and with people who are already there. That is why the test of a review is not how much it resembles the latest release, but how well it holds up the next day's operation.
01
Every definition gets written down: what was chosen, what was discarded and why. That way the decision survives team turnover and nobody has to reconstruct it when someone new joins.
02
I prefer the standard and the explicit over the unique piece only its author understands. A system another developer can read is a system the company does not lose.
03
Scope is split into chunks that can be used. Each stage leaves something in production and a clear point to decide whether to continue, adjust or stop.
Conversation
Most of the projects I work on do not start from zero: they start with an ERP that carries too much, a CRM nobody fills in, or two systems that should talk to each other and do not. If that is your case, one conversation is enough to know where to begin.
And if what you need is outside my area, I will say so and point you in the right direction.
To get started