Vertical I · Business Health Check Service 01 of 08
Business Health Check
A structured, time-boxed examination of where money and time leave the business — between systems, between departments, and in the gaps nobody owns.
| Ref | Finding | Domain | Amount | Traced to | Method | Confidence | Cause |
|---|---|---|---|---|---|---|---|
| F-01 | Delivered, never invoiced | Revenue & billing | ₹ ••,••,••• | Dispatch notes with no invoice line | Dispatch ↔ invoice ↔ ledger match | High | Process |
| F-02 | One item, three prices | Procurement | ₹ •,••,••• | PO lines for one SKU, two sites | Price variance by item and week | High | System |
| F-03 | Input credit at risk | Compliance & tax | ₹ •,••,••• | Purchase register vs vendor filings | Vendor filing behaviour | Medium | Data |
| F-04 | A receivable nobody chases | Receivables | ₹ ••,••• | Ageing report vs follow-up log | Last-touch interval by owner | Medium | Incentive |
Amounts are masked here. In your register every row carries a figure in your currency, the rows it came from, and a confidence rating we are prepared to defend.
The eight domains we examine
- Revenue & billing accuracy — work delivered but never invoiced, rate-card drift, missed escalations.
- Procurement & vendor spend — price variance for the same item, duplicate vendors, off-contract buying.
- Inventory & working capital — stock that is financed but not moving, write-off patterns, shrinkage signals.
- Receivables & collection cycle — ageing concentration, dispute-driven delay, follow-up that stopped.
- Compliance & tax exposure — credits not claimed, credits at risk, filing and documentation gaps.
- Manual effort & duplication — the same figure keyed into three places by three people.
- Data integrity across systems — where two systems disagree about the same fact, and which one is believed.
- Decision latency — the interval between an event happening and a person being able to act on it.
What you receive
- Findings register
- Every finding stated as an amount, with the records it was derived from, the method used, and a confidence rating we are willing to defend.
- Root cause
- Whether the cause is process, system, data, or incentive — because the fix differs completely and three of those four are not software problems.
- Ranked remediation
- Each finding scored on value, effort and certainty, so the sequencing decision is yours and is made on evidence.
- Agreed baseline
- The measurement basis for anything built afterwards, fixed in writing before build starts rather than reconstructed at the end.
What you gain
You find out what is actually wrong, in your own numbers, before committing capital to a system. The register is useful whether or not you engage us further — it is your document, derived from your data, and it survives the relationship.
It also changes your position with every other vendor: a quote you can map to a specific evidenced loss is a decision; one you cannot is a gamble with a purchase order attached.
Best fit when you suspect there is leakage but cannot name it, when two systems disagree and nobody can say which is right, or when you have a proposal in hand and no way to judge whether it solves anything.