Systems we've built, and what they changed.
A few of the systems we've built for clients: the manual process they started with, what we built, and what changed. Real engagements, written up honestly.
Law-firm ERP
Sales pipeline CRM
Manufacturing ERPSales pipeline CRM for a multi-product distributor
Replaced a six-person shared-Excel lead register with configurable stages, weighted forecasts, dual SSO, a contact graph, and full audit history.
Section 138 cheque-bounce case management
A deadline engine that auto-computes statutory windows under the Negotiable Instruments Act 1881, with audit logs and Power Automate reminders.
Law-firm ERP with a Copilot Studio bot
Matter management, billable hours, a four-step invoice approval on Power Automate, GST-ready invoicing, and a Copilot bot grounded on the firm's own data.
Where each one started, and what changed.
Before
Six salespeople shared one Excel lead register. Stage names drifted from row to row, closed-lost deals were deleted, and two reps quoted the same architect on different projects without knowing. Answering “what is our committed pipeline this quarter?” took two days of cleanup.
After
A CRM with six fixed stages, sign-in through the accounts each team already used, a contact graph linking architects and contractors to their projects, and a field-level history of every change. Pipeline reviews now run off one number.
Before
Bounced cheques were tracked by hand in a paper file and spreadsheets. Each one starts three statutory clocks under Section 138 of the Negotiable Instruments Act, and one missed window ends the claim.
After
A deadline engine computes all three dates from the return date, flags cases close to a deadline, and drafts the statutory notice from case data for a lawyer to review. Every change is logged for board review.
Before
Invoices took twelve days on average from draft to client, and one waited 41 days for a partner who was in trial in another city. Conflict checks were an email to practice heads, and matter status lived in individual inboxes.
After
One ERP for matters, conflict checks across current and historical parties, billable hours, a four-step invoice approval on Power Automate, SharePoint document control, and a Copilot Studio bot that answers questions from the firm's own records.
What these have in common
None of them started with software. Each started with a requirement study: sitting with the people doing the work, writing down how it actually ran, workarounds included, and agreeing the scope in writing before anything was built. That is why each system uses the client's own words, the law firm's “matters” and Ceiling Impex's own stage names, and why all three are still in production. The manufacturing ERP we built for Bollard (Complete Infrastructure Pvt. Ltd.) followed the same process; it is not written up here.
Tell us what's slowing you down.
A 30-minute discovery call. We map the process, point out the easy wins, and outline a clear plan (no obligation).