A consultancy signs a deal, then discovers delivery still needs to reconstruct the scope, kickoff date, and account owner from email. That is the useful HubSpot versus Salesforce test: can a won opportunity become an accountable delivery engagement without duplicate customer records?
Our recommendation is to test configuration first, a custom handoff second, and a replacement CRM last. Both platforms can represent more than a simple sales board. A custom system earns its place when the unusual part of your operation is stable and expensive enough to own.
Compare the workflow and the commercial boundary
The custom column describes a proposed implementation, not an existing product or a claim that a vendor cannot support it. Recommendations are Looski's analysis of official documentation reviewed September 26, 2026; this is not a hands-on benchmark.
| Decision | HubSpot | Salesforce | Build your own |
|---|---|---|---|
| Buying unit | Core, Sales, and View-Only seats have different rights. HubSpot seat types | Per-user sales editions. Salesforce Sales pricing | Pay for implementation and ongoing operation, not merely hosting. |
| Useful price anchor | Professional starts at US$90/seat/month annually, plus US$1,500 onboarding. HubSpot Sales Hub pricing | Pro Suite US$100/user/month annually. Salesforce Sales pricing | Quote the exact handoff and retained integrations. |
| Unusual business entities | Custom objects require an eligible Enterprise subscription. HubSpot custom objects | Lookup and master-detail relationships represent different ownership/deletion semantics. Salesforce object relationships | Model engagement, scope version, and acceptance separately. |
| Relationship context | Custom objects can have associations and pipelines. HubSpot custom objects | Relationships connect standard and custom objects. Salesforce object relationships | Use stable IDs across the CRM and delivery records. |
| Access model | Seat entitlement and record access require separate review. HubSpot seat types | Sharing rules expand access from organization defaults; they do not restrict it. Salesforce sharing rules | Enforce permissions on every query, export, and background job. |
| Automation design | Custom objects can participate in workflows. HubSpot custom objects | Pro Suite lists five flows per organization. Salesforce Sales pricing | One tested state transition can create a delivery draft. |
| Integration budgeting | Identify which staff need full Sales Hub capabilities. HubSpot seat types | Pro Suite lists web-services API access at an additional US$25/user/month. Salesforce Sales pricing | Maintain mailbox tokens, retries, and reconciliation. |
| Exit data | Record exports include current properties and associations. HubSpot record exports | Confirm API entitlement against the contracted edition. Salesforce API edition access | Produce records, relationships, files, and a documented schema. |
| Historical activity | Calls and notes need separate activity export paths. HubSpot record exports | Test extraction of the exact historical objects you use. | Keep an append-only change history and source references. |
| Best evaluation focus | Customer context crossing departments. | Complex commercial rules and administration. | A narrow exception that creates repeated manual work. |
Do not choose a cheaper tier and silently assume it contains the integration or object model from a sales demonstration. HubSpot's Enterprise custom-object requirement can matter more than its entry price. Salesforce's current commercial names also differ from older Enterprise/Unlimited comparisons; ask for a line-item proposal that matches the current catalog. HubSpot custom objects Salesforce Sales pricing
Model the handoff before buying more software
Separate the customer, sales opportunity, contracted scope, and delivery engagement. One customer may have several opportunities, and one won opportunity may produce phased engagements. A reopened deal should not erase the original acceptance, while a corrected customer name should not create a new account.
Write down who owns each field. Sales can propose a delivery date; delivery accepts it. Finance owns the billing identifier. The contract system owns the signed document. Without those boundaries, connecting more tools simply moves conflicting values faster.
In the pilot, require a delivery owner, scope reference, and start condition before activation. Preserve who approved the handoff and which scope version they accepted. Distinguish a missing field from a deliberate exception. An exception needs an owner and an expiration or review date, not a checkbox that permanently bypasses the rule.
Salesforce's distinction between lookup and master-detail relationships deserves particular attention: a relationship choice is also a lifecycle choice. Your administrator should explain what happens when a parent is deleted or access changes. The custom implementation needs equally explicit decisions; a database foreign key alone is not a business policy. Salesforce object relationships
Price the work you will actually remove
| Cost or failure mode | Evidence to collect | What the build estimate must include |
|---|---|---|
| Re-entering a won deal | Count handoffs needing manual copying and correction. | Mapping, duplicate detection, and retry-safe creation. |
| Delivery discovers incomplete scope | Sample the last ten kickoff delays. | Required evidence, versioning, and exception handling. |
| Integration fails silently | Reconcile source deals against created engagements. | Monitoring, repair queue, and an accountable operator. |
| Staff need occasional access | List viewers, editors, sellers, and administrators. | Authentication, authorization, and support for each role. |
| Historical migration | Export a shared contact, activity history, and reopened deal. | Data cleanup, attachment transfer, and reconciliation. |
| Change after launch | Request a new approval rule during the trial. | Maintenance capacity and a second maintainer's handover. |
Compare three-year totals using actual seats and realistic administration hours. Treat time savings as capacity first; ten saved minutes do not automatically become ten minutes of additional revenue. Count a subscription saving only when the contract can actually be retired. If marketing and service continue using HubSpot, a custom sales screen may add cost even while improving the workflow.
The sensible custom boundary
Build companies, people, opportunity references, delivery engagements, approval events, and a next-action queue. Keep the existing mailbox, calendar, signature service, and accounting system. Store external IDs and links rather than copying every possible piece of customer history into a new application.
For a hybrid, designate one authoritative system for each record. Consume changes through an integration with explicit retries and deduplication. A second “customer master” with no reconciliation plan is usually worse than the original spreadsheet. Restrict the custom layer to the missing delivery behavior until its value is established.
Choose a packaged CRM when your sales organization uses broad forecasting, administration, and ecosystem capabilities or lacks a permanent software owner. Choose a custom layer when a small set of repeatable exceptions dominates the work. Replace the CRM only when the reduced scope is intentional and the team accepts responsibility for operating it.
A pilot that can reject the idea
Use ten recent opportunities: won, lost, reopened, reassigned, and one with a contact shared between accounts. Trace every handoff to its source. Have a delivery colleague explain the current scope without asking sales. Then revoke a user's access, expire an integration credential, and replay a duplicate event.
Success means fewer manual transfers, no unexplained duplicate engagements, and complete evidence behind each activation. Export the pilot and reconstruct the relationships in a separate environment. Keep the old workflow available until reconciliation passes. A polished screen is not enough to justify moving the customer history.
Frequently asked questions
Do we have to replace our entire CRM?
No. A delivery handoff app can sit beside the CRM first. Keep the CRM authoritative for contacts and deals while testing whether the custom workflow removes enough duplicate work to justify expanding it.
What would a first custom CRM include?
Start with companies, people, opportunities, activities, and delivery engagements. Make a won opportunity create a draft engagement with its source deal attached. Require a delivery owner before activation, retain a history of stage changes, and give staff a next-action queue. Integrate the existing mailbox and calendar rather than implementing either service.
How should we compare the cost of HubSpot, Salesforce, and a custom build?
Count administrator time, onboarding, integrations, and the cost of correcting duplicate customer records alongside licenses. For a build, include mailbox maintenance and migration reconciliation. Compare the same scope and planning horizon, including implementation, retained services, maintenance, and support. A lower subscription bill alone does not establish a lower total cost.