Rev Platform Integrations
The systems in this category are built and operated by this practice rather than integrated from outside it. They are listed separately because presenting them beside third-party platforms without that distinction would read as a claim about reach rather than about a suite.
Each one exists because a repeated client requirement had no adequate answer in the market at a price the requirement justified.
8 systems in this category.
Why a first-party product rather than a configuration
Configuration is the default and is correct nearly always. A product is warranted only where the same requirement appears across unrelated clients, the platform cannot express it, and the alternative is rebuilding the same custom work repeatedly at each one.
The test applied is whether the thing being built would still be needed if the next client had a different stack. Where the answer is no, it is configuration and belongs in the portal rather than in a product.
Which engagement shape fits which situation
What is measured, at which layer, and what each measure is for
Systems in this category
The managed integration layer this practice builds on, where rate limits, retries and schema drift are an operator's obligation rather than the client's.
Configure, price and quote against the HubSpot object model, so a quote is a record rather than a PDF nobody can report on.
Scheduling, dispatch and routing joined to the deal that funds the visit.
Team scheduling resolved against HubSpot contacts and meetings rather than a parallel calendar.
Territory and geography as a layer over the CRM, so location is a dimension rather than a text field.
The go-to-market record: people, coverage and the tech estate, held where the revenue data already is.
Automated portal health checks on data quality and configuration, run on a schedule rather than before a renewal.
Closed deals provisioned into delivery work, from the scope that was sold rather than a re-keyed summary.
Common Questions
Frequently Asked Questions
No. Every engagement described on this site is deliverable without any of them, and most are. They exist where a requirement recurred often enough to justify building against it once rather than repeatedly.
Configuration and documentation belong to the client in every case. Where a first-party product is in use, the terms of continued access are set out in the agreement covering it rather than assumed.
Further reading
Long-form already published on the argument this category turns on.
Related categories
A system in this category that is not listed
The directory shows range rather than limits. A scoped build is quoted from the object model on each side and the fields that have to cross between them.