What the cobbled stack does well
Be fair to it. Notion, Slack, and Drive are cheap or free, everyone already knows them, there is no procurement cycle, and they bend to whatever you need this week. That is exactly why so many partner firms run on them. It is not a bad stack. It is a stack that worked.
Where the workaround stops working
None of these tools talk to each other. Discovery lives in Notion, decisions happen in Slack, files sit in Drive, and the connective tissue between them is human memory and copy-paste.
- It runs on recall. The system works as long as the whole business fits inside what your team can remember. Past roughly ten people, it does not.
- Answers get slow. “What did sales actually promise this client?” or “which requirement was this task for?” becomes a twenty-minute archaeology project.
- The knowledge walks out the door. When the person who held the structure in their head leaves, the structure leaves with them.
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 | Cobbled stack | PartnerView |
|---|---|---|
| Cost to start | Low | Paid |
| Flexibility | High | Structured around the partner model |
| Tools that talk to each other | No, joined by hand | Yes, one system |
| Survives past 10 to 15 people | No | Yes |
| Fast answers across the engagement lifecycle | No | Yes |
| Knowledge held by the system, not a person | 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 cobbled stack is the right call
If you are a handful of people and the whole business genuinely fits in shared memory, the cobbled stack is fine, and you do not need PartnerView yet. The question is not whether it works today. It is whether you want the firm to keep depending on memory as it grows.