Home › Problems we solve
Problems we solve
The software problems manufacturers keep paying to live with
Eleven problems, heard in every sitting with a manufacturer who spends real money on business software year after year. Each one earned its place by being checked against the published record — the receipts sit under every answer.
Chapter
The bill that grows by itself
The renewal quote is nothing like the price you signed.
The first year was a discount; nobody said so at the time. At renewal the discount has quietly expired, and an annual uplift is now a standing line on your cost sheet. You budgeted for software. You are funding a pricing model.
How we answer it. The code we build is yours and the stack is open source. There is no licence to renew and no discount to expire — no renewal lever exists for anyone to pull on you.
Receipts: NetSuite pricing analyses (Inteltech; Broken Rubik) · 2024–25 · documented discount-expiry renewal cases plus standard annual uplifts and current list pricing — corroborated secondary analyses, not primary-verified.
Simple changes need a paid specialist.
A new field, a changed approval, one more report column — and the answer is a consultant, a quotation and a wait. On paper the system is yours. In practice, every adjustment is billable to somebody else.
How we answer it. We train one person on your side to run the system and change it, now and later. The everyday changes stop being purchase orders.
Receipts: Capterra verified user reviews, SAP Business One · ongoing · “expensive to do simple things”, consultant dependency; SAP consulting-market analyses · 2024.
Paying for features nobody opens.
Every suite ships modules your team will never touch, and the subscription prices them in regardless. Usage telemetry says most features in modern software go rarely or never used. The invoice does not distinguish.
How we answer it. Nothing we ship is shelfware. Every feature exists because you asked for it — we build exactly what you want, and nothing you don’t.
Receipts: Pendo Feature Adoption Report · 2019 · usage telemetry across 615 SaaS subscriptions — measures feature usage inside SaaS vendors’ own products, not shelfware in software manufacturers buy.
Software’s share of your budget keeps climbing.
Put this year’s software line beside the one from a few years ago. The slice is visibly larger, and nothing decided that except the vendors’ pricing.
How we answer it. Our economics don’t ratchet: no per-seat fees, no renewal cliff, code you own outright. The cost curve is flat by design.
Receipts: BCG, “Taking Control of Enterprise Software Costs” · 2025 · software’s share of large-enterprise technology budgets, 2019–2024.
Chapter
The trap
Leaving costs more than staying — every time you check.
Extraction fees, data in proprietary formats, re-implementation, retraining. Total the cost of leaving, and staying with a vendor you no longer trust looks like the rational choice. That arithmetic is what lock-in runs on.
How we answer it. Everything is yours from day one: your person trained to run the system, the code documented and handed over with its full history, your data in open formats. Lock-in needs something to hold you with. There is nothing here that does.
Receipts: Tier2 Systems, ERP vendor lock-in analysis · 2024 · exit-cost mechanics; Panorama Consulting ERP Report · 2024 · implementation and switching timelines.
The customisations you paid for break every upgrade.
The changes that made the system fit your business are the same changes that fail when the vendor ships an update. So upgrades get deferred, versions fall behind, and the gap grows more expensive every year.
How we answer it. This is true of our own stack too, and we would rather say so than dodge it. The answer is engineering discipline: customisation written as maintainable code — documented, carrying its full history, upgradeable by anyone — never a fork that strands you.
Receipts: Trax Group, ERP customisation analysis; G2 verified reviews, Dynamics 365 Business Central; ERPNext upgrade documentation · 2023–25 · custom core code as the leading cause of upgrade failures across platforms, including our own.
The implementation that ate the year.
The industry’s median ERP implementation runs 15.5 months, and data migration is the part that classically gets underestimated: opening balances that will not reconcile at cutover, a go-live date that keeps moving.
How we answer it. We failed at this once ourselves, and rebuilt our method around the failure: one small piece at a time, live in daily use, reconciled and locked before the next is built. You keep running the business your way while the system grows around it.
Receipts: Panorama Consulting ERP Report · 2024 · cross-industry implementation-duration survey; Panorama data-migration analyses · 2019 ERP Report.
Chapter
The ground reality
Bought by the boardroom, endured by the floor.
Most business software is sold to the person who signs and shipped to people who were never asked. Management gets the dashboard. The operator gets thirty fields, too many clicks, and a workaround register kept on paper beside the terminal.
How we answer it. We learnt this from the paying side — years of being told “this is what we have, you have to use it like that.” Our bar runs the other way: easier than whatever the team uses today, including pen and paper. A floor workaround counts as our defect.
Receipts: PostHog, enterprise software buying analysis; SaaStr pricing and product commentary · 2024–25 · documented disconnect between the buyer of enterprise software and its daily users.
Reporting stops where your questions begin.
The built-in reports answer the vendor’s idea of your business. The reports you actually run on get rebuilt in a spreadsheet every Monday — by whoever exports, pastes and stitches until the numbers agree. The same numbers, typed a second time.
How we answer it. The reports you run the business on are scoped into the deployment from day one, not sold later as a BI add-on. “Exactly what you want” includes your reports.
Receipts: ERP News, third-party reporting analysis; ExpandCFO, NetSuite reporting review · 2023–24 · native ERP reporting as “starting points, not complete solutions”.
Chapter
The India reality
Too big for the package you started on, too small for the giants.
The accounting package that once ran the whole business now strains under today’s users and volumes, and the global ERPs above it are built, priced and consulted for someone much larger. The middle is where you operate. The middle is underserved.
How we answer it. That middle is exactly who we build for: full ERP capability on an open-source stack at mid-market economics — no per-user pricing, no consulting tail. And the move itself follows the piece-by-piece method, never a rip-and-replace.
Receipts: EasyReports, Tally performance analysis · 2025 · multi-user slowdown reports; PKC India, Tally-to-ERP migration guides; Frappe/ERPNext India · current open-source pricing model.
A small ledger mistake is now an automated notice.
GSTN cross-matches your returns, e-invoices, e-way bills and your suppliers’ filings against each other — automatically. A mismatched rate or an ITC gap that once surfaced quietly at year-end now arrives as a notice. This is not your accounting package failing; it is the new ground every tool stands on.
How we answer it. Compliance-correct by construction: the stack’s India Compliance layer — GST, e-invoicing — is built in, and we set control points that catch the mismatch before the portal does. That is Assurance working inside your operations, not an audit after the fact.
Receipts: GST practitioner guidance (TallyAtCloud) · 2026 · GSTN cross-matching of returns, e-invoices, e-way bills and supplier filings.
If this is your file
The fix is a conversation, not a brochure.
If more than a few of these read like your own file, bring the renewal quote, or the spreadsheet that should not exist — we will find something.