# Where Andrometiq came from — Andrometiq Andrometiq began inside a Tirupur factory in June 2016. What we built, where we failed, and how the capability accumulated — in time order. Canonical: https://andrometiq.com/origin/ [Home](/) › The origin The origin # The first commit was 5 June 2016. An order-management system, written inside Essdee — our family’s apparel business in Tirupur — because the way orders were tracked was costing money and sleep. Nobody called it a product. It has run a working business every day since. Built for our own floor ## There was no plan to become a consulting firm. There was a factory, and a factory produces problems on schedule: work that moves faster than the paper recording it, roles that blur as the team grows, bought software that fights the way the business actually runs. We met each one with our own money at stake, and we solved the one in front of us. Then the next. The failure ## We built the wrong system first. Early on, confidence got ahead of us. We spent a year building the complete system — every module, the whole business in one release. The people who were meant to live in it, our own floor, would not use it. > The floor rejected it. The floor was right. A year of work, unusable — and the most useful year in this story. Everything about how we now build came out of it. That discipline has [a page of its own](/method/). What the years left behind ## Every solved problem left a capability behind. These are the ones we can show. ### Invoicing stopped being a job. Sales invoicing at Essdee was once a dedicated, full-time role, and errors still got through. We closed the gaps until the role itself no longer existed. Nobody there raises a sales invoice any more — the invoice raises itself from the movement records, and billing errors stand at zero. The people moved to work that needs judgement. ### Paper left the floor. Goods movement at the factory is recorded 100% off paper — every delivery challan, every goods receipt, entered once, at the point it happens. ### Audits started producing outcomes. Two years of monthly inventory audits taught us that finding a problem is the easy half. Making the fix hold — the control point in the software, the training, the change of ownership — was learnt on that floor, one cycle at a time. It became the Assurance practice. [See the auditing practice →](/auditing/) ### The organisation was redrawn. As the company grew, the structure that had carried it stopped fitting. We redid departments, reporting lines and, above all, roles — one accountable owner per outcome instead of a shared shrug. Slow, uncomfortable work, and the foundation of the People practice. ### Brands went onto shelves. The house we grew inside builds and sells brands of its own. The brand practice learnt its trade on those shelves first, and now does the same work for clients. [See the brand work →](/brand/) ### The code met a public standard. We have shipped code into ERPNext — the system 30,000+ companies worldwide run on. Work that survives a public maintainer’s review is the standard we hold private builds to. [Why we open-source →](/open-source/) One name ## Capability with a name on it. Person by person, tool by tool, those capabilities accumulated — inside one company, through our team’s earlier careers, through consulting work along the way. Andrometiq is that capability with a name on it, offered outside the walls it was built in. Your problem will not match a template. Nobody has seen your exact problem before — us included — and a consultant who claims otherwise is selling you one. What these years built is a practised way of standing in front of a new problem: read the ground first, bring what it actually needs — the right people, the right tools, software that does not exist yet — and stay until the result is real.