Making proposal reporting tell the truth
- Client
- Solar racking manufacturer, US and Canada
- Platforms
- HubSpot, PandaDoc, Looker Studio
- Work
- Integration, reporting, data clean-up
Where it started
The sales team used PandaDoc for proposals and HubSpot for deals, but the native integration couldn’t give them the proposal and revision reporting they needed. Pipeline views and data needed attention too.
What I built
- A rebuilt PandaDoc–HubSpot integration using custom APIs
- A proposal dashboard tracking revisions and proposal KPIs
- Pipeline management and deal record views
- Looker Studio reporting
- Property and data clean-up
What I learned
The reporting assumed everyone used PandaDoc the same way. They didn’t. Some people sent PDFs outside it; others sent through it with signatories. Some revisions were new copies, others were edits to the same document.
The fix I proposed wasn’t more code. It was one shared habit: every client-facing revision becomes its own document, linked to the deal. Then the revision count finally means something.