33.9°S 151.2°E · Serving Australia
Custom software development for Australia: internal tools and backend systems
Custom software development for Australian companies, from a remote senior team in Ahmedabad: the internal tools, backend systems and B2B portals your operations run on, with the Privacy Act and the Australian Privacy Principles in the data model from the first sprint. We opened delivery to Australia because the work fits, not because a queue of Australian companies is already waiting on us.
No office in Australia and no Australian clients yet either. This is a new market for us and we would rather say so than imply otherwise. What is real: eight years building this kind of system, and a working morning that lands in your afternoon, with nobody on either side starting at midnight.
Working overlap · a normal TuesdayBlue = live together
When our day starts at 10:00 in Ahmedabad it is 14:30 in Sydney on standard time and 15:30 in daylight saving. So the live window is your afternoon: about two and a half hours to a 5pm close in winter, one and a half in summer. Nobody starts at midnight, and the rest of our day runs on into your evening for work that needs no call.
8+
Years in custom software
120+
Projects delivered
50+
Clients worldwide
0
Subcontractors
What we build
Operational software for Australian businesses.
Mining-services contractors, financial-services firms, healthtech teams and professional-services practices all run on a layer of internal software beneath the product: shift and equipment reports, claims and compliance queues, clinic back offices, matter and billing records. We have not built for these sectors in Australia yet; that layer itself is our everyday work.
Internal tools
Shift handover, equipment and permit-to-work tracking for a mining-services contractor, or the approval chain inside a professional-services practice, built around your process rather than the nearest module in a licensed suite.
Laravel · Node.js · React
Custom backend systems
The system of record behind a claims desk or a compliance queue, with an access log your risk team can audit, documented well enough that whoever inherits it after us can carry it forward.
PostgreSQL · REST · queues
B2B portals
Supplier and partner portals where each party sees only what its agreement covers, with invoices handed to your Peppol access point for the eInvoicing network the ATO administers.
Role-based access · Peppol eInvoicing
Reporting tools and dashboards
Reporting pulled live from the systems you already run, so the figures behind each BAS and board pack stop being a spreadsheet someone rebuilds by hand.
Live data · exportable
CRM development
A CRM for advisers and account managers, built around how your team actually works a client, with contact preferences held on every record because most of what a CRM stores is personal information.
Typically $10,500 – $30,000
Cloud and DevOps
AWS in the Sydney region when the data should stay onshore, with backups and a release process that do not depend on one person or one laptop.
AWS ap-southeast-2 · Docker · CI/CD
Why us
Stated plainly: a short overlap, and written handover for the rest.
We will not pretend to have an Australian track record we do not have yet. What we can put a number on is the timezone: our 10:00 start is 14:30 in Sydney, 15:30 in daylight saving, which leaves one and a half to two and a half live hours before a 17:00 close. Live calls sit in that window, a written handover covers the rest, and nobody works through the night to make them.
Your afternoon is our morning
Our day opens at 14:30 Sydney time, 15:30 in daylight saving, so demos, reviews and decisions sit in the one and a half to two and a half hours before your 17:00 close. Neither side moves its hours, and what is left of our day carries on while your office is closed, with a written handover waiting for your morning.
One team, no subcontractor chain
Everyone on the project is a QalbIT employee in Ahmedabad. There is no Australian reseller in the middle taking a margin, so the engineer on your afternoon call is the one writing the code.
Scope written down before pricing
A written scope with the exclusions named, so the figure you agree to is the figure you pay and anything added afterward is quoted, not absorbed silently.
You hold the repository from day one
The code lives in your GitHub or GitLab account from the first commit. Bring the work in-house or end the engagement, and the running system is already in your hands.
APP 8 settled before any data moves
Handing us personal information is a cross-border disclosure under APP 8, and you generally stay accountable for how we handle it. So data-handling and breach-notification terms are put in writing first, because the NDB scheme gives you 30 days to assess a suspected breach.
Process
How the engagement actually runs, hour by hour.
The same disciplined delivery process everywhere, made more useful here because the live overlap means a decision made in your afternoon reaches the build the same day rather than waiting for tomorrow.
Discover & define
We map the current process, the personal information it touches and where that data sits today, so hosting and APP 8 terms are settled before anything is scoped.
Week 1
Design & validate
A clickable prototype reviewed on an afternoon call with the supervisors, claims staff or advisers who will use it, before any production code is written.
Weeks 2–3
Build in sprints
A demo every second week in your afternoon: real screens on a call, never a status email standing in for one.
Sprint by sprint
Launch & stabilise
A rollout timed for a quiet afternoon on your side, data migrated from whatever the system replaces, and a rollback path if anything has to come back out.
Launch week
Improve & extend
Monitoring and access logs you can draw on in an NDB assessment, then the next slice of roadmap once the system carries real operational load.
Ongoing
Engagement models
Fixed scope, a dedicated team, or staff augmentation.
A first engagement usually starts fixed-scope, so both sides can see how the overlap and the process actually work before committing to anything standing.
Fixed-scope project
One release from $5,000, a written scope and a fixed list of exclusions. The usual way to test a first Australian engagement before committing to anything longer.
Fixed price · 6–14 weeks
Dedicated product team
A standing team, from $3,200 per engineer per month, that owns your internal tools release after release once the first system is live.
Monthly · 30 days notice
Staff augmentation
Engineers who work inside your own board and repository, with your morning stand-up replaced by a written one, for when the gap is capacity rather than architecture.
Per engineer · per month
Technologies
Four layers, chosen so the fifth engineer can still read them.
Every Australian build stacks the same four layers, picked so that an engineer you hire in Sydney or Melbourne later can read the code and run it without us.
- 01
Interface
What your users touchScreens for the staff who open them every shift, not a one-off demo.
- 02
Application
Where the rules liveBusiness rules written so an engineer you hire locally later can read them without a handover call.
- 03
Data
What you cannot afford to loseAccess logs and backups in place before the first row, so a suspected breach is assessed from records rather than memory.
- 04
Delivery
How it reaches productionSydney-region hosting where data must stay onshore, staged releases and a rollback path on every deploy.
Already running an accounting package or a licensed suite? We connect to what works rather than rewriting it for a stack preference, and the architecture review names which parts stay, in writing, before anyone touches a repository.
Review my stack →Case studies
Real systems shipped with QalbIT.
None of these are Australian engagements, we have not run one yet. They are the closest evidence we have for the kind of internal tool and platform work this page describes.

Bloomford · hiring portal
A modular hiring portal replacing manual candidate tracking, delivered module by module without downtime.
Result: Structured Records, not attachments

Plugin · club management platform
Court scheduling, memberships, variable pricing and online payments in one system replacing manual admin.
Result: Fewer Double-booked courts
Start here
Tell us what the system needs to replace.
Describe the process and who depends on it. You get a written scope, an architecture recommendation and a price range within 48 hours, scoped on a call that happens inside your own working day.
- A written scope with the exclusions listed
- An architecture recommendation, not a sales deck
- The name of the engineer who would lead it
- Free, and yours to keep either way
Get your free estimate
Three quick questions: scope, approach and a price range back within 48 hours. No sales call required first.
FAQs · Australia
Frequently asked questions from Australian teams
Time zones, data protection, cost and whether we have actually done this before.
Ask us directly →Next step
Start a conversation about your system.
A couple of lines on the process and its hardest constraint will do. A written scope, timeline and price range comes back within 48 hours, scoped on a call in your afternoon.