AI in how we build
We use AI tooling throughout engineering — scaffolding, review, test generation, migration work. It is why a small team can take on the scope we do, and why we can keep maintaining what we ship.
About Aitulya
An AI-first software engineering company, in the literal sense.
Aitulya Private Limited builds and maintains business software — custom systems, ERP, web and mobile applications, platform work and integrations. We call ourselves AI-first because AI is in how we engineer and in what we ship, not because it reads well in a deck. The rest of this page is what that actually commits us to.
What AI-first means here
Two places it belongs, and one where it does not.
AI in what we build
Document assistants, retrieval over a company's own content, classification and extraction, and automation of the handoffs between systems. Applied where there is measurable manual effort to remove.
AI left out on purpose
Plenty of problems are solved better by a well-designed screen, a clear data model or a scheduled job. We will tell you when that is the case, even when it makes the project smaller.
Our values
Five words, each with something behind it.
- 01
Integrity
We say what the software does and what it does not. If a capability is unverified, it stays off the website until it is verified — including on this one.
- 02
Innovation
AI is in our work because it removes real effort, not because it belongs in a pitch. We would rather ship a plain form that works than an intelligent feature that impresses once.
- 03
Responsibility
We build systems businesses depend on to operate. That makes data handling, access control and the second year of maintenance part of the job rather than an afterthought.
- 04
Excellence
Code that the next engineer can read, decisions that can be explained, and software that behaves on a mid-range phone on mobile data — not only on ours.
- 05
Humanity
Software is used by people under time pressure. We design for the person at the counter and the person on the shop floor, not for the demo.
How we work
The same five steps, every time.
Discovery happens where the work happens. Design is agreed before code. Development arrives in cycles you can see running rather than in one reveal at the end.
01
Discover
How the work is done today, on site.
02
Design
Screens and data model agreed first.
03
Develop
Short cycles you can see running.
04
Deploy
Data migrated, team trained.
05
Support
Maintained for as long as it runs.
What we do not do
The boundaries are the point.
We do not quote before we understand the work
An instant price for software you have described in two sentences is a guess wearing a number. We come back with an approach and an honest view of what it takes.
We do not publish claims we cannot show you
No testimonials we did not receive, no logos we are not entitled to, no metrics we did not measure. If something is absent from this site, that is usually why.
We do not disappear after launch
Maintenance is a practice here, not a goodwill gesture. The second year of a system matters more than the first, because that is when it either earns its keep or quietly rots.
We do not take work we are wrong for
If a project needs a capability or a scale we cannot honestly commit to, we say so at the outset rather than learn it together at your expense.
Next
The three pages that say the most
Services
Six engineering practices
What the work actually covers, and the order we do it in.
Read more IndustriesSectors we build for
The operational problems we recognise, and what we would build about them.
Read more ProductsScholarAIMS and ShowShelf
Our own software — built, run and maintained by the same team.
Read moreStart a project
If that sounds like the
kind of team you want, write to us.
Two fields to start. We will come back with an approach and an honest view of what it takes — not an instant quote.