This essay is for owners whose card statement lists the software and whose calendar lists the person moving data between it. By the end you’ll be able to put that labor on the invoice and decide whether you are renting tools or renting someone to connect them.
Open the card statement and you will see HubSpot, Webflow, Zapier, Salesforce. Open the calendar and you will see the real product you bought: someone on your team acting as the integration layer. That person is the middleware. You are paying for them every week, whether or not they appear on a SaaS invoice.
A solar installer stack was not expensive because Salesforce is a bad product. It was expensive because form submissions arrived by email and an office manager retyped them. The Webflow, Zapier, and HubSpot stack is the same shape: growth meters every line, and a person still owns the seams.
01 · Name the job
Middleware is a role, not a feature
Middleware labor looks like:
- Copying website leads into the CRM
- Reconciling the newsletter list against contacts
- Checking that a Zap fired after a platform update
- Asking “which tool is source of truth?” in Slack
None of that shows up as a seat. All of it shows up as hours, retainers, and missed follow-ups.
The same hours show up beside the other sprawl figures on the statistics page. The point here is the role, not the citation.
02 · Why rented glue fails quietly
Task meters and human meters
Zapier-style automation feels like it removes middleware. Sometimes it does, for a season. Then:
- A field renames upstream and the Zap still “succeeds” with empty data
- Task volume climbs with the campaign that was supposed to pay for itself
- The only person who understood the graph leaves
You have replaced salaried middleware with metered middleware plus on-call archaeology. That can be the right trade for a prototype. It is a poor foundation for the operating system of the business.
03 · What ownership changes
Collapse the seams
An owned system does not mean “zero integrations.” It means the high-volume path is native:
- Site form writes to the CRM you own
- Email history sits on the same customer record
- Stages match how you sell and deliver, not a generic object model
The middleware role shrinks to exceptions, not the happy path. That is the difference between a gym that lives in Instagram DMs and a pipeline that captures every enquiry once.
The stack cost calculator is there to put the hours next to the subscriptions before you rebuild.
Conclusion
Put the labor on the invoice, then decide
If you only optimize subscription line items, you will cancel the wrong tools and keep the expensive humans. Put middleware hours next to SaaS on one page. When that sum is honest, own versus rent stops being a slogan and becomes arithmetic. Run the Index linked above, then audit the seams.