Ingo Systems Ingo Systems

Software people actually open every morning.

Most of our work is school and college ERP, business software, and the web and mobile apps that sit around it. A build usually runs six to fourteen weeks. When it ends you get the repository, the documentation and every credential. We do not keep the keys.

6–14 weeks
typical build, scoping call to launch
Flutter · React · Node · Postgres
the stack we maintain in-house
Yours at handover
repo, docs and every login

Three things make up most of our work

The rest of the list is what those three need in order to work properly.

Education ERP
Schools · Colleges · Coaching 01

Education ERP

Admission enquiries, attendance, fee receipts, timetables, exams and transport in one system. Parents get an app. The office gets a register that adds up. The principal gets the one screen worth checking before assembly.

  • Parent app and staff app, both stores
  • Fee ledger with printable receipts and dues
  • Your existing spreadsheets imported, not retyped

Typically 10–14 weeks · we pilot one branch before the rest

Websites and web apps
Web 02

Websites and web apps

Marketing sites that load fast on a mid-range phone, plus the admin panels, portals and dashboards behind them. The CMS is set up so your team edits a page without calling us first.

  • Pages your team can edit without a developer
  • Analytics and Search Console wired in before launch
  • Tested on a ₹12,000 Android, not just a MacBook

Typically 4–8 weeks

Mobile apps
iOS · Android 03

Mobile apps

Flutter or React Native, one codebase, both stores. We handle the parts that usually go wrong late: store review, push notifications, what happens with no signal, and how the next update reaches users.

  • Both store listings prepared and submitted
  • Offline behaviour decided, not left to chance
  • Crash reporting from the first build

Typically 8–12 weeks

The rest of the build

AI assistants and automation

Chatbots that answer from your own documents, lead scoring, and the small automations that remove copy-paste between two tools that were never meant to talk.

UI/UX design

Wireframes and a design system before code, so the build is not an argument about button colours in week nine.

APIs and integrations

Payments, WhatsApp, maps, CRM, Tally. The plumbing between systems that each assume they are the only one.

E-commerce

Storefronts, carts, order management and inventory sync, including multi-vendor when you genuinely need it.

Cloud, security and performance

AWS or GCP setup, backups, hardening, and an honest look at what your current bill is actually buying.

Migration and maintenance

Moving old sites off dying stacks, then keeping them patched, backed up and monitored so nobody notices them.

What the six to fourteen weeks are spent on

Every project runs on this shape. The build stage stretches or shrinks; the rest does not.

Stage How long What you get at the end of it
Scoping 2–3 days A written scope with a fixed price, before any money moves
Design and data model 1–2 weeks Screens you can click through, and the tables behind them
Build 3–10 weeks A working demo every second Friday, not a status email
Pilot 1–2 weeks Your real users on your real data, and our fixes
Handover 2 days Repository, documentation, credentials, and a recorded walkthrough

What we need from you: one person who can make decisions, your existing data in whatever mess it is currently in, and an hour every second Friday. Projects stall on approvals far more often than on code.

Every project ships with

Source code Your repository, your account, from the first commit
Documentation Written for the next developer, not for us
Credentials Every login handed over in a shared vault
30 days Post-launch fixes at no additional cost

When we are not the right call

  • You need it live next week. We would rather say no than hand you something you have to rebuild in six months.
  • You want the cheapest quote in the room. We usually are not it, and we will tell you honestly when a smaller shop would serve you better.
  • You want the agency to keep the code. We hand over everything. If a vendor holding your system is what you are after, we are the wrong choice.

Tell us what breaks today.

Bring the spreadsheet, the WhatsApp group, or the software you already hate. We will tell you what it takes to replace it and what it costs, before you commit to anything.