Status: Demo Project (Self-Directed Practice Work)
Anand Advisory is a fictional 4-person boutique management consulting firm, founded and run day-to-day by a single owner-operator, Priya Anand. As the firm grew, its founder remained the sole point of contact across every client engagement — and every operational process lived entirely in her head, notebook, or scattered messages.
This created five compounding problems: meetings produced no systematic follow-up, no documented procedures existed for core processes like onboarding, project status was invisible to the small team, the inbox mixed urgent client requests with routine noise, and there was no way to get a weekly view of what was actually happening across engagements. The underlying issue wasn't a lack of effort or discipline — it was that nothing had been externalized into a system the rest of the team could work from.
I began with an intake brief and a full architecture-planning pass before opening any tool — mapping how meetings, tasks, projects, and reporting needed to connect, and deciding where each piece of data should live before building anything.
From there, I built a Notion-based system with three linked databases (Meetings, Tasks, Projects), connected through relation properties so that every task automatically traces back to the meeting and client engagement it came from. I configured a button-based automation on each meeting record that instantly generates a linked task in a single click — the practical equivalent of the "automatic" behavior the scenario called for, adapted to what the tool could actually support.
I documented four core SOPs (client onboarding, meeting prep and follow-up, weekly reporting, and inbox triage) as plain reference pages, reasoning that process documentation didn't need database complexity since nothing needed to filter or query against it. I built a client/project tracker with both a status-based board view and a deadline-based timeline view, plus filtered task views per client engagement. I then constructed a Weekly Ops Report that pulls live from the task data itself — surfacing what shipped, what's blocked, and what's due next — rather than being manually compiled each time.
To avoid the system reading as an empty template, I populated it with two simulated weeks of realistic activity: new meetings, tasks moving through statuses, and one re-engaged client project — so the reports and views show a system genuinely in motion.
Throughout the build, I caught and corrected several real design issues before they could mislead a user of the system — including a case where a task's displayed status no longer matched its actual state, and a gap where one legitimate task-completion order (inventory confirmed before compliance) had no corresponding status option. Each was fixed at the root rather than patched superficially
As a demo project, there are no real client outcomes or measured business results to report, and none are claimed here.
What exists is a fully functional, tested system: three interlinked databases with working automation, four documented SOPs, a multi-view project tracker, and a live weekly reporting mechanism — all verified end-to-end with realistic simulated data rather than left as an untested template. The intended value, in a real engagement, would be eliminating the single-point-of-failure risk of one founder holding all operational knowledge, and reducing weekly reporting from a manual compilation task to a near-instant review.