Nithish Singh
Founder — software architect
Six years building the kind of system this company sells — ERP and procurement platforms carrying OEM and supplier workflows, data pipelines at Comcast, retail and CPG analytics at NielsenIQ. The person who writes your code is the person who remains accountable once it is live.
Experience and background
Software architect at Adidev Industries since 2023, where the work is manufacturing: ERP and procurement systems carrying OEM–supplier workflows, order lifecycle, sourcing and analytics — architecture, development oversight, QA governance, deployment and delivery, owned end to end rather than handed along. The invoice that disagrees with the goods receipt note, on the front page of this site, is not an illustration picked at random. It is the job.
Before that, data platforms: Comcast's XRM analytics through Tulasea and UST, building the pipelines that pulled scattered sources into one place. Before that, two years at NielsenIQ in Chennai on retail and CPG data — market segmentation, a sales forecasting model, the drivers of brand loyalty. Before that, network engineering at GEE VEE FAB, automating monitoring and maintenance in Python until most of the manual work was gone. Computer science engineering at Adhiyamaan College.
Shipped along the way, among others: procurement tracking and supplier follow-up for an automotive manufacturer, student admission and onboarding for a global education group, a reporting warehouse and reconciliation engine feeding that group's finance team, an internal chatbot, and a booking app that replaced a spreadsheet. Clients are unnamed here for the same reason they are unnamed everywhere else on this site — the agreements make that their call, not ours. Different industries, one task in different clothes: find the manual step between two systems that should already be talking to each other, and remove it.
Doing AI started from a complaint I kept hearing. Companies were paying for AI strategy and getting slides back: a set of recommendations, an implementation roadmap, and no working software at the end of it. The technology was ready. What was missing was anyone willing to build the thing, wire it into what the company already ran, and still be there when it broke on an ordinary Tuesday. So the company is built the other way round. Scope and price are fixed before anyone writes code, the first system goes live in weeks rather than quarters, and it runs inside the tools your team already opens. If I cannot see the path to production on the first call, I say so on the first call — before you have paid for anything.