Projects AGo · VitaCRM · BestRoute

Projects built from the operational floor

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

AGo ERP · AGo Next sales, purchasing, stock, collections, invoicing VitaCRM care and tickets BestRoute field service one record, entered once and shared

Three products, one principle: the data is entered once and moves between areas with traceability intact.

Case studies

Three products, three concrete problems

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.

  1. Business management

    AGo ERP and AGo Next

    The management system that supports the daily operation of a company that sells, buys, stores and collects.

    Problem
    The operation was split across spreadsheets and tools that did not talk to each other. Every area kept its own version of the data, and rebuilding the full cycle took time nobody had.
    CTO role
    Define the architecture of the management core, order the data model and decide the sequence of the stages by real operational impact, not by technical novelty.
    Scope
    Business management delivered in stages on a single base: sales, purchasing, stock and collections. AGo Next is the evolution of that core, with the same business rules and the ability to integrate with other products.
  2. Customer care and CRM

    VitaCRM

    A care platform for teams that talk to customers all day across different channels.

    Problem
    Conversations arrived through several channels at once, and there was no single place to see the message, the ticket and the customer history. Follow-up depended on whoever was on shift remembering it.
    CTO role
    Design the platform architecture, define how the channels come together in one record, and set how far to automate without taking control away from the care team.
    Scope
    CRM, tickets and WhatsApp in a unified care panel, with AI-assisted automation for repetitive tasks: classification, base replies and follow-up. Sensitive decisions stay with people.
  3. Field service

    BestRoute

    Coordination of work that happens outside the office, between the person requesting it, the person assigning it and the person doing it.

    Problem
    Requests were coordinated by phone and scattered messages. There was no clear way to know who held each job, what state it was in, or when it had been closed.
    CTO role
    Define the request model, the assignment criteria and the record of every state change, so traceability no longer depended on asking over messages.
    Scope
    Requests, assignment, tracking and closure of field service jobs, with the state of each job visible both to the person coordinating and to the person executing it.

Architecture and collaboration

Architecture decisions that keep the work running

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

Documented decisions

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

Systems that can be maintained

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

Delivery in stages

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

If you are untangling a system that is already running, let's talk.

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

The context
What the company does, how it works today and who uses the system.
The objective
What needs to stop happening, or what needs to start working.
The systems
Which tools are involved and who administers them.