CRM Implementation Services: Scope Lines, Platform Differences, Edition Gates and Quote Comparison
CRM implementation services explained: the scope written before a platform is chosen, the Salesforce and HubSpot lines that differ, and how to compare quotes.
Paul Maxwell, PhD
AUTHOR
GET WEEKLY REVOPS INSIGHTS
No spam. Unsubscribe anytime.
Quotes for CRM implementation services on two platforms divide one requirement list into different lines and assume different editions. A Salesforce partner scopes profiles, Flow and Apex on an assumed edition; a HubSpot partner scopes seats, workflows and custom code on an assumed tier per hub. Compared by their totals, the two quotes describe different scopes. Where one has met a requirement by assuming an edition the licence budget never priced, the difference returns as an upgrade at renewal. A second error comes earlier: the requirements and specifications that should choose the platform are written inside one partner's discovery, after the choice is made.
This article sets out a scope list for CRM implementation services that can be held against competing quotes. It starts with the documents written before the platform is chosen, then the lines that exist only on Salesforce or only on HubSpot, and weighs the costs and returns of buying the specification before either. A sample requirement list then shows where each Professional tier stops, followed by a comparison procedure, the symptoms of a scope gap and the limits of the evidence.
CRM implementation services configure a CRM platform against written requirements, including the migration and integrations that configuration depends on, whoever performs the work. A requirement states what one role can do with one kind of record, with a test that accepts it. A platform-neutral line produces a deliverable that can be written before the platform is chosen; a platform-specific line exists because of one platform's design. An edition on Salesforce and a tier on HubSpot are the subscription levels that decide whether a feature exists in an account at all.
Platform-Neutral Scope: Requirements and Specifications
The platform decision changes five kinds of scope line and adds a platform column to the documents beneath them. Access design, automation and custom code, the release path from test to production, data loading and API capacity, and the licence model are built differently on Salesforce and on HubSpot. On both, the edition decides whether some of those lines can be built at all. Requirements, process definitions, the migration specification, the integration specification, report definitions and the training plan are written before selection, and each gains its platform column afterwards, such as the target field names and types in a migration field map. Quotes for different platforms are therefore comparable line by line only on those six documents; every other line can be compared only through the requirement it serves.
A migration needs an owner map, every legacy owner value matched to a user, before any record loads. HubSpot matches owners by name, email address or owner ID under its import file requirements. Salesforce gives rows mapped to a name two users share to whoever runs the import, and recommends the User ID instead. The map is written once; only its key column changes.
Salesforce's integration patterns frame each integration by which system holds the master record and which stores the other's key, and HubSpot's data sync settings ask for a sync direction and the app that wins a conflict. A stage definition is equally portable, configured as pipeline stages with required properties on HubSpot and as the stage values of a sales process on Salesforce.
| Line | Deliverable | Acceptance evidence |
|---|---|---|
| LineRequirements | DeliverableOne statement per role and record type, with a test | Acceptance evidenceEach test passes for a user holding only that role's access |
| LineProcess definitions | DeliverableStages, with entry and exit criteria and required fields | Acceptance evidenceA record cannot enter a stage with a required field empty |
| LineMigration specification | DeliverableSources, record counts, field map, deduplication rule, owner map | Acceptance evidenceRecord and association counts reconcile per object |
| LineIntegration specification | DeliverableMaster system, direction and conflict rule per field; where keys are stored | Acceptance evidenceChanges arrive from each master; conflicts resolve as written |
| LineReport definitions | DeliverableQuestion, calculation, filters and owner per report | Acceptance evidenceEach report matches a figure computed by hand |
| LineTraining plan | DeliverableRoles, cohorts and the procedures each role performs | Acceptance evidenceEach role completes its procedures unaided |
Salesforce Scope Lines: Profiles, Permission Sets, Flow and Apex
A Salesforce user holds one user licence and one profile, and every profile belongs to exactly one licence type. Permission sets add permissions without changing the profile, and Salesforce calls them the recommended way to manage permissions. Salesforce has cancelled the retirement of permissions in profiles that it announced for Spring '26, so a quote that prices a mandatory move to permission sets is pricing a recommendation rather than a deadline.
Record access is a second design. Org-wide defaults set the baseline for records a user does not own, and the role hierarchy and sharing rules can open that access but never narrow it. Each object takes up to 300 sharing rules, of which up to 50 can be criteria-based or guest-user rules. The HubSpot vs Salesforce comparison tests one access policy against both models.
Automation is built in Flow. Salesforce ended support for Workflow Rules and Process Builder on 31 December 2025: active rules keep running without support or bug fixes, and Salesforce provides a Migrate to Flow tool. An implementation that extends an existing org therefore inherits that migration whether or not a quote names it. The edition sets a ceiling, because Professional Edition allows five active flows per flow type against 2,000 on Enterprise.
Logic that Flow cannot express is written in Apex, which is available in Enterprise, Performance, Unlimited and Developer editions and not in Professional, and which deploys only when unit tests cover at least 75% of the code. The threshold applies to the whole org: in Salesforce's own example, a 100-line class at 95% coverage deployed into a 10,000-line org at 70% gives (7,000 + 95) ÷ (10,000 + 100) = 70.25%, and the deployment fails. An inherited org with thin tests therefore carries a test-writing line before anything new can ship.
The release path starts at a lower edition than HubSpot's. Professional Edition includes ten Developer sandboxes, which copy metadata only, and Enterprise includes twenty-five and one Partial Copy sandbox. Change sets run from Professional Edition upward and carry created or modified components of the supported types, while changes to other types are repeated by hand in the target org. Custom objects exist in both editions, 50 on Professional and 200 on Enterprise.
Data loading and API capacity follow the edition too. The Data Import Wizard imports accounts, contacts, leads and custom objects but not opportunities, and Data Loader, which handles between 5,000 and 5 million records, is not listed for Professional Edition. Daily API calls on Enterprise are 100,000 plus 1,000 per Salesforce licence, and Professional Edition appears in that table only with API access enabled. The lower-cost platform licence excludes opportunities and cases, so a user who only reads deals still holds a full licence.
HubSpot Scope Lines: Tiers, Seats, Permissions, Workflows and Sandboxes
HubSpot sells each hub at a tier, and each user's seat decides which features of those tiers the user reaches. View-Only Seats are free and unlimited on Starter, Professional and Enterprise, Sales and Service Seats carry their hub's Professional or Enterprise features, and a purchased seat count cannot be reduced before renewal. The product and services catalog prices every Core Seat at the highest tier the account holds, so a requirement that needs Enterprise on one hub can re-price every Core Seat.
The user permissions guide sets record access per object and action as all records, the team's or the user's own, with an option for unassigned records. Teams require Professional and nested teams Enterprise. Saved permission sets are an Enterprise feature capped at 100 per account, and the catalog limits Starter and Professional to permission templates.
Workflows are documented for Professional and Enterprise subscriptions; the catalog allows Sales Hub Professional up to 300 fully customizable workflows and Enterprise 1,000, and gives Starter 50 with restricted triggers and actions. Code inside a workflow requires Data Hub Professional or Enterprise, and each custom code action must finish within 20 seconds and 128 MB of memory, so heavier logic runs on a service the workflow calls. Custom objects require an Enterprise subscription.
The release path exists only on Enterprise. A sandbox deploy moves up to 300 changes and only a Super Admin runs it, and only new assets deploy: edits to assets copied from production cannot, and deployed workflows arrive switched off. The HubSpot implementation services guide counts how much of a build that leaves to be done in production by hand.
Paid accounts import up to 1,048,576 rows per file and 10,000,000 rows a day under the same import requirements. Daily API calls for privately distributed apps are fixed per account by tier, at 250,000 on Starter, 625,000 on Professional and 1,000,000 on Enterprise, whatever the number of seats. Custom field mappings in data sync require Data Hub at any paid tier.
Platform Scope Lines: Reference Table
| Scope area | Salesforce | HubSpot |
|---|---|---|
| Scope areaFunctional access | SalesforceOne profile and licence per user, plus permission sets | HubSpotScopes per object; permission sets on Enterprise |
| Scope areaRecord access | SalesforceOrg-wide defaults, role hierarchy, sharing rules | HubSpotOwn, team or all records; teams from Professional |
| Scope areaAutomation | SalesforceFlow: 5 active per type on Professional, 2,000 on Enterprise | HubSpotWorkflows: 300 on Sales Hub Professional |
| Scope areaCustom code | SalesforceApex on Enterprise, at 75% org-wide coverage | HubSpotData Hub Professional, 20 seconds per action |
| Scope areaCustom objects | Salesforce50 on Professional, 200 on Enterprise | HubSpotEnterprise only |
| Scope areaRelease path | SalesforceDeveloper sandboxes from Professional; change sets carry edits | HubSpotSandbox on Enterprise; new assets only |
| Scope areaData loading | SalesforceImport Wizard without opportunities; Data Loader from Enterprise | HubSpot1,048,576 rows per file |
| Scope areaAPI capacity | Salesforce100,000 plus 1,000 per licence a day on Enterprise | HubSpot625,000 a day on Professional |
| Scope areaLicences | SalesforceOne edition per org; a full licence to read deals | HubSpotTier per hub; free View-Only Seats; Core Seats at the highest tier |
Costs and Returns of Buying the Specification First
Buying the neutral documents before the platform buys comparability, because every bidder then prices one requirement list rather than its own reading of a sales meeting. It also moves the platform decision onto edition gates, like those in the sample below, rather than onto a demonstration, and its deliverables survive a change of implementer.
It costs a separate engagement and the calendar time before selection, and it is paid for twice when a platform partner declines the documents as an input and repeats discovery in its own vocabulary. The documents also stop short of the platform lines, so permission sets, Apex tests and a seat plan are still priced by someone who builds on the chosen platform.
The case is strongest where the platform is still open, where several source systems and integrations make the specifications large, and where requirements sit near a gate, as R2, R5 and R9 do in the sample below. It is weakest where a group standard or existing licences have already fixed the platform, or where the scope is small enough that a partner's discovery costs little more than a separate specification.
A partner of one platform runs discovery in that platform's constructs, and its revenue depends on that platform being chosen. The firm publishing this article is a HubSpot Solutions Partner and holds that interest in every comparison it makes.
Edition Gates on a Sample Requirement List
The requirement list below is sample data, constructed for the arithmetic and drawn from no client. It describes 40 users, 32 sellers, 6 finance users who read deals and 2 administrators, and classifies each requirement against Salesforce Professional Edition and HubSpot Sales Hub Professional.
| Requirement | Salesforce Professional Edition | HubSpot Sales Hub Professional |
|---|---|---|
| RequirementR1. Load 18,000 contacts, 4,000 companies and 9,500 deals, owners kept | Salesforce Professional EditionMet: deals load through dataloader.io or API access | HubSpot Sales Hub ProfessionalMet: one file per object, owners matched by email |
| RequirementR2. Two pipelines, new business and renewals, with required fields per stage | Salesforce Professional EditionEnterprise: multiple sales processes | HubSpot Sales Hub ProfessionalMet: required stage properties |
| RequirementR3. Reps see their own deals, managers their team's, leadership all | Salesforce Professional EditionMet: private default, role hierarchy | HubSpot Sales Hub ProfessionalMet: scopes and teams |
| RequirementR4. Six finance users read every deal and edit none | Salesforce Professional EditionMet, on six full licences | HubSpot Sales Hub ProfessionalMet, on six free View-Only Seats |
| RequirementR5. A project record linked to companies and deals | Salesforce Professional EditionMet: a custom object | HubSpot Sales Hub ProfessionalEnterprise: custom objects |
| RequirementR6. Twelve automations on new and changed deals and companies | Salesforce Professional EditionEnterprise, or four consolidated flows | HubSpot Sales Hub ProfessionalMet: within 300 workflows |
| RequirementR7. A discount calculation the automation tools cannot express | Salesforce Professional EditionEnterprise: Apex | HubSpot Sales Hub ProfessionalData Hub Professional: custom code |
| RequirementR8. Two-way sync with accounting, which owns billing fields | Salesforce Professional EditionEnterprise, or an API add-on | HubSpot Sales Hub ProfessionalMet through the API; Data Hub for custom sync mappings |
| RequirementR9. Changes tested before release, including edits to existing configuration | Salesforce Professional EditionMet: Developer sandboxes and change sets | HubSpot Sales Hub ProfessionalEnterprise sandbox; edits rebuilt in production |
| RequirementR10. Training for three roles and an administrator handover | Salesforce Professional EditionMet | HubSpot Sales Hub ProfessionalMet |
Salesforce Professional Edition meets six of the ten requirements and HubSpot Sales Hub Professional meets seven. The misses differ, R2, R6, R7 and R8 on Salesforce against R5, R7 and R9 on HubSpot, so R7 is the only requirement that neither Professional tier meets. At the higher tier the difference shrinks to one requirement: Salesforce Enterprise Edition meets all ten, and HubSpot Enterprise with Data Hub Professional meets nine and R9 in part. HubSpot's sandbox deploys new configuration only, and R9's edits are rebuilt by hand.
A Salesforce quote that delivers R2 and R7 has assumed Enterprise Edition for all 40 licences, since neither has a Professional workaround. One that delivers R6 and R8 on Professional has added workarounds, consolidated flows and an API add-on, that no HubSpot quote contains. A HubSpot quote that delivers R5 and R9 has assumed an Enterprise subscription, which the catalog's pricing rule carries into every Core Seat, and one that delivers R7 has assumed Data Hub.
R6's workaround depends on its two objects. A record-triggered flow starts from the new and changed records of a specified object, so the twelve automations consolidate into four flows at most: a before-save and an after-save flow per object. Twelve spread over six objects would not fit in five. The Professional Edition allocations list five flows and processes in total and five active, with no per-type qualifier, and under that reading the four leave one flow for the rest of the org.
The licence lines differ even where no gate applies: R4's six finance readers need six paid Salesforce licences and no paid HubSpot seat. API capacity is counted differently: Enterprise Edition allows 100,000 + 40 × 1,000 = 140,000 calls a day for these 40 licences and grows with each licence added, while Sales Hub Professional allows 625,000 a day at any seat count.
Cross-Platform Quote Comparison: Procedure and Acceptance Check
- Write each requirement in one form, "[role] can [action] on [record] when [condition]", with an acceptance test the buyer can run without the provider.
- Write the six neutral documents in the first table, or buy them as a separate deliverable, before any platform partner's discovery begins.
- For each candidate platform, mark every requirement with the edition or tier that meets it, from the Required Editions block that opens each Salesforce help article and the Available with list that opens each HubSpot knowledge base article.
- Send every bidder the same requirement list and documents, and require one line per requirement, the edition or tier each line assumes, and every workaround as its own line.
- Compare the neutral lines across all quotes and the platform lines only between quotes for the same platform.
- Add each quote's licence consequence to its services total: the edition for every Salesforce licence, the tier and seat mix on HubSpot, and add-ons such as Data Hub or Salesforce API access. The HubSpot implementation cost guide prices the HubSpot side from the catalog.
- For an existing system, add the inherited lines: on Salesforce, the active rules under Setup, Process Automation, Workflow Rules and Process Builder, and the org-wide coverage estimate on the Apex Classes page; on HubSpot, the edits a sandbox cannot deploy and the seats already bought.
- Verify at acceptance by signing in as a test user holding exactly one role's access and running that role's tests; a test that passes only for an administrator has not passed. Then confirm the subscription matches the quote. Salesforce's Setup, Company Information shows the Organization Edition and licences purchased. In HubSpot, the account name in the top right corner, then Account & Billing, lists every hub subscription and add-on, Data Hub included, under My Products & Add-ons. Settings, Users & Teams, Seats then shows the seat assigned to each user.
Quote and Scope Gaps: Symptoms and Causes
A Salesforce deployment fails on code coverage although every new class is fully tested. The org-wide figure with existing code is below 75%, which blocks any deployment containing Apex, and the remedy is a test-writing line scoped before the build rather than found at release.
Imported Salesforce records belong to the user who ran the load. The owner column held full names, two users shared one, and the wizard assigned those rows to the importing user. The repair is an owner map keyed on User IDs for Salesforce and on owner email or ID for HubSpot.
A HubSpot invoice rises for every Core Seat after one requirement was met. That requirement needed Enterprise, and Core Seats are priced at the highest tier held. Purchased seats cannot be reduced until renewal, so the tier belonged beside the requirement in the quote.
A Salesforce Professional org cannot activate another record-triggered flow after go-live. The build gave each automation its own flow until five were active, and consolidating them by object is work the quote should have carried as its own line.
Boundaries of This Scope List
This list covers Salesforce Sales Cloud and HubSpot's Smart CRM and Sales Hub. Dynamics 365, Zoho, Pipedrive and Salesforce's industry clouds are not mapped. The sample sets equally named tiers side by side rather than equally priced ones: Professional is the lowest of the three editions Salesforce's editions page lists as currently sold, and the middle of HubSpot's three. Every platform claim is as documented in October 2026, none was tested in a live Salesforce org or HubSpot account, and both vendors' documentation is authoritative over this text.
Documentation states which features exist at which edition, not how long a line takes, and neither vendor publishes effort data, so the sample counts requirements and gates rather than hours. HubSpot's knowledge base says the number of workflows depends on the subscription without stating it, and the figures above come from its product catalog. The Data Import Wizard's exclusion of opportunities is inferred from the objects Salesforce lists for it. Classifying a line as neutral is an argument from the deliverable it produces rather than a measured share of any project, and the sample's six and seven of ten describe a constructed list.
In Summary
CRM implementation services divide into documents written before the platform is chosen and lines that exist because of one. The six documents, from requirements to the training plan, can be bought first and gain a platform column after selection; the five kinds of platform line are built differently on Salesforce and HubSpot. Both platforms gate those lines by subscription: Salesforce by one edition for the whole org, HubSpot by a tier per hub, the highest of which prices every Core Seat.
In the sample each Professional tier misses a different set of requirements, so a Salesforce quote and a HubSpot quote are comparable only through the requirement list, with every line naming the edition it assumes. Priced that way, the licence consequence of a requirement is known before signature rather than found on the renewal invoice.