Aura Business is built for firms that earn from contracts and call-outs rather than from selling boxes: annual contracts, breakdown calls, engineers with vans, spares consumed on site, SLAs that carry a penalty, and an invoice for every visit.
Some companies sell equipment and service it as a courtesy. Others have no product line at all: the contract is the product, the engineer's time is the cost, and the spare is the margin. Software written for the first kind treats service as a support desk bolted to a sales system. This page is about the second kind.
Aura Business carries a service-led firm end to end. Contracts are set up with their coverage and billing schedule, calls arrive and are logged against the covered asset, an engineer is dispatched by skill and area, the job card records the work and the spares consumed, the SLA clock is visible throughout, and the service invoice is raised from the completed job.
Because contracts and assets sit in the same platform as stock and billing, the two questions a service owner cannot otherwise answer become answerable: which contracts are about to lapse, and which contracts cost more to serve than they bring in.
A distributor can survive a messy service desk. A service company cannot.
Renewal dates live in a diary or a spreadsheet tab, and the customer only remembers the contract when something breaks.
Phone to one person, WhatsApp to another, email to a shared inbox, so nobody knows the true open-call count.
Response and resolution windows are written into the contract but measured, if at all, after the customer complains.
Parts are drawn for a job and never booked against it, so stock is wrong and the job looks more profitable than it was.
Visits done in the first week are billed in the following month because the paperwork has not come back.
Every contract is assumed to be earning until one customer's call volume quietly eats a year of margin.
AMC or CMC created against the customer's assets with coverage, SLA definitions and billing schedule.
The maintenance calendar generates planned visits so contracts are served, not just reacted to.
A breakdown is raised against the asset, with its contract status visible at intake.
Assigned by skill, area and roster, with the SLA timer running from the moment the call opened.
Fault, work done, spares used and photos captured on the mobile app, with the customer's signature on site.
Chargeable work billed with GST; contract-covered work closed without a charge but recorded against the contract.
The renewal engine surfaces contracts approaching their end date before the customer notices.
Workflow: The desk sees the asset, the contract, the SLA window and which engineer is nearest with the right skill, and dispatches without a round of phone calls.
Result: The commitment made to the customer is one the desk can keep.
Workflow: The renewal engine lists contracts ending next quarter with their call history attached, so the quote reflects how much work the customer actually generates.
Result: Renewals are negotiated from evidence rather than from last year's figure.
Workflow: Calls, engineer visits and spares are all booked against the contract, so the cost of serving it is visible next to what it earns.
Result: A loss-making contract is repriced or declined at renewal.
Workflow: Job cards close on the phone and chargeable jobs arrive at the billing desk the same day.
Result: Invoices go out while the visit is still fresh in the customer's mind.
Multi-brand engineers maintaining hospital equipment.
Lifts, HVAC and fire systems on scheduled rounds.
Plant machinery under annual coverage.
Printers, networks and devices across many small sites.
Coverage for equipment the firm never sold.
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.
No. Assets are registered in the installed-base register with make, model and serial regardless of who supplied them, and contracts are written against those assets. Multi-brand coverage is a normal setup.
The modules overlap, but here contracts and SLAs are the commercial centre rather than an after-sales duty. See field service software for the distributor view.
Yes. The mobile job card, photos and customer signature are captured offline in plant rooms and basements, and sync when the phone reconnects. See mobile job cards.
Yes. Contract billing follows the schedule agreed in the contract, while chargeable calls and spares are invoiced with GST from the closed job card, so the two revenue lines stay distinct.
Yes. Customer ticket submission and the self-service portal let a customer log a call, see its status and view their contracts. See the customer portal.
The delivery framework is live in 30 working days where scope allows, with your contracts, assets and spares list migrated in during setup. Support is on WhatsApp, with in-person work in Chennai.
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