About GESA
Fourteen years of technical work where being close enough was never the same as being right — told through what changed, and what didn't.
Our story
GESA was set up in Chennai in 2012 to take on people at the start of their careers — most of the first hires were fresh graduates — and to prove that a team built that way could hold a standard the industry expected only from experience.
The early work was LiDAR — classifying point clouds and extracting features for infrastructure clients who would build directly from what we handed over. A missed conductor or a wrong break-line doesn't fail on delivery day; it fails months later, expensively, in the field. So the checking became the discipline the company was built on.
That discipline turned out to travel. Over fourteen years it has carried us from point cloud processing into full OSP fiber engineering, from supporting other people’s software to building our own — all working out of Chennai, delivering for clients across the United States and beyond.
The work has changed and will change again. The standard we hand it over at hasn't. That is the company.
Milestones
The short version of how one LiDAR practice became a seventy-person company working two disciplines.
2012
Set up to do one thing well: technical work where being close enough is not the same as being right. The early work was LiDAR — classifying point clouds and extracting features for infrastructure clients.
2015
The first project delivered at city scale rather than corridor by corridor — and the first time the standard had to hold across an entire network.
2016
The second discipline, formalised — from supporting other people’s software to designing and building our own.
Today
20,000+ miles of corridor digitized and engineered, clients in all 50 US states, some relationships running past a decade.
What our teams do
Neither team reports to the other, sells to the same client, or does the other's work. They share a building, a founding date, and a standard.
Engineering
A corridor comes to us as raw LiDAR and field data; it leaves as classified point clouds, extracted features, and engineering deliverables — pole loading, make-ready, fiber design — ready for permitting and construction. Every deliverable passes through layered QC before it ships, because our clients build directly from what we hand over.
Software
We start by watching how the job gets done today — then design and build around that, not around a feature list. The result is software people pick up without a manual: dashboards, field apps, and data platforms doing work that is not remotely simple underneath.
What we hold each other to
The same standard shows up in how we hire. See what we hold each other to on the Careers page →
By the numbers
Get in touch
Whether it's a project, a role, or just a question about how we work — we're one message away.
