Contracts, tickets, and assets
on one ledger.
Run the whole shop — the SLA on a managed-services contract, the ticket a client raised at 9 p.m., the laptop it’s logged against, the engineer’s billable hours, and the AMC invoice that goes out on the 1st — on a single system. No more reconciling a helpdesk tool against a spreadsheet of renewals, or guessing which contract a job card belongs to.
Built for managed-service providers, IT-AMC firms, network and security integrators, cloud and CCTV/biometric contractors, and the in-house IT teams that bill internal departments.
If you carry dozens of clients on annual contracts with different SLAs, keep hundreds of their machines under watch, dispatch engineers across the city, sell both labour and licences, and have to raise a clean recurring GST invoice every month while chasing a wall of vendor renewals — this is the system that holds all of it together. One client record carries its contract, its assets, its open tickets, its project hours, and its ledger, so support, sales, and accounts are never looking at three different versions of the same account.
The modules an Indian MSP
actually runs on.
Client record & contacts
One file per client carries the whole relationship — registered name, billing and site addresses, GSTIN and state code, multiple contacts with roles (admin, accounts, escalation), and every site or branch under that account. Because contracts, assets, tickets, projects, and invoices all hang off this one record, anyone — the engineer dispatched at noon, the salesperson upselling a renewal, the accountant raising the bill — opens the same single view of the client instead of stitching three tools together.
Contracts & SLAs
Model each engagement as it really is — comprehensive AMC, non-comprehensive, per-device managed service, retainer, or break-fix — with its term, value, renewal date, and the SLA that governs it: response and resolution targets by priority, covered hours (8×5 or 24×7), and what’s in or out of scope. Every ticket and job card is checked against the contract, so out-of-scope work is flagged for extra billing and an expiring SLA surfaces before it lapses.
Helpdesk & ticketing
Capture every request — email, portal, phone, or WhatsApp — into a ticket that auto-stamps priority, the matching SLA clock, the linked asset, and the assigned engineer. Track first-response and resolution against the contract’s targets, escalate breaches automatically, and let clients reply by email straight into the thread. CSAT on closure, reopened-ticket tracking, and a queue board that shows what’s about to breach turn a chaotic inbox into a measurable desk.
Asset register & CMDB
Keep a live configuration database of every device you manage — desktops, laptops, servers, firewalls, switches, printers, UPS, NVRs — tagged to the client and site, with make, model, serial, warranty expiry, purchase value, and its relationships (which server hosts which app, which switch feeds which floor). Each asset carries its full service history, so when a ticket lands the engineer already knows the machine’s config, warranty status, and last three repairs.
Monitoring & alerts (RMM)
Pull health signals from your RMM and network tools — disk filling up, a server down, a backup that didn’t run, antivirus out of date, a UPS on battery — in through the integration layer, and convert critical events straight into tickets against the right asset and client. Alert thresholds, on-call routing, and a single dashboard of red/amber/green per site mean you catch the failing disk before the client calls, and the proactive fix is logged like any other job.
Dispatch & field engineers
Schedule onsite visits from the ticket, see each engineer’s day on a dispatch board, and send them the job, the site address, and the asset history on a mobile view. They check in, log work done, capture parts used and the client’s signature, and close the job from the field — the time spent and any chargeable parts flow back to the ticket and the billing engine automatically, so a visit never goes unbilled because the paper job card got lost in a bag.
Projects & timesheets
Run the bigger jobs — a network rollout, an Office 365 migration, a CCTV installation — as projects with phases, milestones, a budget, and assigned resources. Engineers book hours to tasks on weekly timesheets, so you see planned versus actual effort, billable versus non-billable time, and true project margin. Milestone-based billing draws straight from approved timesheets and material, so a fixed-price project never quietly bleeds away its profit in unrecorded hours.
Recurring AMC & usage billing
Generate every month’s invoices from the contracts in one run — flat AMC, per-device or per-seat managed service, per-user Microsoft 365 or backup, and metered usage like cloud or bandwidth — with the correct SAC code (998313 for IT support, 998315 for hosting) and 18% GST, CGST/SGST or IGST chosen by the client’s state. Out-of-scope tickets and field visits roll into the same bill, renewals auto-raise on the due date, and an e-invoice IRN is generated where the turnover threshold applies — so recurring revenue collects itself.
Collections, payments & TDS
Send the GST invoice with a Razorpay/PayU or UPI pay link, auto-reconcile the receipt, and run an outstanding-ageing report that shows exactly who’s overdue on which contract. Corporate clients deducting TDS on your service bills under Section 194C/194J are tracked against Form 26AS, so the deducted tax is recognised and reconciled rather than written off as a short payment. Dunning reminders fire automatically before a renewal lapses for non-payment.
Procurement & licensing
Raise purchase orders to distributors, receive hardware into stock against the vendor’s GST invoice (claiming input tax credit), and track software subscriptions and licences — Microsoft 365, antivirus, backup, SSL, domains — with seat counts, cost, sell price, and the renewal date that matters. A single renewal calendar across every client’s licences and warranties means you re-sell the renewal at margin instead of discovering it expired last week.
Knowledge base & SOPs
Build an internal library of fixes, runbooks, and configuration notes — tagged by client, vendor, and issue type — so a recurring problem is solved once and reused, and a new engineer ramps on documented procedure rather than tribal knowledge. Approved articles can be published to the client portal as how-to guides, and resolved tickets prompt you to capture the fix, so the desk gets faster and less dependent on the one person who “knows that site”.
Client portal, communication & payroll
Give every client a portal where they raise and track tickets, see their assets and SLA status, download GST invoices, and read published how-to articles — with all updates, breach alerts, and renewal reminders pushed by email, SMS, and the portal and logged against the account, so “nobody told us” stops being an argument. On the same books, run staff payroll for engineers and support — EPF, ESI, and Professional Tax to current slabs, TDS on salary under Section 192, payslips and the EPF ECR/ESI return files ready to upload — while their billable hours from timesheets feed utilisation reporting. Contracts, tickets, assets, billing, collections, and payroll all reconcile to one set of accounts.
A short tour through
an MSP on Garuda.
Product tour · placeholder footage
One ledger means the engineer, the account manager, and the accountant are all looking at the same client — the SLA, the open ticket, the asset under it, and the invoice it bills to.
Client record linking contract, SLA, assets & billing
Every ticket clocked against its contract target
Recurring AMC invoices with correct SAC & e-invoice
Renewals missed or visits left unbilled
See your contracts
billing in five minutes.
The live demo is a real MSP tenant, pre-loaded with clients, AMC contracts and SLAs, an asset register, open tickets, and a month of recurring invoices. Click in, raise a ticket, close a job, generate an AMC bill with GST — no sign-up. Then write to us about your business.