CLIENT ENGAGEMENTS · REAL OUTCOMES

Work that moved
the needle.

Each engagement below begins with a real problem, describes what we actually did, and ends with a measured result. No composite clients, no hypotheticals.

Filter by sector
01
Financial services Compliance IT systems
ZeroRBI audit findings in following review
14 wksTo full controls implementation
40%Reduction in manual compliance effort
Start a similar engagement

Regulatory overhaul for a mid-size NBFC

The challenge

A Bengaluru-based non-banking financial company (NBFC) with ₹800 crore in assets under management had received adverse findings from the RBI across three consecutive quarterly reviews. Each review identified similar gaps: fragmented controls, inconsistent documentation, delayed reporting and a compliance team that was firefighting rather than working to a structured framework.

The compounding problem was technology. The organisation's compliance workflows were running across three disconnected systems — a legacy loan management platform, a standalone Excel-based reporting tool and an email-based approval process. None of them talked to each other. When a regulator asked for a complete audit trail, the team spent days reconstructing it manually.

The head of compliance had flagged the issue internally for over a year. Without structural change, the organisation was at risk of a show-cause notice and potential operating restrictions.

What we did

1
Diagnostic (Weeks 1–2)

We conducted structured interviews with the compliance, IT, operations and credit teams. We mapped every compliance obligation against the current-state process and identified where gaps originated — distinguishing between process failures, technology failures and people failures.

2
Controls framework design (Weeks 3–5)

We designed a three-tier controls framework: preventive controls (built into process design), detective controls (automated alerts and dashboards) and corrective controls (escalation protocols with named owners). Each control was mapped to its corresponding RBI circular obligation, so the compliance team could demonstrate evidence at the point of inspection.

3
Technology integration (Weeks 4–9)

We specified and oversaw the integration of the loan management system with a centralised compliance dashboard — giving the team a single view of all open obligations, deadlines and approvals. Manual Excel reporting was replaced with automated extracts, reducing human error and saving approximately 18 person-hours per week.

4
Training and embed (Weeks 10–14)

We ran structured training sessions for the compliance team on the new framework and tools, created an operations playbook for each compliance process, and established a monthly management review rhythm. We stayed on retainer for the first RBI review under the new system, supporting the team through the inspection and responding to regulator queries in real time.

The outcome

The organisation's next RBI quarterly review — four months after engagement start — returned zero adverse findings. The inspector specifically noted the quality of the audit trail. The compliance function, which had previously operated reactively, now runs on a structured monthly cadence. Manual compliance effort fell by 40%, freeing the team to focus on emerging obligations rather than retrospective documentation.

"POLI didn't just fix our compliance gaps — they redesigned how our finance team thinks about risk. The RBI review that used to keep us up at night was the smoothest we have ever had."— Director of Finance, Mid-size NBFC, Bengaluru
02
Technology & SaaS Finance transformation
₹42 CrSeries A closed 6 months post-engagement
8 wksTo investor-ready financial model
Faster month-end close
Start a similar engagement

Finance function built for Series A scale

The challenge

A Pune-based B2B SaaS company with 60 employees and ₹8 crore in annualised recurring revenue was preparing for its Series A fundraise. On paper, the business looked ready: strong growth, improving unit economics, a product with genuine enterprise traction. In practice, the finance function was not.

Revenue recognition was inconsistent — different contracts were being accounted for differently, which meant their stated ARR figure could not be defended in an investor data room. Month-end close took three weeks and involved the founders manually reconciling spreadsheets. There was no board-level financial reporting, no variance analysis and no cash flow forecast beyond 90 days.

Two investor conversations had already stalled because the team could not answer basic diligence questions with confidence. The founders knew they needed help, but had never prioritised finance — and had no clarity on what "investor-ready" actually meant in practice.

What we did

1
Baseline and gap assessment (Weeks 1–2)

We reviewed three years of management accounts, all existing contracts and the company's current tech stack (QuickBooks, a manual payroll spreadsheet, and a basic CRM). We identified ten specific gaps between where they were and where a Series A investor would expect them to be — and prioritised them by investor impact.

2
Revenue recognition fix and restatement (Weeks 2–4)

