Skip to content

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

Sydney & MelbourneAEST/AEDT · afternoon into late evening
AhmedabadIndia standard time · 10:00–19:00

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.

  1. 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

  2. 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

  3. 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

  4. 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

  5. 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

  6. 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.

  1. 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

  2. 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

  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

  4. 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

  5. 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.

  1. 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

  2. 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

  3. 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.

  1. 01

    Interface

    What your users touch

    Screens for the staff who open them every shift, not a one-off demo.

  2. 02

    Application

    Where the rules live

    Business rules written so an engineer you hire locally later can read them without a handover call.

  3. 03

    Data

    What you cannot afford to lose

    Access logs and backups in place before the first row, so a suspected breach is assessed from records rather than memory.

  4. 04

    Delivery

    How it reaches production

    Sydney-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 →

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.

What do you need built?
When do you want to start?
Where should we send the estimate?

Answer all three questions above, then send.

NDA-friendly · IP yours from day one

FAQs · Australia


Frequently asked questions from Australian teams

Time zones, data protection, cost and whether we have actually done this before.

Ask us directly →
Not yet. Australia is a new market for us: no existing clients, no local case studies, no track record we can point to. What we do have is eight years building internal tools and backend systems for companies elsewhere, and an office day that starts while your afternoon is still young. We would rather say this plainly than manufacture a reference.
No. QalbIT has no office or legal entity in Australia. Delivery runs remotely from Ahmedabad, India, and we say so upfront rather than implying a local presence that would not survive a follow-up question.
Sydney and Melbourne run 4.5 hours ahead of Ahmedabad on AEST, 5.5 during daylight saving from October to April. Our 10:00 start is 14:30 in Sydney in winter and 15:30 in summer, so the live window is your afternoon: about two and a half hours to a 5pm close on standard time, one and a half in daylight saving. Nobody shifts their hours, and work that needs no call carries on through our afternoon, which is your evening.
Yes, with the right contract terms. Australia’s data protection framework is the Privacy Act 1988, applied through the Australian Privacy Principles and regulated by the OAIC, with the Notifiable Data Breaches scheme covering breach reporting. Giving personal information to a team in India is a cross-border disclosure under APP 8: you take reasonable steps to make sure we handle it to the APP standard, and you generally stay accountable for what we do with it. That is why we agree data-handling and breach-notification terms in writing before the build starts.
We have not built specifically for an Australian mining, financial services, healthtech or professional-services client yet, so we will not claim sector depth we do not have. What we bring is general experience with operational software: internal tools, backend systems and B2B portals, the same layer of software every one of those industries runs on underneath its core product.
Fixed-scope work starts from $5,000, a scoped MVP included, and our published first-release ranges run from $9,000 – $28,500 for custom business software to $19,000 – $52,500 for a first ERP phase, all in US dollars. Integration count and data-migration scope move the figure more than headcount does. A fixed-scope first release typically runs 6 to 14 weeks; you get a written price range within 48 hours of a scoping call, before anything is committed.
In five stages. We map the process and the data it touches, then build a clickable prototype your staff review before any code exists. Working software follows every two weeks, then a launch with data migrated from the old system and a rollback path ready, then monitoring and the next slice of the roadmap. For an Australian team the demos sit in your afternoon, and the first stage also settles where the data will be hosted and the APP 8 terms that let it reach us.
Often, on the engineering line alone: our dedicated engineers start at $3,200 per engineer per month and fixed-scope work at $5,000, in US dollars. But the rate is not the whole cost. Sending personal information to India brings APP 8 accountability you carry, and the live window is your afternoon rather than your whole day. We have no sourced figure for Australian rates, so we will not invent a comparison: price one written scope with both firms, hosting and privacy work included.
Our published range for a custom CRM is $10,500 – $30,000 in US dollars, over 8 to 14 weeks. That covers the pipeline, contacts, automation and the integrations you already run. Where you land depends on how many systems it connects to and how much contact history moves across from the old tool. For an Australian firm the scope also sets out how consent and contact preferences are held, since most of what a CRM stores is personal information under the Privacy Act.
The duty sits with you. If your business is covered by the Privacy Act, you must assess a suspected breach within 30 days, and notify the OAIC and the people affected when serious harm is likely. A breach at your developer still counts as yours, so the contract sets out when and how we report one to you. That is why our access logs are in place before launch: an assessment needs a record of who saw which records, and when.
You do, from the first commit. The repository lives in your GitHub or GitLab account, not ours, so there is nothing to negotiate if the engagement ends or you decide to bring the work in-house.
We invoice as an overseas vendor; whether GST applies to your purchase depends on your own registration and is worth confirming with your accountant. Contract terms, IP assignment and payment milestones are agreed in writing before work starts, in line with normal Australian procurement practice.
Often yes, and it is usually the better call. A large share of our operational-software work elsewhere is extending an existing platform with a custom module or portal rather than rebuilding it from zero.
Launch is a release, not an ending. Most clients keep a small standing team for support and iteration on 30 days' notice; if you would rather run it yourselves, you get documentation and a handover walkthrough instead.

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.