Custom operations software
Every trip, litre and rupee on one register.
Lanefolio is operations software built around the way your organisation already runs. Your registers, your expense heads, your documents, your reports. One depot or a national network.
Built for your organisation
The specification is your workflow, not our template.
Lanefolio has a proven core: one ledger, and a register for every kind of movement and cost. Everything above that core is built for your organisation, in the language your own office already uses.
Two operations that look identical from outside keep their books differently, price differently and approve differently. So the engagement starts by reading yours, and the software is written to it.
Your vocabulary
Khoraki, kanta, bilty, or whatever your office says instead. The screens carry your words, not translations of them.
Your registers
The expense heads you actually book, the approval chain you actually run, and the documents you actually issue.
Your reports
The figures your management asks for, in the format they already read them in, on the day they need them.
Your gaps
Anything your workflow needs that does not exist yet is specified with you and built into your deployment.
How we help organisations
Four failures that look like clerical problems and are not.
Nobody can cost one vehicle
The organisation knows what the month cost. It cannot say what one vehicle, one route or one contract cost, because no figure traces back to a transaction.
The sheet is typed, not calculated
Totals are keyed in by hand. One cell holds a number somebody typed instead of a sum, and it stays wrong from that day on because nothing points back to a source.
Documents expire quietly
Insurance, fitness, permit, road tax, PUC. A vehicle runs on an expired document until a checkpoint finds it, and by then the renewal was the cheap part.
Month-end is rebuilt, not read
The same spreadsheets, reconciled by hand, every month. Days of work, and at the end of it the answer is still an estimate.
What it does
Twelve registers. One ledger underneath.
This is the core, as it runs today. Each register is configured to your operation and named in your terms, and what your workflow needs beyond it is built.
Trip register
Every journey, its freight and every expense against it. Trips stay open and keep taking expenses as they are reported, rather than being batched at the end.
One ledger
Wages, repairs, fuel, documents, halting, assets. Each writes one row into the same ledger, and no register keeps a private total of its own.
Cost per unit
What one vehicle, route or contract earned, what it cost and what it made. Cash and normalised, side by side, for any period you ask for.
Fuel and consumables
Litres per trip held against a route norm and flagged past the threshold you set, from the slips the office already keys in.
Documents and compliance
Every statutory document per asset, with the warning arriving before the date rather than after it.
Workshop and maintenance
Job cards with material and labour as separate line items, allotted either to a journey or to the asset itself.
Advances and accounts
Advances and expenses in one running account that carries across trips and people. The khata, kept straight.
Reports and exports
Every register exports to Excel and PDF, formatted and printable, ready for the accounts team without anybody retyping it.
API and integrations
A documented REST API and webhooks, with connectors for accounting, ERP, fuel cards, GPS and weighbridge feeds. If a system has an interface, it can be wired in.
Roles, access and audit
Permissions by role and by branch, and an audit trail on every change: who altered what, and when.
Branches and entities
Depots, companies and cost centres reported separately or consolidated, in a single deployment.
Built for weak lines
Entry keeps working when the connection drops and syncs when it returns. Nothing that was typed is ever lost.
What makes it work
Three decisions that change what the numbers tell you.
Every figure traces back to a transaction.
Anything that costs money writes exactly one row into one ledger. Nothing anywhere stores a total, so a number in a board report is not a claim about the operation, it is a query over it.
That is why a wrong figure can be found. Open it, and the transactions that made it are there.
| Vehicle 11, June, total cost | 3,84,120 |
| Fuel, 4 entries | 1,92,400 |
| Trip expenses, 31 lines | 88,300 |
| Workshop, 3 job cards | 62,900 |
| Documents, apportioned | 40,520 |
Every line opens to the entry that made it. Nothing here was typed as a total. Illustrative figures, in ₹.
Costs land in the period they belong to.
An annual permit or road tax bill lands in one month and makes a perfectly good asset look like a loss-maker. Lanefolio spreads that cost across the period it actually covers and shows both views, so a sound asset is not written off on a timing artefact.
| Cash | Normalised | |
|---|---|---|
| Freight | 2,60,000 | 2,60,000 |
| Fuel | 1,41,000 | 1,41,000 |
| Trip expenses | 46,500 | 46,500 |
| Road tax, annual | 78,000 | 6,500 |
| Result | −5,500 | 66,000 |
The same asset and the same month. One view is a cash artefact, the other is the truth. Illustrative figures, in ₹.
It fits the systems you already run.
Your accounts team stays in the software it knows. Exports are built to the format the receiving system expects, and the API moves the same data into your accounting package, your ERP or your own reporting warehouse on a schedule.
Nothing here asks anyone to abandon a system that works. New integrations are part of the build, not a separate product.
| Accounting | Ledger exports in the receiving format |
| ERP | REST API, scheduled or on demand |
| Fuel cards | Statement import, matched to entries |
| Telematics | Position and odometer feeds, per asset |
| Weighbridge | Slip capture, per movement |
| Your warehouse | Webhooks and a documented API |
Connectors are specified against the system on the other side, and are part of the build.
How we work
Specified with your team. Built to your workflow.
Four stages, in the open. You see the specification before anybody writes code, and the increments as they land.
Survey
We read what already exists: your registers, your expense heads, your documents and the reports your management actually reads.
Specification
A written specification and a plan you can price, weigh and challenge before anybody writes code. No black boxes.
Build
Delivered in visible increments, configured to your operation, with your own vocabulary on the screens your staff use.
Run
Hosted, monitored, backed up and supported by the people who built it. Changes keep coming as the operation changes.
Managed cloud infrastructure.
The same infrastructure standard applies whatever you run: encrypted in transit and at rest, backed up daily, and audited on every change. Your data stays in India, and it stays yours.
Contact
Tell us how your operation runs.
What you move, how many assets, and what you use to track them today. That is enough for a useful first conversation.