Prepared for Peterson

A shared relationship platform for sales and leasing.

HubSpot implementation, team enablement, and launch support for Peterson’s residential sales and leasing teams.

Prepared by: Dave Betcher | Betcher Consulting Group

Date: November 3, 2026 | Draft for review

Investment: $8,000 CAD plus applicable taxes

01Executive overview

One relationship platform, two distinct customer journeys.

This engagement establishes HubSpot as a shared relationship platform for Peterson, with separate sales and leasing processes, clear project ownership, consistent follow-up, and practical management reporting.

The implementation follows a phased approach: agree the process, configure the CRM, prepare and migrate the approved data, build and test customer journeys, then train the team and launch. The initial rollout will focus on the projects, users, and workflows agreed before kickoff, with a structure that can support future growth.

One shared CRM

Separate sales and leasing processes built on one contact database.

Consistent follow-up

Clear project ownership and reliable appointment follow-up.

Initial AI pilots

One website customer-agent pilot and one AI-assisted nurture pilot.

Reporting and adoption

Core dashboards, role-based training, and the Peterson Success Center.

Milestone-based delivery

Four phases, each completed against an agreed threshold.

Intended outcomes

  • Faster and more consistent inquiry handling.
  • Better visibility into prospect activity.
  • Reliable appointment follow-up.
  • Clearer reporting from initial inquiry through purchase or lease.

Investment summary

Total implementation
$8,000 CAD plus applicable taxes
Payment
Four milestone installments of $2,000 CAD
HubSpot software is purchased separately.
Integration discovery is included; development is scoped separately.
See the full investment details

02Discovery and implementation scope

Agree the process before configuring the system.

Working sessions will confirm the initial projects and rental properties, participating teams, current systems, source data, customer journeys, and reporting priorities.

Discovery will address

  • Prospect funnel structure
  • Lists and qualification
  • Appointment booking
  • Daily traffic reporting
  • Website assistance
  • Handoff of purchaser information to contract management

How scope is set

  1. 1. Before kickoff

    Peterson and Betcher Consulting Group agree the launch project list, source datasets, and allowances for forms, templates, workflows, dashboards, and training sessions.

  2. 2. During discovery

    Discovery validates these assumptions and produces an approved implementation blueprint.

  3. 3. If more work is identified

    Any expansion is documented and approved before additional work begins.

03CRM architecture and account setup

One contact database, separate opportunities, clear ownership.

One contact database will support separate purchasing and leasing opportunities, with project-specific information and accountable owners.

ComponentProposed approach
ContactsOne record per person, with relationship history and communication preferences.
OpportunitiesSeparate deal records for each purchasing or leasing journey.
PipelinesOne residential sales pipeline and one leasing pipeline.
Projects and propertiesA consistent project structure linked to contacts and opportunities. A custom object will be used only if supported by the selected subscription and agreed requirements.
OwnershipIndividual opportunity owners, project teams, and backup coverage rules.
Daily workspaceSaved views, tasks, qualification fields, next steps, and appointment outcomes.

Configuration includes

  • Account settings and agreed user permissions
  • Naming conventions
  • Lead sources and lifecycle definitions
  • Subscription preferences
  • Duplicate management rules

04Data preparation and migration

Clean, mapped, and reconciled data.

The agreed source datasets will be reviewed, mapped, cleaned, and imported into HubSpot.

Preparation includes

  • Project associations and ownership
  • Statuses and available history
  • Legacy identifiers
  • Unsubscribes and suppression information

Validation

  • A sample import is reviewed before the full migration.
  • Record counts and key fields are reconciled.
  • Exceptions and export limitations are documented.

Historical reconstruction beyond the agreed exports is separately scoped.

Marketing-contact status will be managed separately from communication permission. Segmentation and audience controls will help Peterson maintain a relevant marketing audience within its selected subscription tier.

05Sales and leasing journeys

Two journeys, given equal care.

Sales and leasing will share customer history while maintaining distinct stages, ownership, follow-up, and reporting. Proposed stages will be confirmed during discovery.

Residential sales
  1. New inquiry

  2. Engaged and needs identified

  3. Appointment scheduled

  4. Appointment completed

  5. Actively considering

  6. Reservation or offer in progress

  7. Under contract

  8. Closed or homeowner

  9. Closed lost

Leasing
  1. New rental inquiry

  2. Requirements confirmed

  3. Tour scheduled

  4. Tour completed

  5. Application invited or submitted

  6. Application review or approval milestone

  7. Lease signed

  8. Moved in or resident

  9. Closed lost or withdrawn

