Understand what is bought, what is configured, what has actually run, and what the business still needs. Those are four different kinds of evidence.
Do not approve the aggressive downgrade yet. Request a written, line-item renewal quote and clear the contact, custom-object, Data, workflow-cap and seat-transition gates. The $2,048 intermediate scenario avoids the unproven contact cut but is not technically cleared either.
Current monthly run-rate is $3,609.85, corroborated by billing screenshot and paid receipt. The annualized run-rate is $43,318.20. Annual term: 29 September 2025–28 September 2026; monthly billing; renewal and next payment 29 September 2026. This is not confirmation of next-term pricing.
The screenshot lists 61 Granted Core Seats at $0. They are not 61 active employees and are not automatically preserved after changes. Require duration, no-charge status, eligibility and included-seat treatment in writing.
Capability ≠ purchased entitlement ≠ configured artifact ≠ recent execution ≠ business value. OFF does not mean disposable; ON does not mean enrolled; published does not mean delivered; app activity is not ROI.
Dated snapshot: 10 September 2026, not a live dashboard or automatic refresh. Public, anyone-with-link educational view; no login. No HubSpot changes are authorized or performed by this guide. Filters and scenario buttons only change the view; there are no draft, notes or calculator-entry fields.
Start with the vocabulary, then follow a real campaign, inspect usage and test the renewal assumptions.
Objects → records → properties → associations. Learn what the business stores and how records relate before considering deletion or migration.
Separate Hub, tier, seat, permission, add-on, credit and grant. The product map below states purchased versus unverified packaging.
Campaign organizes; segment selects; workflow executes; marketing email delivers the asset. A real Sales Sequence is a different personal-inbox tool.
Inventory proves that configurations and records exist. Recent execution and successful business outcomes require additional evidence.
Identify outcome, accountable owner, enrollment trigger, actions, dependencies, incoming references and rollback before keeping, simplifying or retiring a workflow.
Map required features to users, permissions and purchased commitments. Do not size by job title or infer billability from deactivated labels.
Separate CRM storage, marketing status, consent and eligibility. Preserve important relationships and change status only through an approved audience plan.
Compare matched cohorts and bot-filtered engagement, then qualified conversations, booked meetings, supported clients or saved manual work—not raw opens alone.
The price presets are planning math, not order forms. Technical dependencies, transition costs and grant preservation control feasibility.
Use the owner matrix, remaining business questions and source notes to obtain a defensible quote and explicit approval.
A category of information, like contacts, companies, deals or tickets. A record is one item in that category. An object definition is not a count of people.
A contact represents a person; a company represents an organization. They can be associated without being the same record. CRM storage and marketing billing are different questions.
A deal tracks a commercial opportunity. A pipeline defines its stages. This account has four deal pipelines; the current Sales Pro allowance is 15, not two.
A record for a service request or operational case, typically managed through a ticket pipeline and service workspace.
A business-specific category beyond the standard CRM. Here: post 90-day check-ins, coaching sessions and virtual assistants. Removing the last Enterprise entitlement restricts operations on them.
A field on a record, such as lifecycle stage or marketing status. A field’s value can drive a segment or workflow. A missing value is not proof the relationship is unimportant.
A link between records, such as a contact at a company or a ticket connected to a deal. Associations preserve business context; a field alone is not that relationship.
An organizing and measurement container that groups related marketing assets. It does not itself send messages or automatically trigger a segment.
A saved audience or record selection. Active lists update using rules; static lists hold selected membership. Membership is not consent or guaranteed sendability, and lists overlap.
A rules engine: enrollment criteria → conditions, delays and actions. It can send marketing emails, edit records or hand data to another system. ON means enabled, not proof someone enrolled or a send succeeded.
A message asset sent through the marketing channel, including automated emails used by workflows. Published is not the same as delivered. A marketing nurture called a sequence is not necessarily Sales Sequences.
An individual-inbox sales follow-up combining email and tasks. It needs an eligible Sales/Service Pro or Enterprise seat and permissions. Workflow-based sequence enrollment has a separate Enterprise dependency.
A Hub is a product area; a tier is its feature level (Free, Starter, Professional or Enterprise where offered). Having a Hub does not grant every tier feature or prove it is used.
A user’s licensed tool access. Sales/Service seats include Core access; Core does not unlock all advanced Sales/Service tools. Purchased, assigned and granted are different counts.
Authorization to perform an action within available tools. Super Admin is a permission, not a paid Sales seat. Changing a seat does not automatically fix permissions.
A contact classified in the billable marketing category. Non-marketing contacts can remain in the CRM. Consent, opt-out, deliverability and billing classification are separate. Status changes and tier reductions have timing rules.
Add-ons extend capacity; credits meter eligible features; grants may preserve negotiated access. The 61 no-charge Granted Core Seats must be explicitly protected in writing.
An annual commitment can be paid monthly. The current term ends 28 September 2026; renewal and next payment are 29 September. The notice deadline is a separate contractual requirement.
Counts below describe accessible records and assets at the snapshot—not unique people across objects, not storage billing, and not proof of effective use.
26,718 active contacts = 24,027 marketing + 2,691 non-marketing. The proposal’s 22,483 marketing snapshot is 1,544 below the audit. Marketing status is a billable-category proxy, not the billing-period meter.
49 non-deactivated standard users; 104 deactivated standard users. 18 app-service identities are not employees. 12 active Sales assignments and five Service assignments overlap in four people, giving 13 distinct specialized-seat users. Other combinations: 33 Core-only, two Partner and one View-only.
44 of the 49 active users have an app action within 30 days; two are 31–90 days; three older than 90 days are Partner/View-only, not unused paid Sales/Service seats. Last Active is updated daily and is not last login or feature-level use.
13 permission sets; five non-deactivated super admins. Nine owner-embedded team IDs are partial evidence, not a complete team hierarchy. Four deal and nine ticket pipelines fit current Pro limits of 15 each.
1,768 files total 66,011,698,855 bytes (66.01 decimal GB) in metadata; this is not whole-account billable storage. Contacts have 588 property definitions, companies 265, deals 337 and tickets 561. Missing hubspotDefined flags are custom candidates, not a proven custom-property count.
Campaign-linked metrics cover 12 June–10 September 2026 and 433 asset associations, not every asset’s delivery history. Forms are inventoried, not all submission histories. Payments and commerce_payments are aliases; the table counts payments once. CRM invoices are not HubSpot software invoices.
| Object | Count | Coverage |
|---|---|---|
| Contacts | 26,718 | Search snapshot |
| Companies | 35,758 | Search snapshot |
| Deals | 1,125 | Search snapshot |
| Tickets | 1,332 | Search snapshot |
| Calls | 15,339 | Search snapshot |
| Emails | Unknown | Unavailable — HTTP 403 |
| Meetings | 7,504 | Search snapshot |
| Notes | 8,961 | Search snapshot |
| Tasks | 22,731 | Search snapshot |
| Products | 13 | Search snapshot |
| Line items | 13,332 | Search snapshot |
| Quotes | 0 | Search snapshot |
| Invoices | 5,022 | Search snapshot |
| Payments | 5,106 | Search snapshot |
| Subscriptions | 479 | Search snapshot |
| Leads | 1,644 | Search snapshot |
| Appointments | 423 | Search snapshot |
| Courses | Unknown | Unavailable — HTTP 403 |
| Listings | 0 | Search snapshot |
| Services | 0 | Search snapshot |
| Discounts | 512 | Search snapshot |
| Fees | 0 | Search snapshot |
| Taxes | 0 | Search snapshot |
| Carts | 0 | Search snapshot |
| Orders | 0 | Search snapshot |
| Post 90-day check-ins | 15 | Search snapshot |
| Coaching sessions | 38 | Search snapshot |
| Virtual assistants | 2 | Search snapshot |
| Communications | 2,054 | Search snapshot |
| Postal mail | 0 | Search snapshot |
| Feedback submissions | 678 | Search snapshot |
| Goals | 1 | Search snapshot |
| Payment links | Unknown | Unavailable — HTTP 400 |
| Marketing events | Unknown | Unavailable — HTTP 400 |
| Asset collection | Count | Coverage |
|---|---|---|
| Blog authors | 0 | Pagination exhausted |
| Blog posts | 1 | Pagination exhausted |
| Blog tags | 0 | Pagination exhausted |
| Campaigns | 18 | Pagination exhausted |
| Domains | 5 | Pagination exhausted |
| Files | 1,768 | Pagination exhausted |
| Forms | 172 | Pagination exhausted |
| HubDB tables | Unknown | Unavailable / incomplete |
| Landing pages | 0 | Pagination exhausted |
| Marketing emails (non-archived) | 842 | Pagination exhausted |
| Marketing emails (archived) | 2 | Pagination exhausted |
| Saved lists / segments | 437 | Pagination exhausted |
| URL redirects | 0 | Pagination exhausted |
| Website pages | 0 | Pagination exhausted |
All 523 API-visible flows are represented below using safe metadata. Curated teaching labels are shown for selected examples; other titles are deliberately replaced with IDs to avoid exposing customer or employee names.
523 unique flows across six exhausted pages: 522 WORKFLOW + one ACTION_SET; 197 ON / 326 OFF. Full graphs read for 522; enabled workflow 1856171049 failed with HTTP 500 / ListError.INTERNAL_LIST_CONVERSION. Its actions remain unknown. Fresh reconciliation found no ID, revision or state changes during collection.
2,561 action nodes: 792 marketing-email sends, 533 duration delays, 299 property edits, 264 branches and 110 enroll-other-workflow nodes. The last group resolves to 97 unique source/target links. No missing graph edges or unreachable nodes were found in readable graphs; this is not proof of business correctness.
90-day performance returned events for 92 mapped flows, including 32 currently OFF. Legacy matching covers 364 current flows, not all 523. Missing events do not mean never used. Counts may include re-enrollment and the same person across flows; never call their sum unique contacts.
26 zero-action flows are all OFF. Six conservative fingerprint groups contain 18 flows, but redacted content may differ. Two OFF flows reference placeholder email ID 0. Preserve ownership, history and incoming references before any cleanup.
The highest retained Hub allowance applies: Pro Marketing/Sales/Service 300, Data Pro 400, qualifying Enterprise 1,000 (Data Enterprise 1,100). Embedded automations are exempt. The 522 workflow-typed records minus 300 is a gross stress test of 222, NOT a confirmed excess or deletion requirement. Obtain the usage meter and written over-limit treatment.
Low: at most five actions and no branch; medium: other readable graphs up to 20 actions and at most three branches; high: more than 20 actions or more than three branches. Counts: 328 low, 185 medium, nine high and one unreadable. This is an audit heuristic, not a product limit.
Filters are temporary view controls. No customer titles, record details, code or integration destinations are included.
Loading safe inventory…
These arrows explain the architecture; they are not an execution trace. A campaign does not trigger its segment. Each path has a verified email-to-campaign UUID, workflow IN_LIST criterion and workflow send action pointing to the email ID.
Campaign: organizing container. Segment: current member population, not guaranteed sendable recipients. Workflow: enrolled records move through rules and timing. Marketing email: published message asset, not a delivery receipt.
All three original workflows are OFF and all three selected email assets are published. Each chain is a marketing nurture, not a real Sales Sequence. The examples demonstrate configured relationships, not successful sends or attribution.
Enabled continuation workflow 1861308219 sends emails 2–8 and its current enrollment mode is MANUAL. Do not invent an active segment trigger from paused original 1858142032 or assume a historical enrollment occurred. The first continuation email ID is 218123373594.
Marketing should confirm approved audience, consent and communication intent; Stephen should confirm trigger/action integrity and dependencies. Retained Marketing Pro/Enterprise supports the marketing toolchain, subject to actual action licensing and eligible recipients. Removing or pausing the workflow interrupts its automation, not the existence of campaign history.
087c8186-1bfd-4873-a8c8-88388181cf33Organizes the email asset4633230 members · audience only1858142032OFF · IN_LIST enrollment criterion218124282752Published · not delivery proof7dee4f41-8b12-43b8-8355-d752989ba2f2Organizes the email asset257226 members · audience only567742071OFF · IN_LIST enrollment criterion161727088205Published · not delivery proof6cbbed36-3439-43e0-9a45-37d48321bc54Organizes the email asset363352 members · audience only573550113OFF · IN_LIST enrollment criterion164140628607Published · not delivery proof53 deduplicated Sales Sequence definitions were read across 153 queried user/owner contexts, with no remaining paging cursors. User context is visibility scope, not a count of active users.
The 53 sequences contain 326 API steps: 122 EMAIL, 115 TASK and 89 FINISH_ENROLLMENT. Terminal steps can appear more than once; 89 is not the sequence count. Public examples show only IDs and step counts; no sender identities, customer details or email bodies.
Sales/Service Professional supports eligible sequence use with an assigned Sales/Service seat, connected individual work inbox and permissions. Current catalog comparisons show 5,000 sequences/account; Pro sends 500/user/day versus Enterprise 1,000. Confirm actual account limits and sender eligibility.
OFF workflow 1704753709 has a workflow-based sequence-enrollment action targeting sequence 289721966. That action requires Sales/Service Enterprise. Keeping ordinary Pro sequences does not prove this automation remains licensed.
Account-wide enrollment history, individual deliveries and feature-level adoption were not retrieved. Archived/deleted-user visibility is not independently guaranteed. A sequence definition is not an active send campaign.
| Sequence ID | API steps | Task | Terminal | |
|---|---|---|---|---|
| 281891163 | 4 | 1 | 1 | 2 |
| 299921506 | 10 | 5 | 4 | 1 |
| 289721966 | 9 | 0 | 8 | 1 |
| Sequence ID | API steps | Task | Terminal | |
|---|---|---|---|---|
| 281891163 | 4 | 1 | 1 | 2 |
| 289487141 | 6 | 2 | 3 | 1 |
| 295833446 | 2 | 1 | 0 | 1 |
| 310255485 | 2 | 1 | 0 | 1 |
| 297333289 | 4 | 1 | 1 | 2 |
| 299921506 | 10 | 5 | 4 | 1 |
| 280628016 | 4 | 1 | 1 | 2 |
| 306480473 | 10 | 5 | 4 | 1 |
| 284117890 | 4 | 1 | 1 | 2 |
| 297795447 | 4 | 1 | 1 | 2 |
| 307476587 | 8 | 3 | 3 | 2 |
| 297045830 | 4 | 1 | 1 | 2 |
| 296275048 | 2 | 1 | 0 | 1 |
| 303297057 | 6 | 3 | 1 | 2 |
| 281984906 | 8 | 3 | 3 | 2 |
| 307462233 | 10 | 5 | 4 | 1 |
| 309680211 | 6 | 3 | 2 | 1 |
| 306527661 | 4 | 1 | 1 | 2 |
| 289721966 | 9 | 0 | 8 | 1 |
| 307634319 | 4 | 1 | 1 | 2 |
| 283647787 | 8 | 3 | 3 | 2 |
| 300412064 | 7 | 3 | 2 | 2 |
| 300085261 | 5 | 2 | 1 | 2 |
| 286612141 | 8 | 3 | 3 | 2 |
| 305654024 | 5 | 2 | 1 | 2 |
| 309179312 | 4 | 1 | 1 | 2 |
| 293846192 | 9 | 3 | 5 | 1 |
| 305491069 | 4 | 1 | 1 | 2 |
| 279031876 | 6 | 3 | 1 | 2 |
| 283487744 | 8 | 3 | 3 | 2 |
| 287824825 | 9 | 3 | 4 | 2 |
| 305571001 | 5 | 2 | 1 | 2 |
| 292461943 | 7 | 3 | 3 | 1 |
| 297233706 | 6 | 2 | 2 | 2 |
| 309912737 | 10 | 5 | 4 | 1 |
| 307902309 | 4 | 1 | 1 | 2 |
| 279159722 | 4 | 1 | 1 | 2 |
| 283329956 | 8 | 3 | 3 | 2 |
| 305786911 | 6 | 3 | 2 | 1 |
| 290414602 | 4 | 1 | 1 | 2 |
| 310597951 | 10 | 5 | 4 | 1 |
| 284589423 | 7 | 3 | 3 | 1 |
| 306961490 | 4 | 1 | 1 | 2 |
| 305957714 | 4 | 1 | 1 | 2 |
| 310989206 | 4 | 1 | 1 | 2 |
| 308865643 | 4 | 1 | 1 | 2 |
| 307476604 | 8 | 3 | 3 | 2 |
| 280966260 | 10 | 4 | 5 | 1 |
| 307476605 | 8 | 3 | 3 | 2 |
| 309535307 | 10 | 5 | 4 | 1 |
| 287696017 | 7 | 3 | 2 | 2 |
| 288398352 | 8 | 3 | 3 | 2 |
| 305714343 | 4 | 1 | 1 | 2 |
The base capacity is 2,000. The observed marketing category is 24,027. This is a business-audience decision, not a record-deletion exercise.
Reaching 2,000 requires 22,027 fewer marketing contacts before new inflow. Only one contact is marked marketing until the next update in the snapshot. The scenario must also address status-change timing and contract tier-reduction rules.
A deduplicated hygiene-review union has 4,064 marketing contacts with missing email, global opt-out, positive bounce history, quarantine or a current hard-bounce reason. Even reclassifying all leaves 19,963. These are review signals, not permission to remove everyone.
2,004 marketing contacts have current-customer=yes, already above the 2,000 target; only 710 have lifecycle Customer. Reconcile the customer roster and communication requirements before using either field as a rule.
15,802 marketing contacts have neither recorded open nor click in 365 days; excluding all still leaves 8,225. Of these broader review signals, 3,100 were created over 365 days ago with no recorded open or click. Tracking absence is not proof of no relationship.
23,352 marketing contacts have Workflow as the current marketing-status source. This field does not identify the responsible workflow or its current state. Map the setting actions and prevent approved changes from being reversed by new enrollment.
4,830 marketing contacts show an open in 90 days, but only 256 show a click. Opens may reflect privacy proxies or bots. Compare the same eligible cohorts and periods across providers, filter bots consistently and measure downstream business outcomes.
Define protected clients and essential communications → reconcile consent and deliverability → agree the future marketing audience → audit status-setting automation → approve a staged reclassification and test plan → confirm billing effective date and written tier quote. No changes are authorized by this report.
Select a preset to see the same line-item assumptions in context. These buttons do not request a quote or change the subscription.
Tax, implementation, replacement software, migration, onboarding, usage credits and overages are excluded. Annual figures are monthly × 12, not a promise of annual billing or an annual vendor quote. All current discounts and no-charge grants must survive in writing.
This preserves the current $700 / 25,000-contact add-on while using the same proposed five Sales Pro seats, two Service Pro seats and no Data Pro. It avoids the immediate 2,000-contact target, but not custom-object, Data, seat, phone or workflow-cap risk. A differently sized contact tier would require a separate written quote.
Current catalog starts: Marketing Pro $890/month; Sales Pro $100/seat/month; Sales Enterprise $150/seat/month billed annually; Service Pro $100/seat/month; Data Pro $800/month. Additional Core: Pro $50, Enterprise $75/month. Pro Sales onboarding is listed at $1,500; whether a renewal downgrade incurs it is unresolved. These are not this account’s negotiated rates.
29 September 2026 is renewal, not 28 September. Public guidance says contact the Contract Manager at least five business days in advance. Ask Ted for the exact enforceable notice deadline and submission requirements; do not treat the day before renewal as safe.
| Line item | Current | Keep add-on | 2,000 target |
|---|---|---|---|
| Marketing Professional | $623.00 | $623.00 | $623.00 |
| 25,000 extra marketing contacts | $700.00 | $700.00 | $0.00 |
| Sales seats (14 Enterprise → 5 Pro) | $1,431.85 | $500.00 | $500.00 |
| Service Pro seats (5 → 2) | $350.00 | $200.00 | $200.00 |
| Data Professional | $480.00 | $0.00 | $0.00 |
| Five extra phone numbers | $25.00 | $25.00 | $25.00 |
| 61 Granted Core Seats | $0 verified | Preservation unquoted | Preservation unquoted |
Both lower-cost scenarios remain conditional. None of the items below authorizes a live change.
Ted: written line items, discounts, minimum seat commitments and all 61 $0 Granted Core Seats. Clarify grant duration, whether Marketing’s three and Data’s one included Core seats are additive, and what happens when Data is removed. Unassigning a seat does not itself reduce an invoice.
Stephen with process owners: post 90-day check-ins 15 records, coaching sessions 38, virtual assistants two. Removing the last Enterprise subscription blocks creation/editing, new associations and custom-object workflows; records remain viewable. Retain entitlement or prove a migration and operating replacement before downgrade.
Enabled workflow 1817319036 contains an external webhook handoff; its name is not proof of successful downstream receipt. Two OFF custom-code workflows need preservation/review. Inventory Connected Apps, custom sync mappings, Data Studio, scheduled/event triggers, formatting/enrichment and reporting dependencies. Unknown actions and one unreadable graph prevent a universal safety claim.
Stephen and HubSpot: identify chargeable versus embedded-exempt workflows, retained-Hub cap and limit add-ons. Get written handling of existing over-limit workflows. Turning OFF 326 already disabled flows is not a remedy for a creation-count cap.
Stephen and Alva should coordinate a private transition matrix against 12 Sales and five Service assignments, four dual holders, the proposed four incoming salespeople plus architect, and the proposed two Service users. This is a recommended responsibility, not an accepted assignment. Confirm advanced Help Desk, sequences, forecasting, calling and permissions before removing seats.
Sales Pro allows 100 custom reports versus Enterprise 500; Data Pro currently contributes 3,100 custom reports and 325 dashboards. Actual report/dashboard usage is unverified. Losing all Enterprise removes permission-set assignments but users retain permissions; export and review the 13 sets. Nine discovered teams do not prove total hierarchy fits Pro’s ten-team limit.
Sales Pro includes up to three numbers / 3,000 minutes versus Enterprise five / 12,000. Confirm retention and routing of all ten existing numbers and the five-number add-on. Pro sequences remain, but workflow-based sequence enrollment is Enterprise-dependent. Do not claim SSO is necessarily lost when Pro subscriptions remain.
Business owners: protect required communications and agree the marketing-contact tier/effective date. Ted supplies a written quote; Lillie validates adoption/product fit; Zack helps business-objective and sales fit. Obtain explicit final commercial and operational approval before any mutation.
Evidence: audit · billing · downgrade · catalog · actions · seats
A blocked or unsupported endpoint is not proof that a feature is absent or unused.
Missing settings.users.teams.read. Direct teams and full hierarchy not retrieved. Owner-embedded teams are partial discovery only; request authorized scope or a read-only administrative export.
Missing account-info.security.read. Login history, security events and audit logs were not analyzed. App Last Active is a different field. An authorized export or appropriate scope is needed for stronger utilization/security conclusions.
The error advertises one or more of crm.schemas.emails.read, crm.objects.emails.read and sales-email-read. This blocks CRM email-object search, not the separate marketing-email metadata inventory, which succeeded.
Provider message says the needed scope is not available for public use; no exact grantable scope name was provided. Do not invent one. Confirm through supported product UI or vendor assistance.
One enabled workflow graph returns HTTP 500, not a permission error. Payment-link and marketing-event CRM search routes returned validation errors; dedicated product inventories were not exhausted. Archived meetings, invoices, payments, subscriptions and communications cannot be paged by those routes.
Full granular permission matrices, installed integrations, data-sync mappings, report/dashboard usage, per-feature activity, account-wide sequence enrollment and all-email send histories remain unverified. Archived file/CMS flags returned active IDs; separate archive totals are unknown. No universal entitlement/object registry was established.
Current prices are corroborated, but next-term quote, grant preservation and exact notice deadline remain open. The supervising audit’s receipt/screenshot facts are used without publishing private artifacts. Full historic vendor correspondence was not exhausted; no claim is made that no older quote or attachment exists.
These roles separate a commercial answer from a technical or business acceptance. Internal coordination tasks below are recommendations, not claimed commitments.
Infrastructure point of contact and proposal author. Coordinate dependency map, billable workflow meter, permissions export, Connected Apps review and seat-transition matrix. Preserve rollback and proof of replacement before proposing cleanup.
Recommended coordinator with the business teams for required audiences, sales/service coverage, timing and responsibility handoffs. Her exact approval authority is not established in the retrieved evidence.
Confirmed vendor owner for renewal, paperwork, contract administration and billing. Obtain final pricing, grandfathered entitlement preservation, timing, minimum commitments and written downgrade terms.
Confirmed vendor contact for product adoption and customer-success support. Validate which capabilities the team needs and which risks require product assistance. Healthy usage is a vendor assertion, not verified ROI.
Confirmed Enterprise Account Executive contact for business objectives and sales fit. Help map commercial options to outcomes; do not substitute product positioning for contract confirmation.
The authorized business decision-maker approves the final quote, retained capabilities, transition costs and operating risk only after the above evidence is reconciled. No approval is inferred from viewing a preset.
These cannot be settled by counting assets or reading API labels.
Rank qualified sales conversations, client communication, service response, delivery operations and reporting. Which one system should own each outcome after renewal?
Which current clients, prospects, partners and contractual communications must be protected, and which belong in a different approved communication channel?
Which people need personal-inbox sequences, forecasting, advanced service tools or calling during and after the transition? What is the overlap period for incoming staff?
Who creates and updates check-ins, coaching sessions and virtual-assistant records, and what would stop if those operations became read-only?
How much migration effort, replacement software expense and temporary dual operation is justified by the net savings—not just the reduced HubSpot line item?
Who signs off on the protected audience, technical replacement proof, final quote and cutover timing? When can each dependency gate realistically be cleared?
First-party documentation was reviewed for the 10 September 2026 audit. Public catalog terms are not a substitute for your signed order form. Private source descriptions below deliberately omit private links and raw downloads.
Snapshot 10 September 2026. Complete accessible automation, data and roster pagination; exceptions explicitly listed. Private evidence retained separately.
Private source · summary onlyBilling screenshot confirms all current line items, 61 Granted Core Seats at $0, annual term 29 September 2025–28 September 2026 and monthly billing. Receipt corroborates $3,609.85 paid. Next payment and renewal: 29 September 2026. Screenshot facts supplied by the supervising audit; no payment details reproduced.
Private source · summary onlyStephen’s September renewal proposal supplies the $1,348 component assumptions. The proposal’s older 22,483-contact snapshot and Sales Pro two-pipeline claim are superseded by this audit.
Private source · summary onlyPublic packaging comparison, read 10 September 2026; not your negotiated order form.
Read first-party source ↗Consequences for custom objects, permissions, reports, workflows and data sync.
Read first-party source ↗Highest Hub limit, embedded exemptions and evidence-retention limits.
Read first-party source ↗Data Hub actions and Enterprise sequence-enrollment requirements.
Read first-party source ↗Individual inbox, eligible paid seat, permissions and sequence mechanics.
Read first-party source ↗Campaign organization and performance; Marketing Pro/Enterprise.
Read first-party source ↗Seats and permissions are separate; view-only limitations.
Read first-party source ↗Advanced Service features need the relevant Service seat.
Read first-party source ↗Public guidance says contact Contract Manager at least five business days before renewal; the actual contract controls.
Read first-party source ↗User properties and API access evidence.
Read first-party source ↗Login/security coverage limitations.
Read first-party source ↗Definition and user-context inventory; not account-wide enrollment history.
Read first-party source ↗