The founding artifact is not a garage or a napkin. It is a Starbucks that G. Satish and Prabu Ekambaram still pass. Years after they had worked together at an enterprise-software company Satish co-founded, the two former colleagues sat down over coffee and began pulling on an old irritation. They had delivered large systems to enormous companies. They knew exactly what those systems could do. They also knew what happened after the contract was signed: deployments grew long, budgets grew anxious, users endured training, and daily work bent itself around the software.
Their question was plain enough to sound almost impolite: “Is there a way to do enterprise software differently?” The emerging combination of cloud computing and mobile devices suggested an answer. Instead of sending field observations through layers of paper and back-office entry, a mechanic, inspector, or technician could record the work where it happened. Instead of asking a crew to learn the software company’s process, the product could be configured around the crew’s own forms and routines.
That coffee-shop conversation became Connixt, founded in 2015 with Satish as chief executive and Ekambaram as chief technology officer. The pair chose a corner of technology largely invisible to ordinary consumers: the inspections, work orders, parts, photographs, approvals, and compliance records that keep heavy assets alive. There is little glamour in a preventive-maintenance checklist. There is considerable glamour in a train arriving safely, though the checklist rarely gets invited to take a bow.
“The field is where technology has to prove itself - and that is the standard we hold ourselves to.”G. Satish
An engineer’s useful suspicion
Satish arrived at software through the physical world. He earned a bachelor’s degree in mechanical engineering at the College of Engineering, Guindy, then a master’s in industrial engineering and management at Oklahoma State University. He was elected to the Phi Kappa Phi and Alpha Pi Mu academic honor societies. His later career crossed complex enterprise applications, supply chains, mobility, and big-data analytics, including more than one startup. Machines, processes, and information were never separate subjects for long.
That background helps explain his skepticism toward technology displayed merely as technology. A maintenance system is judged downstream, by whether a person can document a defect on a noisy floor, whether the record reaches the right system, and whether someone can act before a small problem becomes an expensive one. The elegance lies in the chain, not the screen.
Connixt’s answer was iMarq, a mobile-first maintenance suite designed to work with existing back-end systems rather than stage a palace coup against them. The founders kept two early rules: few moving parts, and an almost fussy devotion to end-user simplicity. They described their approach as starting small, building a scalable platform, and perfecting it. In an industry fond of road maps resembling airport departure boards, restraint became a feature.
Restraint did not mean a tiny ambition. Their plan moved from automating transactions, to collecting data from sensors, to creating a connected grid of assets, materials, and crews. The difference was sequencing. Each addition had to serve work already happening in workshops, warehouses, rail yards, and the field.
The clipboard was giving a review
The old clipboard, in this telling, is not a quaint villain. It is a review left by the user. Paper boots instantly. It accepts any handwriting. It has a magnificent offline mode. If crews keep it beside an expensive enterprise system, they are not resisting the future; they are explaining the present.
Satish’s target user might be wearing gloves, standing beneath a vehicle, moving between assets, or working where connectivity comes and goes. Useful features are correspondingly untheatrical: annotating a photograph without leaving a work order, speaking a note instead of thumb-typing, capturing an observation in the user’s first language, and synchronizing later. The app stops feeling like a compliance demand and starts behaving like a tool.
LA Metro gave the argument scale. Its maintenance work spans buses, railcars, tracks, facilities, signals, quality assurance, and environmental compliance. The agency used iMarq to digitize inspection and compliance forms and connect completed work with inventory and timesheet systems. Its published case study reported a 20 percent reduction in labor hours among users, with an agency-wide projection of 400 hours saved per day at 2,000 users.
In 2019, LA Metro nominated Connixt for the METRO Innovation Award, which they won together. In 2021, Metro’s Rail Fleet Services received a Bright Ideas Award for the iMarq deployment across its divisions. The more revealing detail was the implementation method: managers, supervisors, frontline employees, the technology team, and Connixt supplied regular feedback. The software did not descend upon the yard fully enlightened. It listened there.
When a user keeps a workaround, study it before removing it. The workaround may contain a better product brief than the requirements document.
AI, required to show its work
Connixt eventually added iBot, an AI assistant inside iMarq. Satish’s test for an AI feature is sharper than the customary promise to make something faster or cheaper: does it make possible something that genuinely could not be done before? The standard keeps the conversation attached to the technician and supervisor. Asset history, recurring failure patterns, or insight surfaced in the field matters only if it changes what the person can see or do.
A 2026 iMarq release extended that practical line. It developed iBot’s maintenance insights, automated cycle counts and stock adjustments through mobile scanning, strengthened integrations, and added broadcast messages for safety and operational updates. Each feature closes a small distance between the physical asset, the person working on it, and the digital record. None needs a robot voice to seem futuristic.
The rail industry supplied a verdict. iMarq won a 2025 Progressive Railroading Readers’ Choice Award. In 2026, iBot won in two categories, Artificial Intelligence and Existing Product, New Feature. Satish cared about who voted: rail professionals, including customers, working in yards, on lines, and in back offices. In his thank-you note, he promptly tried to give the award away.
“When an industry votes for you, it is telling you that something you built actually mattered to the people doing the work.”G. Satish
He thanked customers for every question, workaround, and missing piece they reported. He thanked partners for the unglamorous labor of making systems speak correctly. He thanked colleagues who stayed late to fix problems and sat in rail yards with technicians rather than assuming they understood the workflow. Pinpoint, a capability inside iBot, had been shaped by customers using early versions in the field. “This award has your fingerprints on it,” he wrote.
The founder outside the company
Satish’s public work extends into the engineering community. He serves as national president of the American Society of Engineers of Indian Origin, whose mission includes mentoring, scholarships, professional networks, STEM careers, and technology exchange between India and the United States. He also serves on Oklahoma State University’s Industrial Engineering and Management advisory board. The pattern is consistent: systems improve when experienced people make their knowledge available to the next person in the chain.
He writes, too, in the conversational register of a founder who has accumulated enough scar tissue to be suspicious of tidy advice. One recent idea is “anti-preneurship,” his term for the social and personal pressure that pulls entrepreneurs back toward safety and respectability before the market has rendered its verdict. It is a useful counterweight to the mythology of the lone, endlessly confident founder. Businesses are built among relationships, expectations, and raised eyebrows.
At a 2023 industry showdown, Satish compressed iMarq into a five-minute live demonstration. Connixt’s account says the demo was laced with quick wit and humor and received warm applause. The anecdote fits. His company works in severe environments but does not speak as if seriousness requires solemnity. Even the founding critique of enterprise user experience used the technical term “sucky.” Precision sometimes wears work boots.
What stayed still
A decade into Connixt, the technology stack has moved from mobile forms toward sensors, predictive analysis, inventory intelligence, and AI. Satish’s subject has barely moved at all. It is still the person closest to the asset. The company now talks about benefits that travel from workshop to back office to boardroom, but the route begins where the wrench turns.
This is the quiet strategic lesson in his story. A product may grow without continuously renegotiating whom it respects. Platforms expand. Interfaces change. Fashion sends everyone racing toward the newest noun. The fixed point can be a human promise: make the shift easier, preserve the crew’s knowledge, and return useful information while there is still time to act.
The Starbucks still exists in the founders’ geography, an ordinary landmark beside an increasingly elaborate business. Somewhere inside that first conversation was the decision that software should fit the work instead of making the work perform tricks. Ten years later, Satish is still asking the product to prove the point - out in the field, where a bad idea has nowhere comfortable to hide.