Configuration will cover

  • Online and walk-in registrations
  • Project routing
  • Owner notifications
  • Qualification fields
  • Calendar connections and scheduling links
  • Appointment outcomes
  • Dated next steps

Boundaries

  • Long-term nurture will be tracked separately from active opportunities.
  • Application screening, contract execution, accounting, and resident operations remain in the appropriate operational systems.

06Website capture and follow-up automation

Every inquiry arrives with its context.

The agreed website forms and tracking will capture project interest, inquiry source, and relevant customer preferences. Existing websites can remain in place, with website-team coordination where needed.

Initial templates and workflows

  • Inquiry acknowledgment
  • Assignment and follow-up tasks
  • Appointment confirmations and reminders
  • Post-visit follow-up
  • Missed appointments
  • Longer-term nurture

Enrollment and exit rules

Each workflow will have defined enrollment, suppression, and exit rules. Follow-up will pause or change when a prospect replies, books, progresses, opts out, or is taken over by a team member, as appropriate to the workflow.

SMS

SMS can be assessed during discovery. Activation depends on an approved provider, appropriate consent, and separate subscription and usage costs.

07AI engagement and team support

Two controlled AI pilots, with people in control.

The implementation includes one initial website customer-agent pilot and one initial AI-assisted nurture pilot for an agreed audience.

Website customer-agent pilot

Uses approved Peterson content to answer common questions, guide visitors toward an inquiry or appointment, and escalate questions requiring a person. It will not invent pricing, availability, incentives, or contract terms.

AI-assisted nurture pilot

Uses available prospect interests and appointment context to make follow-up more relevant, with approved messaging, human review during testing, and clear exit rules.

Pilot acceptance
  • Agreed scenario testing.
  • Appropriate escalation.
  • Suppression checks.
  • A named Peterson owner.
  • Usage-monitoring guidance.

Activation depends on HubSpot licensing, account eligibility, and approved content. If a capability is unavailable, a replacement deliverable will be agreed before proceeding. AI credits and software usage are separate.

08Integration discovery and handoffs

Reduce duplicate entry with clear handoffs.

Integration discovery and planning are included. Custom integration development is not included in the $8,000 fee.

For Peterson’s confirmed contract management and property management systems, discovery will identify:

  • Required fields
  • Handoff milestones
  • Supported interfaces
  • Matching identifiers
  • Data direction
  • The authoritative source for each milestone

The goal is to reduce duplicate entry and reflect relevant purchaser, application, contract, or lease milestones in HubSpot where supported. No specific connector or two-way synchronization is assumed.

Deliverable

A feasibility assessment, field mapping, and agreed handoff plan. Any recommended development will receive a separate scope and price. A documented interim handoff may support the core launch if Peterson approves it.

09Reporting and engagement priorities

Clear numbers from inquiry to purchase or lease.

Core HubSpot reporting will provide visibility into inquiries, active opportunities, scheduled and completed appointments, confirmed sales or leases, sources, project performance, and follow-up coverage.

Daily traffic reporting will use agreed definitions for new inquiries, unique prospects, walk-ins, appointments, and repeat visits. Reporting will distinguish automated acknowledgments from meaningful team responses and scheduled appointments from completed visits.

Saved views will highlight

  • Unassigned inquiries
  • Overdue follow-up
  • Stalled opportunities
  • Prospects showing renewed engagement

Digital activity will help prioritize review without being treated as proof of purchase readiness.

Advanced historical reporting, BigQuery, Looker Studio, custom Excel generation, and multi-system reporting are optional services scoped separately.

10Training and adoption

Peterson Success Center

Launch training and ongoing reference, in one place.

The initial Peterson Success Center is included as a branded resource for launch training and ongoing reference. It will contain the agreed process guides, recordings, communication examples, daily checklists, and answers to common questions.

Content

  • Getting started
  • Managing contacts
  • Sales and leasing journeys
  • Tasks and follow-up
  • Marketing preferences
  • AI pilot guidance
  • Dashboards

Role-based training

Live role-based training will use Peterson’s launch configuration. Designated users will receive a walkthrough of the Success Center and the daily processes relevant to their roles.

Hosting and access

Hosting and access arrangements will be confirmed during discovery; third-party charges are separate.

Outside the initial scope

  • Custom authentication
  • Learning progress tracking
  • Quizzes
  • Certifications
  • Live CRM connections