We worked with the founding team to establish a consistent Ind AS-aligned revenue recognition policy, applied it retrospectively across the contract portfolio and produced a restated revenue schedule that could withstand investor scrutiny. The restated ARR was actually 11% higher than what they had been reporting — the inconsistency had been understating revenue.

3
Financial model and investor reporting (Weeks 3–8)

We built a bottom-up, driver-based financial model covering three scenarios (base, upside, stress), integrated with a 24-month cash flow forecast and a standard SaaS metrics dashboard (ARR, NRR, CAC, LTV, payback period, churn by cohort). We also designed a monthly board pack template and ran two board reporting cycles with the founders before the fundraise.

4
Systems and close process (Weeks 5–10)

We oversaw the migration from QuickBooks to a more appropriate accounting platform, established an automated bank reconciliation workflow and redesigned the month-end close process. Close time reduced from three weeks to five days. We documented the entire finance operations process so that a future finance hire could onboard without institutional knowledge dependency.

The outcome

The company re-entered investor conversations six weeks after the engagement started. The Series A — ₹42 crore from a Tier 1 Indian VC — closed five months later. The lead investor specifically cited the quality of the financial model and the clarity of the data room as unusual for a company at that stage. Month-end close now runs in five days. The finance function, which previously consumed 15–20% of the co-founder's time, now runs autonomously under a part-time finance manager.

"Within eight weeks we had a financial model our investors could trust and a reporting rhythm our board actually valued. POLI bridged the gap between where we were and where a Series A company needs to be."— Co-founder & CEO, B2B SaaS startup, Pune
03
Consumer & retail Operations Tech integration
+9 ptsGross margin improvement in 2 quarters
22%Reduction in food & labour cost variance
12Locations on unified tech-enabled model
Start a similar engagement

Margin recovery for a multi-city F&B brand

The challenge

A fast-growing restaurant group — a contemporary Indian casual dining concept — had expanded from two outlets in Bengaluru to twelve across four cities in eighteen months. Revenue was growing. Margin was not. Gross margin had declined from 68% at the original two outlets to 58% across the expanded portfolio — and the gap was widening with each new city added.

The management team knew something was wrong but could not pinpoint where. The POS system at each outlet was different. Inventory was tracked manually at some locations, not at all at others. Purchasing decisions were being made by individual outlet managers, without visibility into what other sites were paying for the same ingredients. Pricing had been set location by location, without a central logic.

The group's founders had raised ₹15 crore in growth capital and had committed to opening eight more locations in the following year. If the operating model did not improve before that expansion, each new outlet would compound the margin problem further.

What we did

1
Cost and variance diagnostic (Weeks 1–3)

We spent two weeks across four outlet types — a flagship, a high-street format, a mall location and a delivery-focused dark kitchen — documenting actual versus theoretical food cost for 60 menu items, conducting labour time-and-motion studies and benchmarking purchasing prices against market rates for key inputs. We identified that food cost variance alone was 14 percentage points above what it should have been at a well-managed comparable operation.

2
Menu and pricing rationalisation (Weeks 3–6)

We rebuilt the menu engineering model from scratch — calculating true contribution margin per item across raw material, labour and waste factors. Seven menu items were removed (high complexity, low margin), four were repriced (below market despite premium perception), and three new items were introduced that leveraged existing inventory. A unified pricing policy was established across all formats, with defined location-level adjustments.

3
Technology and procurement integration (Weeks 5–10)

We oversaw the standardisation of the POS platform across all twelve outlets, the implementation of a centralised inventory management system connected to purchasing, and the creation of a single vendor panel with negotiated rate cards for the group's top 40 ingredients. Purchasing authority was restructured — daily orders remained with outlet managers, but weekly procurement and vendor selection moved to a central function.

4
Operating model and training (Weeks 9–14)

We designed a standard operating model for each outlet format, covering shift structure, prep schedules, waste management procedures and end-of-day reporting. We trained outlet managers on the new systems and financial accountability framework, and established a weekly operations dashboard that allowed the central team to see food cost, labour cost and gross margin per outlet in real time.

The outcome

Gross margin recovered from 58% to 67% within two quarters of the engagement — a nine-point improvement worth approximately ₹2.1 crore annualised at the current revenue run rate. Food and labour cost variance across the portfolio fell by 22%. All twelve locations are now operating on a single tech-enabled model, with the central team able to identify and address performance outliers within 24 hours rather than waiting for month-end accounts.

