Business Management Platform for Ash**** Advisory, SingaporeCase Study

Time capture was the weakest link. Consultants filled in weekly Excel timesheets, usually late and often from memory, so utilisation figures were rough indicators at best and engagement profitability could not be measured with any confidence. Partners were effectively reviewing performance on quarterly guesswork, and fixed-fee scoping had no reliable feedback loop.

Deliverables sat in shared drives where versioning depended on filename conventions. That approach had already failed once, when a superseded draft was sent to a client — exactly the kind of incident an advisory brand cannot afford to repeat. Billing compounded the pain: someone had to gather time entries, recall each engagement's rate arrangement and produce invoices by hand, a multi-day monthly exercise that generated client queries whenever a detail slipped.

Cross-border invoicing across ASEAN entities and currencies added complexity a simple hours-times-rate model could not absorb. On the compliance side, client documents held personal data covered by Singapore's Personal Data Protection Act, yet the firm could not say with certainty where a given client's files lived or who had accessed them. Leadership also wanted any new invoicing approach to accommodate IRAS's phased InvoiceNow rollout rather than become an obstacle to it.

PapaSiddhi designed an engagement management platform with a Next.js front end, a Node.js API and a PostgreSQL database. Time entry was rethought around consultant behaviour: logging takes seconds on a phone, and a Calendar API integration prompts entries from actual meetings instead of confronting people with an empty grid at the end of the week. Each engagement stores its own rate arrangement, currency and billing entity, so automated invoice generation applies the correct commercial terms without relying on anyone's memory.

Document management introduced genuine version history and an explicit released-to-client state, making it impossible to confuse a working draft with an issued deliverable. Files are scoped per engagement, giving the firm a clear audit trail of where client data sits and who has touched it — built with PDPA accountability in mind. Stripe handles card collection where engagements are billed that way, an email service carries notifications, and the invoicing layer was structured so a Peppol-based InvoiceNow route can be added later without reworking invoice production.

Delivery was a fixed-price engagement. Historical time and billing records were migrated so utilisation trends extend back before go-live, important for a partnership that reviews performance annually. Documents moved across in their existing folder structure rather than under an imposed taxonomy, and live utilisation and engagement margin dashboards replaced the quarterly assembly exercise.