11Delivery phases and launch

Four phases, each with a clear completion threshold.

The delivery schedule will be agreed at kickoff around Peterson’s launch priorities, data readiness, and team availability.

  1. Discovery and kickoff

    Launch scope, responsibilities, access requirements, and implementation plan agreed.

  2. CRM foundation and data

    Core CRM structure and pipelines demonstrated; sample migration, mappings, and exception rules approved.

  3. Workflow and reporting readiness

    Agreed forms, routing, scheduling, templates, workflows, and dashboards pass documented scenario tests; AI pilots reviewed.

  4. Training and launch

    Approved migration reconciled, training delivered, Success Center available, launch checklist accepted, and core rollout completed.

Testing will include contact matching, routing, opportunity associations, permissions, reminders, workflow exits, reporting reconciliation, and approved handoffs. Launch stabilization and its duration will be agreed in the kickoff plan. Separately commissioned integrations will have their own delivery schedule.

12Investment

Investment and payment thresholds

Total implementation fee

$8,000 CAD

Plus applicable taxes.

The fee includes discovery, the agreed CRM configuration and migration, lead capture, initial follow-up automation, the two defined AI pilots, core reporting, integration discovery, role-based training, the initial Peterson Success Center, testing, and launch support.

Payment schedule

PaymentThreshold for invoicingAmount
1 of 4Proposal acceptance and project kickoff, with the initial scope and responsibilities agreed.$2,000 CAD
2 of 4Peterson approval of the core CRM structure, pipelines, data mappings, and sample migration.$2,000 CAD
3 of 4Peterson approval of workflow and reporting readiness following documented testing of the agreed forms, routing, scheduling, follow-up, and dashboards, plus review of the AI pilots.$2,000 CAD
4 of 4Completion of the approved core launch, reconciled migration, role-based training, and delivery of the initial Peterson Success Center.$2,000 CAD
TotalFour equal installments of 25%$8,000 CAD

Milestones are based on completion of the agreed deliverables, rather than elapsed calendar time. Written milestone approval will confirm that the applicable threshold has been reached. Invoice payment terms will be confirmed in the final agreement.

HubSpot software and third-party costs

HubSpot software is purchased separately under Peterson’s own HubSpot quote. Third-party subscriptions, SMS usage, AI credits, vendor interface fees, middleware, and hosting are additional and will be identified for approval before commitment.

Ongoing consulting

Ongoing consulting after the agreed launch support period is optional, with scope, capacity, and fees agreed separately. No monthly retainer is included in this proposal.

13Responsibilities & Acceptance

Who does what, and when it is complete.

Betcher Consulting Group

  • Solution design
  • Configuration
  • Data mapping and migration coordination
  • Templates, workflows, and reporting
  • Integration discovery
  • Training and launch support

Peterson

  • Timely access and source data
  • Approved content
  • Business owners and process decisions
  • Participation in testing
  • Approval of the blueprint, migration, milestone deliverables, and launch

Vendor and website partners

  • Required access
  • Technical documentation
  • Agreed changes within their systems

Deliverables and acceptance

DeliverableAcceptance method
Approved implementation blueprintWritten approval by Peterson
Core CRM structure and pipelinesDemonstrated and approved by Peterson
Data migrationSample migration approved; full migration reconciled
Forms, routing, scheduling, templates, workflows, and dashboardsDocumented scenario tests
Integration discoveryFeasibility assessment, field mapping, and agreed handoff plan
Initial AI pilotsAgreed scenario testing, appropriate escalation, suppression checks, a named Peterson owner, and usage-monitoring guidance
Peterson Success CenterInitial Success Center available to designated users.
LaunchTraining delivered and launch checklist accepted
Completion will be assessed against working business scenarios and the approved scope. Separately scoped integrations are not a requirement for core acceptance when an agreed interim handoff supports launch. Material additions, extra project rollouts, extensive historical-data reconstruction, and custom development require an approved change in scope.

14 · Next steps

Where we go from here.

  1. 1Review the proposed scope and four payment thresholds.
  2. 2Confirm the initial projects, teams, datasets, and deliverable allowances.
  3. 3Finalize HubSpot licensing and identify the relevant technical partners.
  4. 4Agree invoice terms, launch support duration, and the implementation schedule.
  5. 5Approve the engagement and schedule kickoff.

Prepared for Peterson · Prepared by Dave Betcher | Betcher Consulting Group · dave@davebetcher.com