Revenue & Operations Intelligence Platform
Data integration · Analytics · Built for an enterprise quality-software company
Proprietary Project.
Image not available
Outcome
Leadership's first single view of account health, cost-to-serve and team capacity.
The challenge
Revenue, time and recurring-revenue records lived in three systems with no shared key. Leadership could not reliably answer which accounts were at risk, which were profitable, or whether the team had capacity, and monthly reporting was slow manual reconciliation.
How I led it
Architect and lead analyst, built alongside full delivery responsibilities.
What I delivered
A repeatable Python pipeline that matches records across the three systems, scores every account's health, and produces refreshable executive dashboards that non-technical teams can filter themselves.
- ChallengeThree systems, no shared key.SolutionNormalization and fuzzy matching link accounts across time, customer relationship management (CRM) and revenue data.
- ChallengeNo early warning on at-risk accounts.SolutionExplainable 0–100 health score weighting revenue, recent engagement and service investment, tiered Critical to Healthy.
- ChallengePlans assumed one person per task.SolutionAnalysis showed most milestones need 2–3 people, which reshaped scoping and capacity planning.
- ChallengeReporting depended on one analyst.SolutionScripted refresh any team member can run, plus role-specific quick-start guides.
Key features
- ·Master analytics workbook with executive KPIs
- ·Cost-to-serve and gross margin by account
- ·Team utilization and task-type analysis
- ·Milestone scheduled-vs-actual tracking
- ·Interactive web dashboard with heatmaps and roadmap
Notable & novel components
- ·Explainable account health scoring engine
- ·Three-way cross-system record matching
- ·Scheduled-vs-actual assignment gap discovery
Tech stack
Details generalized and figures withheld to protect confidential employer information.