Why being here matters
Most of this job is remote. The part that is not, matters enormously.
Writing the software is the part that can happen anywhere, and it mostly does. Understanding what to write cannot. It means standing where the work happens and watching which register gets filled, who chases which approval, and what the person at the counter types when the screen does not have a field for what just walked in.
From Trichy that is an afternoon, not an expedition — for Thanjavur, Pudukkottai, Karur, Perambalur and the towns between them as much as for the city itself. It changes what gets built, because a visit you can make again next week is a visit you actually make again next week.
Everywhere else in India we work the same way and simply fly for the two visits that count. What we will not do is claim an office in a city we do not sit in.
What we build
Software that an operation runs on.
Custom ERP systems
One system carrying orders, stock, production, purchase, billing and the approvals between them, shaped around the way your company already runs. The alternative is a product your people work around — which is how a register reappears on the floor and you end up with two versions of the same number.
Internal tools and dashboards
Attendance, approvals, dispatch, document trails, the report the owner asks for every Monday morning. Narrow builds that replace one spreadsheet properly, ship in weeks, and are felt the week they land.
Mobile apps
For the people who are not at a desk — supervisors on the floor, drivers, field sales, hostel wardens. One codebase, both stores, native where it actually matters.
Websites and integrations
A site that loads, a payment gateway that reconciles, a link between the software you bought last year and the software you had before it. If it is software and it is in your way, it is in scope.
If you make something, the fuller version of this is on the manufacturing ERP page; the one build written up end to end is biometric attendance feeding payroll.
Around here
What this part of Tamil Nadu actually runs on.
Engineering and fabrication
Trichy's heavy-engineering belt runs on subcontract work, and subcontract work is where ERP products break: job cards issued outside the building, material that leaves and comes back changed, and a cost per job nobody can state until it is over.
Foundries and casting units
Heat and casting records that stay attached to the part that came out of them, rejection and rework counted where it happens, and a cost per casting that holds up when the mix changes mid-month.
Colleges, schools and institutions
Admissions through to alumni, with fees, attendance, hostel and examinations in one place — and the reports a management meeting and an inspection each expect in their own format.
Distribution and multi-branch retail
Stock that agrees across branches, orders and dispatch in a single flow, and receivables an owner can look at directly instead of asking three people to prepare a sheet.
Questions we get asked
The answers before the first call.
Where in Trichy are you?
Our office is in Trichy, 620020 — that is the only address we have, and it is the one in our schema and on every page of this site. We have not put a street line on the site yet because we would rather arrange a visit than have people arrive at a door. Email us and we will send the location, or we will come to you, which is what usually happens.
Do you only work with companies in Trichy?
No. Trichy is where the team sits, not the limit of who we build for — we work with organisations across India, and the build itself is remote regardless of where you are. What being here does change is Trichy, Thanjavur, Pudukkottai, Karur and the towns between them: that is a drive rather than a flight, so a site visit costs an afternoon instead of a trip that has to be planned a fortnight ahead.
Can you come and look at how we work before we commit to anything?
Yes, and for anything larger than a small tool we would insist on it. Software development for an operation that already runs starts with watching it run — which register gets filled, who chases which approval, what the person at the counter actually types. An afternoon on your floor or your campus tells us more than a fortnight of requirement documents, and it costs you nothing to find out we are the wrong team.
We are a college, not a factory. Do you build campus software too?
Yes. Admissions, attendance, fees and receipts, hostel, exams, and the reports that management and an inspection both ask for — the shape of the problem is the same as a plant's even though the vocabulary is different. Trichy has more institutions than most cities its size, and the software most of them run was written for a smaller version of them.
We already bought a system and it did not work out. Do we start over?
Usually not entirely, and anyone who tells you otherwise before looking is selling a rewrite. Often the licence you are paying for covers most of what you need and the gap is two modules and a set of integrations, which is far cheaper to build than a replacement. Sometimes the product genuinely cannot be made to fit and we will say that too. We will tell you which one it is after we have seen it, not before.
How does a project start, and what does the first month look like?
A week of questions first — on site, with the people who do the work rather than only the people who authorise it. That week ends with a written scope and a fixed price for the first slice: the narrowest module that is useful on its own. You commit to that slice and nothing more, and if the budget and the problem do not meet, you find out in week one instead of month six.
Let us come and look at it.
What you do, how the month closes today, and the one process that costs you the most time. That is enough for us to tell you whether this is a small build or a bigger problem — and whether we are the right team for it.