Void Magic Start a project

We build business software that fits how you actually work.

The systems off-the-shelf software can't cover: ERP, inventory, operations, reporting. Thirteen years of enterprise experience, now available to your business.

Based in Kerala · Working with businesses across India

The problem

When the spreadsheet stops being enough

Most growing businesses hit the same wall. Tally handles the accounts. A packaged app handles one department. Everything in between — the part that's actually your business — lives in spreadsheets, WhatsApp groups and someone's memory.

Generic software makes you change how you work to fit it. That's fine until the way you work is your advantage. Then you need something built around you.

That's the only thing we do.

Where packaged software stops A single span representing everything a business does end to end. Accounting software claims a small block at one end and a packaged departmental app claims another at the far end. The wide territory between them is unclaimed, and holds production planning, approvals, reporting, stock movement, buying plans, outlet sales, job work, costing and reconciliation. Everything your business actually does, end to end Covered Accounts Ledgers · GST Covered Packaged app One department Everything in between — this is your business Production planning Approvals Reporting Stock movement Buying plans Outlet sales Job work Costing Reconciliation We build here
Accounting claims one end of the span. A packaged app claims a department at the other. Everything between them is where the business actually runs — nine different jobs, and nothing off the shelf fits any of them.

What we build

From one screen to a whole system

ERP & manufacturing

Inventory, procurement, job work, production planning, costing. Built for how goods actually move through your business, not a textbook version of it.

Sales & distribution

Order to cash, multi-outlet stock, franchise and dealer operations, billing that keeps working when the internet doesn’t.

Operations & workflow

Task management, approvals, field reporting, internal portals. The unglamorous systems that decide whether a week runs smoothly.

Reporting & dashboards

One number, one source. Reports your management team actually opens, on the phone, on Monday morning.

Mobile, web & desktop

The same system wherever your people are — shop floor, showroom, warehouse, head office.

Integrations

Connecting what you already run — accounting, payments, logistics, existing databases — instead of replacing it all at once.

Marketing sites

A site for the business itself — built quickly, handed over clean, yours to edit. Often the first thing we build for a client, and rarely the last.

What we've built

The problems, without the names

Our work is under client confidentiality, so we describe it without naming names. The problems, and how we solved them, are real.

01 · Apparel manufacturing

Fabric to finished goods, without the spreadsheets

Purchasing, job work and stock were tracked across separate spreadsheets, with fabric bought by weight and consumed by length — so nobody could say what was really in stock. We built an inventory core that handles dual units of measure with variance reconciliation at the job-work stage, connected to procurement, production and costing.

Stock positions accurate to the day.
Dual unit-of-measure reconciliation Four stages. Purchase: the supplier invoices fabric by weight in kilograms. Receipt: stock is booked in metres at a provisional conversion factor. Job work: the unit measures the length that actually rolls off. Stock ledger: everything is held in one base unit. The difference between the provisional figure and the measured one is posted back against the receipt as a variance, so the ledger corrects itself rather than drifting. Bought in KG Consumed in MTR Purchase By weight · KG Receipt Provisional factor Job work By length · MTR Stock ledger Base unit Variance posted back on actual consumption This is where stock usually drifts
Bought by weight, consumed by length. The receipt converts on a provisional factor; actual consumption at the job work unit posts the difference back, so the ledger stays true instead of drifting.

02 · Multi-outlet retail

Billing that doesn't stop when the connection does

Outlets spread across a wide area, hundreds of bills a day at each, and unreliable connectivity at several of them. We designed a local-first architecture: each outlet holds its own stock and bills offline, syncing to the central system whenever the network returns.

Head office sees consolidated sales. No counter ever waits on a network.
The offline badge is the only thing on this screen that changes when the connection drops. Everything else — stock, pricing, the payment button — keeps working off the outlet’s own copy.

03 · Buying & merchandising

A planning cycle that used to run on email

Purchase planning moved between outlets, head office and suppliers as emailed spreadsheets, with no record of who changed what. We built a staged approval workflow — outlet plan, central review, supplier confirmation — with full version history and an audit trail on every change.

Every revision traceable to a person and a date.
The screen that replaced the email thread. Version 3 of the same plan — not a third spreadsheet — with every change and every send-back attached to the record underneath it.

04 · Systems integration

Opening the system to the tools around it

As the business grew, other software needed access to the core data — and handing out staff logins was not an option. We built scoped, revocable API access, separate from user accounts, so partners and internal tools read exactly what they're entitled to and nothing more.

Access granted per client, revoked in one step.
Each key carries only the scopes it needs and can be revoked on its own line. Turning off the marketplace feed in March affected nobody else — no shared password to rotate, no staff account touched.

Every one of these started as a conversation about a process, not a request for software.

How we work

Four stages, in this order

01

Understand the process

We spend the first stretch watching how the work is actually done — which usually differs from how it's documented. Nothing gets built until we can describe your process better than the brief did.

02

Show something small, early

A working prototype of the part that matters most, in weeks. Feedback on something real beats sign-off on a document.

03

Build in stages, live early

One module at a time, in your hands and in use. You see progress you can measure, and we course-correct while it's still cheap to.

04

Hand over properly

Documentation, training, and a team that can run the system without us. We'd rather you stayed because it's working than because you're stuck.

Who we are

Thirteen years inside businesses like yours

  • 13years building enterprise systems
  • 3platforms — mobile, web, desktop
  • 1system build at a time — smaller work runs alongside

Void Magic is built on thirteen years of designing and shipping enterprise systems — ERP for manufacturing and retail, task and reporting tools, applications across mobile, web and desktop.

That experience came from inside large, complicated businesses, where software either earns its keep every day or gets quietly abandoned. It taught us the thing most software gets wrong: a system people avoid using is worse than no system at all. So we design for the person on the shop floor at 9am first, and for the feature list second.

We take on a small number of projects at a time. That's deliberate.

Contact

Tell us what you're trying to fix

No sales call, no obligation. Describe the problem in a few lines and we'll tell you honestly whether we're the right people for it — and roughly what it would take.

We reply within one working day.