What a partner services firm's tech stack actually looks like
Seven tools, none of them talking, and a spreadsheet doing the job all seven were supposed to do together.
Ask a partner services firm what runs their business and you will not get one answer. You will get a list.
The typical stack, honestly inventoried
- A CRM for the sales pipeline
- A PSA or project tool for delivery
- An accounting system for the books
- A spreadsheet for commission tracking
- Another spreadsheet for resourcing and capacity
- A folder of SOWs for subcontracting terms
- A standing weekly meeting to reconcile all of the above
Each tool is good at its slice. None of them were built to know about the others.
Where each one goes blind
- The CRM cannot see delivery, so it stops at closed-won
- The PSA cannot see the sale, so it starts at the SOW
- Accounting sees the money but not the commission logic behind it
- The spreadsheets see everything and trust nothing, because they are maintained by hand
The spreadsheet is not a tool in this stack. It is the integration layer. It is the only thing that touches all the others, and it is the most fragile thing you own.
The pattern under the pattern
This is not a discipline problem. Firms do not cobble seven tools together because they are disorganized. They do it because no single tool was built for the shape of a partner services firm: license commissions, direct delivery, and subcontracting in one business.
We ran this exact stack ourselves before we built PartnerView. Seven tools, one spreadsheet holding them together, one meeting a week to keep the spreadsheet honest. We wrote about what that costs in the operating tax. The first useful step is just seeing the stack for what it is: a workaround you have been paying for.