Software built around how you work

Custom software is a system built around one business’s own way of working. Instead of buying a ready-made product and bending your process to fit it, you get software that follows your steps, applies your rules and produces your paperwork.

It is worth it when the way you work is part of what makes your business good, or when ready-made software leaves you keeping spreadsheets beside it. A jewellery wholesaler that prices in grams of fine gold, a manufacturer that tracks expensive brass to the gram, and a support company with night shifts that cross midnight each needed software that could hold what made them different.

It is not always the answer. For standard jobs, such as basic accounting or email, ready-made software is cheaper and better, and we will tell you so. Often the right system is a mix: custom software for the work that sets you apart, connected to ready-made tools for everything else.

We start where the work happens, not in a meeting room. Before designing anything, we follow real orders, jobs or cases from the first call to the last document, through every team that touches them, and write down what actually happens.

That is where the useful findings are. In a Jamnagar manufacturing plant, we found that delivery dates were promised without anyone seeing how loaded the machines were, and that brass losses only showed up when the stores were counted. In a Coimbatore dispatch room, dispatchers spent their day phoning drivers for positions their GPS devices already knew. Findings like these rarely appear in a written list of requirements.

The result is a process map your team recognises: each step, who does it, what they need to know, what they produce and where things go wrong. It becomes the plan for the software, and it is often the first time the whole business has seen its own process on one page.

We need the people who do the work, the rules they follow, and one owner for the project on your side.

The people matter most. Supervisors, accountants, storekeepers and sales staff know the exceptions no document mentions: the customer who always pays late, the part that needs a second inspection, the shift that ends the next morning. We spend time with each of them, and each team checks its own part of the design before we build it.

The rules include prices, discounts, approval limits, tax and statutory rules, and the formats of the documents you send out. Copies of real invoices, challans, reports and spreadsheets help more than descriptions of them.

The owner is one person who can settle disagreements between teams and decide quickly. It is often the business owner or a senior manager who knows how all the parts fit together.

At the heart of a custom system is a single record that every team works on. An order is entered once, by the person who receives it, and then carries its details through stores, production, quality, dispatch and accounts, with each team adding its part.

That ends the retyping and the arguments. Sales, the floor and accounts look at the same order, so there is one answer to “where has it reached?” and one figure for what is owed. Every step is time-stamped, so you can see how long each stage really takes and where work waits.

Each person sees the record through their role. A supervisor on a tablet sees the job card, the drawing and the checks for the next operation. An accountant sees rates, credit and invoices. The owner sees everything, including what each team is holding and what is running late.

Your rules become part of the system, so they are applied the same way every time. A batch can’t move on until its inspection is passed. An order that would take a customer over their credit limit waits for approval instead of being refused outright. Attendance follows your own grace minutes, late marks and overtime rules, for every shift.

Approvals arrive as tasks for the right person, with the facts they need attached: the customer’s balance, the order’s value, the employee’s leave history. They can approve from a phone, and the decision is recorded with their name and the time.

Exceptions are where spreadsheets usually break, so we design for them on purpose. A rush order that must jump the queue, a part sent back for rework, a payment split across two invoices: each gets a defined path, so nobody has to invent one on a busy day.

Documents should come out of the system, not be typed beside it. Once the record holds the facts, the paperwork follows: quotations, invoices, delivery challans, packing lists, labels, payslips, certificates and letters, all in your own formats.

In India, that includes GST. A custom system can generate GST e-invoices and e-way bills through an authorised GST API provider, prepare job work challans and the details for the ITC-04 return, and send invoices to Tally so your accountant never retypes them. For the Jamnagar manufacturer, dispatch now produces the e-invoice, the e-way bill and the invoice in Tally from the same record.

For businesses elsewhere it means VAT invoices, deposits in several currencies or rooming lists, whatever your business sends out. The principle is the same: enter it once, use it everywhere.

People work in different places, so the system meets them there. Office teams use a web application on their computers. Shop-floor supervisors use rugged tablets and scan QR codes on each batch. Drivers and field staff use a phone app with large buttons, in their own language.

Apps for the floor and the road keep working when the network drops. They save what was recorded and send it when the connection returns, so a highway with no signal or a factory corner with weak Wi-Fi doesn’t stop work.

Every screen is designed with the people who will use it, for the moment they use it. A supervisor at a machine needs large buttons and few choices, an accountant needs keyboard shortcuts, and a manager needs the exceptions first.

A new system should arrive without a day when nothing works. We move over one team at a time, and the old way keeps running beside the new one until the figures match.

For a payroll system, that means running a full pay cycle in both and comparing every payslip line by line. For orders and planning, it means planners using the new board beside their spreadsheets until they trust it. Data from spreadsheets and old software is cleaned, checked and moved across before each team switches.

Training happens where people work: at their desks, beside their machines, or at the hub as drivers come in. By the time a team switches, it has already used the system on its own real work.

We agree what better looks like before we build, in your own terms. It might be how long month-end payroll takes, how often promised dates are met, how many calls the dispatch room makes to find a truck, or how many invoices are typed twice.

We record the starting point while we learn how the work moves, and measure again after each team moves over. Because the new system time-stamps every step, the later figures come from the system itself rather than from anyone’s estimate.

Custom software has to keep fitting a business that doesn’t stand still. New products, branches and customers arrive, tax and labour rules change, and a report someone needs today didn’t exist last year.

We keep the system running and change it with you. The payroll portal in our portfolio was updated for every budget and statutory change in the years after it launched, and the fleet tracking dashboard took on new routes and customers, and then FASTag toll records once FASTag became mandatory.

Because the system was built around your process, changing it usually means changing a rule or adding a step, not waiting for someone else’s next release.