Amrita Service — operational debt discovery
A discovery & design engagement for an equipment-repair business running ‘between systems’. We mapped three sources of operational debt and designed a unified operational model — partially implemented, then paused on the client's budget.
This system was designed and partially implemented — full rollout is currently paused due to client budget. We share it as a discovery & design case to show how we work.
- Industry
- Equipment repair & field service
- Engagement
- Discovery & system design
- Status
- Partially implemented (paused)
- Our role
- Process discovery & architecture
- Existing tools
- CRM · accounting · Excel
Scenario 1 — Fast service that must beat the system
For short on-site jobs, speed is part of the service. Staff wrote orders on paper because creating them digitally was slower — the same order was then re-created in accounting. Paper won on speed, not modernity.
Scenario 2 — Core business & manual handoffs
For multi-day hydraulic-cylinder repairs, intake happened on paper, photos went via messenger, and an accountant later re-entered everything. In season, dozens of orders a day turned manual handoff into the main bottleneck — re-entry, errors and stale data.
Scenario 3 — When Excel becomes the production system
Every morning the team rebuilt the operational picture by hand from exports — urgency, promised deadlines, current stage, parts needed, specialist load — then planned the day. Excel wasn't the problem; it was a symptom of a missing single operational picture.
Unified operational space
One operational layer connected to the existing accounting system — not another silo.
Ultra-fast intake for quick service
Create an order on-site, find parts by code/name/keyword, assemble typical kits, auto-calculate cost and pass it to accounting with no re-entry.
Digital intake for core repairs
A single order card holding client info, measurements, photos, specialist notes, work history and live status.
Operational visibility dashboards
Orders per stage, overdue work, urgent jobs, orders waiting on parts and load per department — generated automatically.
The company already had software meant to support its core processes: a CRM for clients, an accounting system for orders and finance, and years of accumulated operational data. Yet Excel remained the real entry point for daily decisions — what to work on, which orders are urgent, where to direct the team.
Part of the operational flow still happened between systems: on paper, in messengers, and in people's memory. That gap — between how the business actually works and how its systems work — is operational debt. Not the absence of technology, but a fast-growing distance between real workflows and the tools meant to support them.
Paper kept winning over software not because staff resisted change, but because in some scenarios it was simply faster. Excel survived because it was the only place to see the whole business at once.
- Quick-service order time cut from minutes of manual coordination to one continuous digital flow
- Fewer manual handoffs between departments
- Less dependency on individual employees
- Higher transparency of order status across the repair lifecycle
- Less time spent on daily planning
- A single operational picture without manual data gathering
- Lower coordination cost as the business grows
Enter information once
Data is entered a single time and used by everyone — no re-keying between people and systems.
Different scenarios, different workflows
Fast service and multi-day repair need different interfaces and different logic.
Visibility as a by-product
Operational visibility should appear automatically from the system — not be assembled by hand each morning.
Reflect real work
The system should mirror how the business actually works and reduce friction, not force staff to adapt to software limits.
The problem wasn't missing data. It was that information moved between people faster than it moved through the tools.
If your operations feel harder to manage than they should — we're happy to take a look.
We usually start by identifying one area that can be improved quickly.
Discuss your situation