Acordo Systems — 2019–22
A telecom CRM taken from empty repository to production platform
Nearly three years leading the Acordo project end to end: a cloud-native microservices CRM and sales platform used by major telecom companies, designed from the first commit for fault isolation and independent deployment.
The situation
Acordo was a web-based CRM and sales platform aimed at telecom operators — a domain with complicated quoting, complicated billing and very little tolerance for a system that falls over during a sales push.
We were involved from the very beginning, which is the rare and valuable case: the architecture could be chosen rather than inherited.
What we did
We designed and implemented a cloud-native microservices architecture, and led the setup of the cloud infrastructure for file storage and compute. Each service is independently deployable with its own datastore and its own CI/CD pipeline. An API gateway handles ingress, service discovery handles interservice communication, and event-driven messaging is used where it genuinely earns its complexity — not everywhere.
The front-end is React; the back-end is containerised Node.js services covering authentication, customer accounts, pipeline management, quoting, billing and notifications. We also established centralised observability, because a microservices platform without it is just a distributed system you cannot debug.
The outcome
A platform in production with major telecom companies, with the scalability and fault isolation that the architecture was chosen to provide, and an iteration speed that comes from services that can ship independently.
Three years of living with our own architectural decisions is the most useful education available to an engineer. Most of what we now advise clients to avoid, we learned here.
Let’s build something that lasts.
Tell us about the project. If we’re not the right studio for it, we’ll say so — and usually point you at someone who is.