What the spreadsheet does well
Be fair to the spreadsheet. It is free, it is flexible, everyone can use it, and it bends to whatever shape you need this week. That is exactly why it became the operating system for so many partner services firms. It is not a bad tool. It is a workaround that worked.
Where the workaround stops working
The spreadsheet is not really a tool in your stack. It is the integration layer. It is the one thing that touches the CRM, the PSA, and the accounting system, and it holds them together by hand.
That has a cost, and the cost compounds:
- It is maintained by a person. Every reconciliation, every commission check, every capacity update is manual. The work is the tax.
- It is fragile. The logic lives in one person’s head and a tab nobody else fully understands. When that person is busy or gone, the firm is flying blind.
- It does not scale. At ten people the spreadsheet is fine. At thirty it is a liability, and the firm usually does not notice the moment it stopped working.
We wrote about this at length in the partner services operating tax. The short version: the spreadsheet feels free, and it is the most expensive thing you own.
What PartnerView does instead
- Append-only audit log. Permission grants, settings edits, retention policy edits, lock and unlock cycles, trash and restore events. No UI or API path can mutate or delete an audit row.
- Trash and retention substrate. Soft-delete on every entity with 14 retention policies; daily auto-purge cron at 04:00 UTC; snapshot-on-purge with 30-day emergency recovery; admin trash console at /admin/trash.
- Entity history on every write. Full row JSON snapshot per insert, update, soft-delete, and restore; field-level and word-level diff views; cross-entity batch restore via change_batch_id.
- Daily off-site backups. R2 backup cron at 06:00 UTC, 7-day retention, restore dry-run preview, backup audit log.
- 71 named reports across 16 domains. Sales, deals, partners, finance, escalations, MSP, payroll, HR, onboarding, offboarding, time, permissions, subco, compensation, revenue, tasks. Every report exports to xlsx, CSV, and PDF.
Side by side
| Capability | Spreadsheets | PartnerView |
|---|---|---|
| Cost to start | Free | Paid |
| Flexibility | High | Structured around the partner model |
| Commission reconciliation | Manual, by hand | Modeled and flagged automatically |
| Resourcing and capacity | Manual, by hand | Tracked as data |
| Subcontracting terms and timing | Manual, by hand | Modeled |
| Survives the person who built it | No | Yes |
| Scales past thirty people | No | Yes |
| Append-only audit log across governance events | No | Yes |
| Trash, retention, and entity history | No | Yes |
| Daily off-site backups with restore dry-run | No | Yes |
| 71 named reports with xlsx/CSV/PDF export | No | Yes |
When the spreadsheet is the right call
If you are a few people and the whole business fits in one head, the spreadsheet is genuinely fine, and you do not need PartnerView yet. The question is not whether the spreadsheet works today. It is whether you want the business to keep depending on it as it grows.