The product
What Jagga does
Jagga is software that runs an engineering consultancy’s service delivery. The pattern is always the same: a client requests a service, staff process it through a tracked pipeline, payment is collected, an authorised report is delivered, and the client can see the status the whole way through.
Most of that work is property valuation for bank loan collateral, but the platform is not built only for valuation — it runs seven kinds of service. See Services.
Several consultancy firms use the same platform, each under its own branding, and each firm’s data is walled off from every other firm’s.
One file, thirteen steps
Every file walks the same backbone, whatever the service. Only the middle — the production work — changes from one service to another.
- 1Lead capture
A client asks for a service, or a Case Manager records the request. Client / Case Manager - 2Assessment
The Case Manager reviews the request and the inputs, and opens the file. Case Manager - 3Quotation
A price is offered. Either the configured price, or a negotiated one. The client accepts it. Case Manager - 4Advance payment
The advance is collected. Production does not begin before this. Payment gate. Client / Finance - 5Production
The work itself. Site survey where the service needs one, then the technical work. Surveyor / Engineers - 6Case Manager data entry
Always happens. The Case Manager enters the file's data. Case Manager - 7Client verification
Optional. The client checks the entered data. Client - 8Documents complete
A gate: the required documents must all be present. Case Manager - 9Drafting
Design, legal and report drafting. Design Engineer / Legal / Principal Engineer - 10Authorisation
The Principal Engineer finalises, signs and stamps. Principal Engineer - 11Final payment
The rest of the fee is settled. Payment gate. Client / Finance - 12Delivery
The client downloads the report, or receives a recorded hand-over. Client - 13Review window
A period in which a correction can be requested. Client / Principal Engineer
The two payment gates
Two of those steps are gates, and they are worth naming because they explain most “why is my file not moving” questions:
- Production does not start before the advance is paid. The quotation has to be accepted and the advance settled first.
- The report does not unlock before the final payment settles. It is visibly locked, with the amount due shown — not hidden.
The default split is 70% advance and 30% on completion, but a firm can configure that.
Where each step happens
| Step | Where |
|---|---|
| Requesting a service | The client portal on the web, or the Jagga phone app |
| The site visit | The Jagga Surveyor phone app, which works with no signal |
| Quoting, payments, coordination | The web console |
| Drafting and signing the report | The web console |
| Tracking, paying, downloading | The client portal or the phone app |
| Checking a finished report | A public page — no account needed |
What is fixed and what is configured
The backbone above is fixed, and so are the two payment gates. What a service does in the middle — which forms are filled, which documents are required, which steps run and in what order, which report format is produced — is configured, not programmed. Someone edits it in an admin screen; nobody writes code.
That is why a firm can add a document to a checklist, or a bank can get its own report layout, without a software release.
Read next
- Services — what the platform actually sells.
- Who does what — the people on a file.
- File statuses — what each status means.
- Money and dates — rupees, milestones, and dual calendars.
- The report — how it becomes authentic.
Last reviewed 2026-09-08.