Why we built OpsBridge — and what it taught us about running a governed services business

When we started SYSTEMBENDER in late 2023, we did what most early-stage staffing businesses do — we patched together a system from whatever tools were available. Timesheets in Google Sheets. Invoices in Zoho. Contracts in email threads. Leave requests via WhatsApp. Payroll worked out manually at month end.

It worked. Barely. And only because the team was small enough that everyone could hold the whole picture in their head at once. By mid-2024, with 18 people and a growing contractor base across India, Singapore, Malaysia and the UK, it stopped working entirely.

Why we couldn't just buy something off the shelf

We looked. There are plenty of HRMS and staffing platforms out there — Zoho People, Keka, greytHR, BambooHR. Some are good. None of them were built for the specific problem of an Indian staff augmentation business placing contractors internationally.

The core gap: most platforms are built for a single-entity, single-jurisdiction workforce. We needed to track contractors billing in SGD to a Singapore client, with the revenue flowing into an Indian entity, GST calculated on the Indian invoice, and the contractor paid in INR — all from the same timesheet approval. Not one platform handled this chain end-to-end. We were always stitching two or three tools together, and the joins were always where things broke.

What OpsBridge actually does

We built OpsBridge to solve our own problem first. The core loop is simple but critical: a contractor submits a timesheet → a manager approves it → an AR invoice is automatically generated in GST-compliant format → the invoice is sent via a payment run → when it's paid, the AP bill for the contractor is created → payroll is calculated. One approval triggers the entire chain.

It runs at ops.systembender.com — and we use it every day to run our own business.

The things we got wrong on the first attempt

Building internal tools is humbling. You think you know your own workflows until you try to encode them in software and realise how much tribal knowledge you've accumulated that nobody has ever written down.

Three things bit us hardest:

• Access control is harder than it looks. Who can see which contractor's rate card? Can a manager see payroll? Can a contractor see other contractors' timesheets? We rewrote the RBAC layer twice before we got to something that felt right.
• GST edge cases are endless. Forward charges, reverse charges, place of supply rules, TDS implications for contractors — Indian tax compliance is not something you can bolt on at the end. It has to be in the data model from day one.
• Approval workflows need to be opinionated. We initially built a flexible, configurable workflow engine. Nobody used the flexibility — they just wanted things to work the obvious way. We simplified it dramatically and adoption improved immediately.

What's coming next

OpsBridge is live and handling our own operations. The next phase is an AI intelligence layer — document OCR and classification for contracts and invoices, explainable work queue ranking (why is this item urgent, what should I do next), and a copilot that can draft invoices, summarise approvals, and flag exceptions automatically.

We're also opening it up to other services companies — staff augmentation agencies, IT services firms, and multi-entity businesses managing employees, contractors, and clients across India, Singapore, and Malaysia. If you're running on a patchwork of spreadsheets and you recognise the pain we described — we'd love to talk.

Today, OpsBridge is used in production to run Systembender's own operations — managing employees, contractors, vendors, clients, timesheets, billing, payroll, and compliance across India, Singapore, and Malaysia. Every approval is logged. Every invoice traces back to an approved timesheet. Every payroll run has a statutory-compliant audit trail. It is the system of record we wished had existed when we started. We are now making it available to other services businesses who are at the same inflection point we were.