CRM Scenario Build — HubSpot

A complete fictional CRM environment, built from scratch to show fluency with real client-facing systems.

HubSpotCRM DesignPipeline ManagementData Modeling

HubSpot support ticket pipeline showing 9 tickets across statuses

Overview

To get truly comfortable inside a real CRM, I built one out from nothing — populating HubSpot with realistic contacts, companies, and activity, then structuring the pipelines a support or sales team would actually use day to day.

Approach

01
Created 13 fictional contacts across multiple companies, with realistic profiles and relationship history.
02
Built out a full ticket pipeline and a separate deal pipeline, each with logical stages.
03
Logged calls and emails against records to simulate genuine account activity over time.
04
Documented the full CRM data model and ticket pipeline in a support-documentation PDF with captioned screenshots.

In Practice

Ticket Pipeline Management

The Support Pipeline, with 9 tickets split across New, Waiting on contact, Waiting on us, and Closed — worked both as a kanban board and as a sortable list, with a close look at moving a ticket between stages.

HubSpot support ticket pipeline shown as a kanban board — Ticket Pipeline — Board View: 9 tickets across New, Waiting on contact, Waiting on us, and Closed.

HubSpot support tickets shown as a sortable list view — Ticket Pipeline — List View: the same 9 tickets as a sortable table of pipeline, status, date, and priority.

Editing a ticket pipeline stage in HubSpot with quick-action buttons visible — Updating a Ticket's Pipeline Stage: moving a ticket to Closed, with Note/Email/Call/Task/Meeting quick-actions alongside.

Contact & Relationship Management

13 contacts across multiple companies — from the full list down to a single record with its AI-generated interaction summary, linked deal, and open ticket all in one view.

HubSpot contacts list showing 13 contacts across multiple companies — Contacts — All Contacts View: 13 contacts spanning BrightPeak Fitness, Parallel Grove Consulting, and others.

HubSpot contact record for Samuel Chen with recent interactions, linked deal, and ticket — Contact Record — Samuel Chen, BrightPeak Fitness: one contact tied to both its sales history ($2,400 deal) and support history (an open ticket) in a single view.

Deal Pipeline & Data Model

The sales side of the same CRM — a weighted deal pipeline — and the data model underneath that connects tickets, deals, and contacts to each other.

HubSpot sales deal pipeline shown as a kanban board with weighted totals — Deal Pipeline — Board View: 9 deals across four stages, each column totaled by weighted close probability.

HubSpot CRM data model builder listing standard and activity objects — CRM Data Model: the Data Model Builder, listing each object's record count, property count, and associated objects.

Outcome

I came out of this comfortable navigating and structuring a CRM from the ground up — not just entering data into one, but understanding how the pieces (contacts, companies, deals, tickets) connect. That's core to both CRM-focused support and EVA work.

Interested in working together?

Let's talk about how I can help your team run smoother.

Get in Touch