A software audit that finds where your records stop agreeing
The details
01What is drift, and how do you know you have it?
Drift is what happens when systems that should agree slowly stop agreeing. The CRM says an order was paid; the accounts say it wasn’t. Stock in the warehouse system doesn’t match stock in the books. Month-end takes longer because someone has to reconcile by hand, and nobody is quite sure which number is the right one.
Each mismatch looks small on its own. The cost is in the pattern: decisions made on the wrong figure, staff time spent reconciling, and errors that surface only when a customer, an auditor or a lender asks. The Drift Audit is for the point where you suspect the problem sits in how the systems connect, not in the people using them.
What does the audit produce?
First, a system map: the end-to-end flow of money, data and records, showing which system each figure starts in and where it is copied, transformed or typed again. Then a reconciliation analysis compares those systems against each other and traces each mismatch to its root cause — a sync that fails without telling anyone, a manual step, or two teams using the same field to mean different things.
The drift register lists where and why drift occurs, in one place your team can work through. Priority fixes rank the high-impact actions by value, and the executive readout puts the whole picture into a concise report for the people who decide what to fund.
What happens after the audit?
The Drift Audit is described in three short sentences: “We diagnose. You get clarity. We quote only after that.” The audit does not change your systems; it tells you what to change and in what order. If you want us to carry out the priority fixes, they are scoped and quoted separately once the diagnosis is done, each with its own fixed written proposal, so the cure is priced only after the cause is known.
Is this a code audit?
No. The Drift Audit follows records across systems — CRM, billing, accounts, inventory, wherever your numbers live — and asks why they disagree. It does not grade code quality or test coverage. That is Technical Due Diligence (₹23,000, up to 7 days), which reviews architecture, code, security red flags and key-person risk, and suits someone about to acquire, invest in or inherit a codebase.
Two other packages sit close by. If your records agree but the cloud bill or reliability is the worry, the Cloud Cost & Reliability Tune-up starts at ₹15,000. If the numbers are sound and the problem is seeing them clearly, the Finance MIS & Cash-Flow Dashboard (₹45,000) brings P&L, receivables ageing and cash flow into one current view.
How it works
02- 0115-min callTell us what’s breaking. We ask the questions that change the price.
- 02Scope in writingA fixed quote and a written scope: what’s in, what isn’t.
- 03Build & reviewWorking software early, with review rounds on real screens.
- 04LaunchWe go live with you, train your team and hand over access.
- 05SupportFixes, changes and growth on a retainer, if you want one.
FAQ
03What does a software audit cost?
The Drift Audit is ₹49,000 and takes 2–3 weeks, from mapping your systems to the executive readout. It is priced as a diagnosis: any fixes you decide to carry out afterwards are quoted separately, once you have seen the findings. Your fixed price arrives in writing after a 15-minute scope call.
What do you need from us?
Access to the systems whose records should agree, and time with the people who run them day to day, because a mismatch often starts in a manual step that is not written down anywhere. Exactly which systems are in scope, and what access that needs, is agreed on the scope call.
Is this the same as a statutory audit?
No. A statutory audit is carried out by a chartered accountant and ends in an opinion on your financial statements. The Drift Audit gives no such opinion. It looks at how your systems pass money, data and records between them, and where and why those records stop agreeing, so it sits alongside your accountant’s work rather than replacing it.
Which systems does it look at?
On the homepage it sits under financial systems: the ones where money, data or records should agree, such as a CRM and an invoicing tool, an online store and the accounts, or a stock system and the books. The system map comes first so the audit covers what you actually run; which of your systems are in scope is fixed on the call.
Who is the executive readout for?
The people who decide what to fund — an owner, a finance head, a board. It is a concise report: what drifts, why, and the priority fixes ranked by value. The system map, reconciliation analysis and drift register sit behind it for the team that will do the work.
Start with these
04Related reading
0515 minutes.
One quote.
Tell us what you need. We reply on WhatsApp or email with a time, and a written quote after the call.
Re: Drift Audit
MAKIN 