We take on transaction processing and back office work that our clients cannot economically run in-house, and we build the software that supports it. In practice that falls into four areas: data processing solutions, custom software development, e-commerce applications, and IT and back office services. The common thread is volume — work that arrives in cycles, has to be accurate, and has to be finished by a fixed time.
Since 1984, from Mumbai. The company marked its silver jubilee in 2009 and has been operating continuously since. We run two locations: a corporate office and delivery centre at Laxmi Industrial Estate in Andheri (W), and a branch office at Hindustan Building, Kalbadevi.
There is no fixed floor, but the economics matter to both sides. Below roughly a few thousand transactions a month, the cost of transition and controls usually outweighs the saving, and we will say so rather than sell you an engagement that will not pay for itself. Where volume is small but growing or seasonal, a dedicated-team or project engagement often works better than per-transaction pricing.
Client engagements are segregated physically and logically. Access is granted by role, reviewed periodically and logged. Media handling is controlled from receipt through to destruction, and every batch carries an audit trail you can follow end to end. Staff are under confidentiality obligation. Nothing about your volumes, your process or your customers is shared, cited or reused — including as a client reference without your written agreement.
It depends on the complexity of the process and how well documented it already is, but the sequence does not change: process mapping, runbook, operator training, then a parallel run against your existing output. You sign off on accuracy before we take live volume. A well-documented single-stream process can move through that in weeks; a multi-product operation with many exception paths takes longer, and we would rather say so at scoping than discover it at go-live.
Accuracy and turnaround targets are agreed per process before go-live, because a payments cycle and a document indexing queue do not deserve the same numbers. Whatever is agreed is what we report against on your cycle: volume handled, accuracy sampled by an independent quality team, turnaround achieved, and exceptions outstanding with their age. Where we miss, you hear it from us with the cause and the correction.
Yes, and often that is the better arrangement. Processing directly in your application over controlled access keeps your data in your environment and your audit trail in one place. Where that is not practical we process in our environment and return output in your format, with reconciliation performed on both sides. Either way, integration is scoped and tested during the parallel run rather than improvised after go-live.
Four models, chosen to fit the work rather than the other way round: per transaction for steady processing volume, per seat for a dedicated team running your process, a monthly fee for a fully managed operation, and fixed scope for software projects. We do not publish rate cards, because a rate that ignores your exception rate and cut-off times is a number without meaning. Send us the volumes and we will quote against them.
Banking, financial services, life insurance, general insurance, CRM operations and retail. That experience matters most in the exception paths — knowing which mandate mismatches are worth chasing, which policy servicing requests need referral, and which retail reconciliation breaks are timing rather than error.
A named contact who knows your process, not a queue. Customer service is the cornerstone of the microcom business philosophy, and in practice that means a response within the working day and an escalation path that reaches someone empowered to decide rather than someone empowered to apologise.
