Built by operators. For operators.
Cogens was founded by three people who spent years working inside mid-market businesses — one running revenue, one running finance, one running technology — and kept running into the same problem. The tools existed. The teams were capable. The architecture was missing.
Two principals. Two domains. One shared mandate.
Abhishek leads revenue architecture, Piyush leads financial control. They spent years inside mid-market businesses encountering the same problem: the tools existed, the teams were capable, but the architecture connecting them was missing.
We didn't build Cogens from the outside in.
Before Cogens, Abhishek spent years in sales and revenue operations, managing CRM systems that were sophisticated in isolation and useless in practice — because nothing they captured flowed to the people who needed it most.
Piyush came from the other direction — years in finance and financial control, where month-end close was a ritual of manual reconciliation and cash visibility was always a week behind reality. The data existed somewhere. Getting to it was the problem.
They met while working on a shared client engagement in the UAE — a mid-market trading business that had invested heavily in software and was still running core operations on spreadsheets and WhatsApp groups. The systems weren't the problem. The architecture was.
Cogens was built to solve that problem — not as a technology vendor, but as a systems architecture firm. The work starts before any software is opened and ends only when the business can operate independently of us.
Three functions. One firm.
"We are not a software reseller. We are not an IT vendor. We are a systems architecture firm — and the difference matters."
The principles we don't compromise on.
We design before we build
No tool is opened until the architecture is agreed. Every engagement begins with a system design document — data flows, decision rights, integration points — that the client reviews and approves before implementation begins.
We build for independence
A system that requires ongoing Cogens involvement to function is a system we have not built correctly. Every engagement ends with full documentation, team training, and a handover that allows the client to operate without us.
We measure outcomes, not outputs
We are not paid to configure software. We are engaged to produce business outcomes — faster close cycles, real-time financial visibility, predictable operations. If the configuration does not produce those outcomes, it is not done.
Small by design.
Senior by default.
If the architecture is right, everything else follows.
We take a limited number of engagements at any time to ensure both founders are directly involved in every client system. If you're running a mid-market business in the UAE or GCC and your systems are fragmented, it's worth a conversation.