The group has since opened four additional locations using the same operating model. Each new outlet reached target margin within six weeks of opening, compared to the previous average of eighteen months.

"They asked better questions than anyone we'd worked with before. The operating model they built is still running two years later — with zero modifications. That's what good work looks like."— Managing Partner, F&B Group, Bengaluru
04
Professional services Growth & revenue
34%Revenue per partner increase in year one
3 newRetainer products launched in 10 weeks
60%Revenue now from recurring mandates
Start a similar engagement

Revenue model redesign for a Bengaluru law firm

The challenge

A 45-lawyer Bengaluru firm with a strong reputation in litigation and regulatory advisory had been billing almost exclusively on hourly rates for fifteen years. The model had worked when the firm was smaller. At its current size, it was creating three interconnected problems.

First, revenue predictability was poor. The firm could not forecast annual revenue with any confidence, because it depended on matters being filed, which depended on client decisions outside their control. Budgeting, hiring and investment decisions were all made in a state of structural uncertainty.

Second, client relationships were transactional. Because the firm only engaged with clients when a matter was active, there was no institutional relationship between engagements. Mid-market clients — the firm's target segment — were moving larger mandates to bigger firms that offered broader coverage, even when POLI's client had superior technical expertise.

Third, the hourly model made it structurally impossible to reflect the actual value of senior partner involvement. A one-hour conversation that resolved a complex issue was billed at the same rate as a one-hour document review. Revenue per partner had plateaued for two years as a result.

What we did

1
Client and revenue analysis (Weeks 1–3)

We analysed five years of billing data by client, matter type, partner and practice area. We identified the firm's twenty most valuable client relationships by total revenue, matter frequency and referral behaviour — and compared actual billing against estimated value of work performed. The gap revealed significant under-charging on complex regulatory advisory and consistent over-investment in small-ticket litigation matters.

2
Retainer product design (Weeks 3–7)

We worked with the firm's partners to design three structured retainer products for their core client segments: a General Counsel retainer for mid-market companies without in-house legal (₹1.5–4 lakh/month, covering unlimited advisory access, monthly risk review and priority matter handling); a Regulatory Monitoring retainer for compliance-heavy sectors (₹75,000–1.5 lakh/month, covering regulatory watch, impact assessments and two advisory hours); and a Transaction Support retainer for active deal teams (scoped per quarter). We priced each product based on value delivered, not hours worked.

3
Pilot and iteration (Weeks 6–10)

We identified eight existing clients as ideal candidates for the General Counsel retainer based on billing history and relationship strength. The managing partner personally presented the new model to each — we prepared the pitch materials, pricing rationale and objection responses. Six of eight converted. Two declined but remained hourly clients. The pilot generated ₹22 lakh in monthly recurring revenue before the broader rollout.

4
Operations and systems (Weeks 8–14)

We redesigned the firm's internal matter management and billing systems to support recurring-revenue products — introducing a simple CRM to track retainer deliverables, automate monthly invoicing and monitor utilisation per client. We also restructured the partner review process to separate retainer client management from matter-based work, so that ongoing relationships received consistent senior attention rather than getting deprioritised during active litigation periods.

The outcome

In the twelve months following the engagement, revenue per equity partner increased by 34% — the largest single-year improvement in the firm's history. Three retainer product lines were live within ten weeks of engagement start. By the end of year one, 60% of total firm revenue was coming from recurring mandates, compared to near-zero at the start of the engagement.

The structural benefit has compounded: the firm now enters each financial year with a visible revenue base, which has made hiring, investment and expansion decisions significantly easier. Two new partners have been admitted in the two years since the engagement, funded directly by the improved revenue visibility.

"POLI helped us see something we could not see from inside. The retainer model felt risky at the time. Within six months it was the most obvious decision we had made in years."— Managing Partner, Litigation & Regulatory Advisory Firm, Bengaluru

READY TO START?

Your engagement begins with a conversation.

Tell us what you are working through. We will respond within one business day with a senior advisor who has relevant experience — no forms, no junior handoffs, no sales process.

Request a consultation Chat on WhatsApp
Chat with us