Aura Business is built for maintenance work that arrives in waves: a contract covering every unit across a customer's sites, planned visits that must finish before the season, filter and consumable replacements on their own cycle, and renewals that all fall due together.
An HVAC maintenance contract is rarely about one machine. It covers a fleet: forty split units across an office, a chiller plant and its handling units in a hospital, or every unit in eighteen branches of the same customer. The contract is one agreement, the schedule is per unit, and the invoicing is usually per site or per group. Software for HVAC AMC work has to hold that shape, because a service system that assumes one asset per contract will not survive the first renewal.
The second difficulty is that the work is seasonal. Everybody wants their planned maintenance finished before the weather turns, which compresses a year of visits into a few weeks and then fills the following months with breakdown calls. Aura Business schedules planned visits per unit, plans engineer routes across sites, tracks filter and consumable replacement separately from the visit itself, and raises renewals before the season rather than after it.
The problems of an HVAC service business are problems of capacity, repetition and scale rather than of complexity.
The contract covers units installed years ago, some replaced or moved, and the list has never been corrected.
The pre-season programme is still unfinished when the breakdown calls start, so it is quietly abandoned.
Visits are assigned by whoever calls first rather than grouped by area, so half the day is travel.
Filters and belts are replaced when an engineer notices, so the van does not carry what the site needed.
One customer with eighteen branches wants one invoice, or eighteen, and that is assembled by hand each time.
Contracts lapse in the busiest month and are only noticed when a lapsed customer calls with a breakdown.
Every unit is recorded as an asset with its site, location, capacity, make and installation date.
One contract covers the listed units across one or many sites, with the visit count and response commitment agreed.
Planned visits are raised per unit and grouped into a programme that can be finished before the load arrives.
Visits are planned by area and by day, so a team covers a cluster of sites rather than one call at a time.
The checklist is completed on the mobile job card, with filters or consumables issued against the job.
In-season calls are logged, dispatched against the contract response commitment, and closed with a job card.
Contract invoicing per site or per group, and the renewal engine raises the offer ahead of the next season.
Workflow: Visits due are shown as a programme with a completion count, so the shortfall is visible weeks before the season rather than during it.
Result: Planned work done while there is still capacity.
Workflow: Scheduled visits are grouped by area into a route, and the engineer works down the list on the mobile app.
Result: More units serviced per engineer per day.
Workflow: Consumable cycles per unit show what is due at the site being visited, and the parts are issued against the jobs before the run.
Result: One visit instead of two.
Workflow: The multi-site contract holds all sites under one customer, and invoicing is raised consolidated or per site as agreed.
Result: Billing that matches how the customer wants to pay.
Units sold, installed and then maintained under contract.
Contracts on units installed by somebody else.
HVAC as one line inside a wider site contract.
Critical sites with tighter response commitments.
Chillers and plant rooms with usage-based schedules.
Problem: A distribution business run entirely on WhatsApp and Excel.
Built: Field app, manager dashboard, GST billing and payment tracking.
Stack: React Native, Supabase, WordPress.
Problem: No online store or way to manage distributors.
Built: Storefront, distributor portal, quote-to-order and 253 SEO pages.
Stack: Supabase, JavaScript, Playwright.
Yes. A contract covers a listed fleet of assets, and each unit keeps its own location, schedule and service history. Multi-site contracts hold the sites of one customer under a single agreement with reporting across all of them.
Visits are raised per unit against the contract and shown as a programme with due, completed and outstanding counts. Routing groups them by area, so capacity is spent on units rather than on travel.
Yes. Consumables can run on their own replacement cycle per unit, and the items are issued against the job when they are fitted, so stock drops and the unit's history shows what was changed and when.
Yes. The customer portal and helpdesk let a facilities team raise a call, see its status and see the visit history for their sites, which also gives you a clean intake time for measuring response.
Yes. A call can be recorded as covered or chargeable, with parts and labour billed on a service invoice where they fall outside the agreement. What is covered and excluded is held on the contract for the desk to check at intake.
No. The renewal engine works from contract end dates and raises the offer in advance, which matters in a seasonal trade where a lapse during the busy months is rarely noticed until a breakdown call arrives.
Invoicing a contract fleet.
Schedules and checklists.
Routes across sites.
Plant assets and breakdowns.
Multi-brand service contracts.
What AMC software does.
Scheduled testing across a building.
Tell us how you work today. We will show you what the platform would look like for you, and give you a clear scope and timeline.
Founder-led · Chennai, India · Built and supported by the person who wrote it