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

The firm's consultants were recording time in weekly Excel timesheets submitted late and often reconstructed from memory, which made utilisation reporting directionally useful at best and engagement profitability effectively unmeasurable. Client deliverables lived in shared drives with version control by filename convention, which had already produced one incident where a superseded draft reached a client. Billing was manual: someone assembled time entries, applied engagement-specific rate arrangements, and produced invoices — a multi-day exercise each month with errors that surfaced as client queries. Because the firm bills clients in several ASEAN jurisdictions with different entities and currencies, invoicing carried complexity that a simple time-and-rate calculation could not handle. Singapore's PDPA obligations applied to client data held in those documents, and the firm had no reliable way to answer where a given client's data actually was. They were also conscious of IRAS's phased InvoiceNow requirements and did not want to build something that would need replacing.

We built the platform on Next.js with a Node.js API and PostgreSQL. Time capture was designed for the reality that consultants do not enjoy timesheets — entry takes seconds, works on a phone, and prompts based on calendar activity rather than presenting an empty grid on a Friday afternoon. Engagements carry their own rate arrangements, currency and billing entity, so invoice generation applies the right terms automatically instead of relying on someone remembering the arrangement. Document management includes real versioning with an explicit released-to-client state, so a draft cannot be confused with an issued deliverable — a direct response to the incident that prompted the project. Files are stored with per-engagement access scoping so the firm can answer a PDPA question about where a client's data sits and who has touched it. Stripe handles payment collection for the engagements billed that way, and the invoicing layer was structured so that a Peppol-based InvoiceNow path can be added without reworking how invoices are produced. Utilisation and engagement margin report from live data rather than a quarterly assembly exercise. Historical time and billing data was migrated so utilisation trends span the period before the platform existed, which mattered to a partnership that reviews performance annually. Document migration preserved the existing folder structure rather than imposing a new taxonomy nobody had agreed to. Related: custom software development and cloud solutions.