This playbook is how Collingwood uses HubSpot from first contact through to a closed deal. It covers both Advisory pipelines, New Business (new clients and fresh mandates) and Existing Customers (renewals and upsells), and the reporting and tools that run off them.
Everything in HubSpot exists to give the business one reliable, shared view of the pipeline. When records are complete and up to date, forecasting works, reporting is trusted, and nobody has to chase. When they're not, the whole picture breaks. That is why a handful of behaviours in this guide are treated as non-negotiable.
Five behaviours underpin everything else. If these are right, the pipeline runs itself.
- Calls, emails, meetings and tasks logged against the deal. This is the raw material for every report.
- Owner, associated contact and company, amount, close date, contract start date and Deal Category, on every deal.
- New clients and mandates in New Business; renewals and upsells in Existing Customers.
- The owner is whoever leads the deal, not whoever makes it show up in a report.
- A next activity is logged (call / email / meeting / task, future-dated)
- Owner, contact, company, amount, close date, contract start date and Deal Category are all filled
- It's in the right pipeline
This is the engine room of the whole system. Every call, email, meeting and task must land on the deal, automatically wherever possible.
Email logging works on two levels. Understanding the difference is what keeps the CRM complete without extra effort.
- When your Microsoft 365 mailbox is connected to HubSpot, emails to and from known contacts log automatically, no panel, no clicking.
- Replies to logged emails sync back to HubSpot automatically.
- Sent items are visible in both HubSpot and your Outlook Sent folder.
- This is the always-on layer. It relies on the mailbox being connected with the account rule set to log emails from known contacts.
- Emails from people who aren't in HubSpot yet don't log. Log them from the add-in, which can also create the contact.
- The sidebar inside Outlook. Use it to log an email to a specific deal, create new contacts from an email, or retroactively log.
- Also gives you open/click tracking and notifications.
- Use this when you need an email tied to a particular deal rather than only the contact.
Fathom records calls and writes the AI summary into the deal. The summary lands in the internal meeting notes on the record and is the source the proposal brief automation reads from (section 09).
- Connected Outlook logs emails to/from known contacts automatically
- Use the Office 365 add-in to log an email to a specific deal
- Log calls in HubSpot: they feed Next Activity Date
- Fathom writes call summaries onto the deal
- Always keep a future next activity on every open deal
Contacts are the foundation of the CRM. Get the basics right and everything downstream works.
- Always search before you create, avoid duplicates
- Create the contact first, then the company
- Log everything against the record
- Marketing consent set correctly
Always search before you create. Duplicates fragment history and break reporting, so search by name, email and company first. Create the contact before the company: the association then flows naturally and company data populates against the right record. Log everything, every time (see section 02). Marketing consent must be handled correctly at creation.
How a contact becomes a lead, and how to create one yourself.
Before the lead: how HubSpot decides
- Is the company already a customer? Then HubSpot does not create a lead. New work for a customer goes in the Existing Customers pipeline.
- Is the company ICP? HubSpot checks the type of company, its annual revenue and its number of employees.
- An ICP contact becomes a lead when their score passes the ICP threshold, or when they fill in the Contact Us form.
- A contact that is not ICP becomes a lead when they pass a separate threshold, or fill in a form.
- Revenue and headcount do not stop a lead. They decide if it is ICP or not.
Lifecycle stage follows the lead
- Only ICP leads become MQL. Leads that are not ICP skip MQL.
- A qualified lead becomes SQL. A deal in the later stages becomes Opportunity. A deal won becomes Customer.
- Subscriber means newsletter subscribers only. Lifecycle stage is not a segmentation tool: use the other fields for that.
When you create one
- Link it to a contact or a company.
- Name it, keep the Lead pipeline and the New stage, and check the owner.
- If it comes from a campaign, pick the BD Campaign.
Six stages, from New to a decision. Move the lead on as you work it.
| Stage | What it means |
|---|---|
| New | The lead is new. Nobody has contacted them yet. |
| Attempting | You are trying to reach them. |
| Connected | You have spoken to them. |
| Meeting Booked | A meeting is in the diary. |
| Qualified | There is a real opportunity. Create the deal from the lead: Deals, then Add (section 06). |
| Disqualified | Not a fit now. Pick a reason and add a short note on why. |
Finding your leads
- CRM, then Leads. The board has one column per stage.
- My Leads shows only the leads you own. The other views: Open leads, Target Accounts, CF Leads and CF Hot/Warm/Cold.
- Click a lead to open it in a panel on the right, with the stage tracker, the contact and the activities.
A deal is created after the initial call, once there's a genuine opportunity. Three things must be right at creation.
- Set Deal Category, Project or Retainer (add Upsell / Winback if they apply)
- Choose the right pipeline: New Business or Existing Customers
- Build the deal value from line items in the product library
- Fill owner, contact, company, amount, close date, contract start date
Deal Category is a mandatory multi-select. Set Project or Retainer as the core classification on every deal, and add Upsell and/or Winback alongside where they apply (e.g. Retainer + Winback). Reporting, company measurement and automated comms all run off this, so it has to be correct every time.
| Situation | Pipeline |
|---|---|
| New client or a fresh mandate | New Business - Advisory |
| Renewal or upsell on a client we already work with | Existing Customers - Advisory |
Build the deal from line items pulled from the product library: the full productised catalogue is in there. The modules carry their own value and pricing, so the deal value and reporting come straight from what's in scope. Do not type a value in by hand.
Two Advisory pipelines, each with its own stages. Use the one that fits the deal (section 06).
What has to be true on a deal as it moves: the fields that make it complete, and the one date that gates progression.
A date field on every deal. The owner sets it once a proposal is realistically in sight and updates it as the timeline firms up. It feeds the pipeline forecast so efforts can be coordinated ahead of time. It becomes required to move a deal into Discovery 1 Completed (New Business) and Proposal Made (Existing Customers). Visible on the record and the board cards.
- Set it once a proposal is in sight, update as it firms up
- Required to reach Discovery 1 Completed (NB) / Proposal Made (EC)
Every deal needs these fields filled. Each one is exactly what the weekly deal hygiene report checks, fill them and your deal is never flagged. This is the direct link between doing it right and staying off the report.
| Field on the deal | Why it matters | Hygiene flag if missing/wrong |
|---|---|---|
| Next Activity Date | The next scheduled step. Set automatically when you log a future call/email/meeting/task. | No next activity |
| Deal owner | Whoever leads the deal. | No deal owner |
| Associated contact | At least one contact linked. | No contact linked |
| Associated company | The company linked. | No company linked |
| Amount | Built from line items, never zero. | No deal value |
| Close date | Realistic, not left in the past. | Close date in the past |
| Contract start date | On or after the close date. | Starts before close |
| Deal Category | Project/Retainer set. | No deal category |
| Time in stage | Keep deals moving; don't let them sit. | Same stage 30+ days |
From D2 to signature, including the automated proposal brief that means nobody starts from a blank page.
When a New Business deal reaches Discovery 2 Completed, a proposal brief can be generated automatically. It pulls the deal data, the Fathom call notes from the record, and the client's material and prior proposal from their SharePoint folder, and fills the firm's proposal briefing template in Word. The deal lead edits and fills the gaps rather than building the brief from scratch. Scope: New Business.
- At Discovery 2 Completed, generate the brief
- It pulls deal data + Fathom notes + SharePoint material into the firm template
- Edit and fill the gaps, don't start from scratch
How a renewal or upsell moves from contract end in sight to signed, and, critically, when to create the deal.
- Contract end in sight and worth pursuing → create the renewal deal + start the proposal
- VCB, where scheduled → scope, first draft ready
- Proposal made → negotiation → legals → close
Ownership is the foundation everything else sits on. If it's wrong, every report built on top of it is wrong too.
Deals often change hands. A deal originated at initial call and D1 by one person frequently passes to a different deal lead to run to close. When that happens, the owner must be updated to the person now leading it. Origination is tracked separately for credit. It does not mean that person stays the owner.
- At creation: set the owner to whoever will lead the deal from here.
- On handover: when a deal passes to another lead, change the owner there and then. Don't leave it stale.
- Check your own deals: periodically review the deals against your name and confirm they're yours.
Origination and ownership are two different things and they are recorded in two different places. Deal Originator is a field on the deal record. It holds the person who brought the deal in, and it stays with them after ownership passes to whoever ends up leading the work. That is where credit and the commission position live.
- If you bring in a deal you will not lead: put yourself in Deal Originator and set the deal lead as the owner.
- If you bring in a deal and lead it yourself: you are both. Set both fields to your name.
- To see everything you have originated: filter the deal list by Deal Originator. You keep sight of your deals whoever owns them.
- Owner = whoever leads the deal
- Deal Originator = whoever brought it in, and it stays with them
- Change the owner at the point of handover
- Review the deals under your name and confirm they're yours
A live snapshot of the pipeline, emailed every week, so reviews focus on the exceptions rather than reading out the whole board.
- Wins this week
- Stalled deals
- What's closing / overdue
- Deals with no next step
- New & moved: what's changed, from → to
The always-on version lives on the dashboard, see section 15.
Every live engagement and when its contract ends, so renewal and upsell conversations start before the work runs out.
- Every live engagement, sorted soonest first, so what is ending next sits at the top
- The contract end date for each client, taken from Float
- The VCB date where one is scheduled, labelled finalised or not finalised
- Your cue: where a renewal or upsell is worth pursuing, create the deal in Existing Customers and start the proposal
Dates come from Float, using the latest scheduled end across each client's live work. If one looks wrong, flag it and it gets corrected at source rather than worked around.
The weekly check that keeps the pipeline clean enough to trust. Nine checks, run across both Advisory pipelines.
Each open deal is checked against nine rules. Owners get a reminder of their own flagged deals; a management summary goes out weekly; and a live dashboard shows the current state at any time.
| Check | What it catches |
|---|---|
| Close date in the past | Deal still open with a close date that's already gone. |
| Contract starts before close | Contract start date earlier than the close date, a logical error. |
| No next activity | No next step scheduled, or the next activity date has passed. |
| Same stage 30+ days | Deal hasn't moved in over a month. |
| No deal owner | Owner missing. |
| No deal category | Project/Retainer not set. |
| No deal value | Amount missing or zero. |
| No contact linked | No associated contact. |
| No company linked | No associated company. |
- Each owner gets their own flagged deals to fix. The sales week closes Thursday, so everything should be up to date by then.
- A summary of the pipeline's hygiene goes to management to review and follow up.
Always-on views of the pipeline and hygiene. Click through any time, no need to wait for the email.
Fathom records calls and writes the AI summary onto the deal.
- The AI summary lands in the internal meeting notes on the record.
- It's the source the proposal brief automation reads from (section 09), so a clean Fathom summary makes for a better brief.
The reusable assets (frameworks, agendas and templates) that keep the process consistent.
- Initial call and D1 frameworks are actively used and sent by BD.
- Information request templates for the client data chase.
- Proposal templates (new business and renewal).
- The proposal briefing template, filled automatically by the brief automation (section 09).
The by-stage nurture that runs as deals progress, and the one important exclusion.
Two items of data that keep the client base accurate and let comms come from the right person.
The Engagement Lead is a user field on the contact identifying who owns the relationship. Set it on the contact so client comms come from the right person rather than a generic address.
A live client is flagged by setting the customer flag on the company to Yes. This is what separates current clients from the rest of the database for reporting and segmentation. Keep it accurate as clients come on board and roll off.
- Set the Engagement Lead on the contact
- Mark live clients with the customer flag = Yes on the company
Each thing we need to know about a company lives in one field. Lists, reports, dashboards and the TAM and SAM are built on these fields and nothing else.
| Field | What it holds | How it's filled |
|---|---|---|
| Which of the following best describes your company? | Ownership, and whether the business is B2B or B2C. | By hand, or by a form answer. |
| How would you define your core business? | What the company does. More than one answer is allowed. | By hand, or by a form answer. |
| Industry Vertical | The sector the company serves, such as legal, retail or construction. | By hand or by enrichment. No form asks for it. |
| What is your Annual Revenue? | Revenue band: <3m, 3-5m, 5-10m, 10-25m, 25-100m or >100m. The band carries no currency. | By hand, or by a contact's form answer when the company has no revenue. |
| Primary Company Currency | GBP or USD, the currency of the revenue band. | Required whenever a revenue band is entered by hand. |
| Employee Range | Headcount band. The reference for reporting and targeting. | By hand, or by enrichment when it's empty. |
| Number of Employees (Human Verified) | A headcount a person has checked. | By hand. Entering it updates Employee Range to the matching band. |
| Country | The country, picked from a standard list. | By hand or by enrichment. See D5. |
| State (US only) | The US state. Blank for every other country. | By hand or by enrichment, US companies only. |
| Data Flag | Shows when two fields disagree, or a field that identifies the company has changed. | Set automatically. See D4. |
- Lists, reports and segmentation use the fields in this section only
- A revenue band always goes with its currency
- Headcount means Employee Range, not Number of Employees
- State only for US companies
Automated sources only fill fields that are empty. Enrichment and the contact record never replace a value already on a company, and HubSpot's own estimates never fill our fields at all. Forms are the exception for a few questions, set out in D3.
| Source | When it can change a company master field |
|---|---|
| A person, by hand | Always. A revenue band needs its currency. |
| A form | Depends on the question. See D3. |
| The contact record | Revenue only, and only when the company has no revenue. |
| Enrichment | Only when the field is empty. |
| A human verified headcount | Always. A person has checked it, so it replaces what's there. |
HubSpot's own revenue estimates never fill our fields. When we tested them against what we already knew, they were right about seven times in ten, and a wrong figure in a master field looks exactly like a real one. A company with no revenue stays blank until someone finds out, and the blank shows the gap.
A contact takes its employee numbers and core business from its primary company. When a contact is linked to more than one company, the primary decides what the contact shows, so set it to the company the person actually works for.
- Enrichment and the contact record only fill empty fields
- Forms: D3 sets out what each question changes
- Leave a field blank rather than guess
- Set the right primary company on every contact
Forms used to be where most bad company data came from: someone at a target company would guess at their revenue on a download form, and the guess replaced what we knew. This is what each answer does now.
| Form question | Where the answer goes | If it differs from the company |
|---|---|---|
| What is your Annual Revenue? | The contact's own revenue and currency fields. It fills the company only when the company has no revenue. | Neither value changes. Both records get the Annual Revenue flag. |
| How would you define your core business? | The company. | The answer replaces the company's value. |
| Which of the following best describes your company? | The company. | The answer replaces the company's value. |
| Company name and domain | The company. | The change goes through, and the company gets the Company Name/Domain Updated flag so it can be checked. |
Revenue and the business model are treated differently on purpose. Revenue is a figure people often guess at, so a form answer is held on the contact and never replaces the company's band. Anyone at a company knows what the business does and whether it's B2B or B2C, so for those two questions the latest answer is trusted.
On contacts, the Form Data overwritten flag is on test on the CMR26 form. It marks a contact whose first name, last name or company domain was changed by a form.
- Start from one of the two templates, [FORM TEMPLATE] Clone this for new forms or FORM TO CLONE FOR DOWNLOADS. Their fields already point at the right properties.
- Ask for revenue with the contact's What is your Annual Revenue?, never the company's.
- Before adding a question, check whether a field in D1 already holds the answer.
- The careers form doesn't create HubSpot contacts: applications go straight to HR.
- Build new forms from the templates
- Revenue questions go to the contact, never the company
- A revenue answer never replaces the company's band
A flag means two fields disagree, or a field that identifies the company has changed. It shows in red in the Data Flag field at the top of the record.
| Flag | On | What it means | What to do |
|---|---|---|---|
| Annual Revenue | Company and contact | The contact's revenue band, from a form, differs from the company's. | Correct whichever is wrong. When the two match, the flag clears on both. |
| Emp No/Range | Company | Number of Employees doesn't fall inside Employee Range. | Correct whichever is wrong. Employee Range is the reference. When they agree, the flag clears. |
| Company Name/Domain Updated | Company | The company's name or domain has changed. | Check the change is right, and where it came from. |
| Form Data overwritten | Contact | A form changed the contact's name or company domain. On test on the CMR26 form. | Check the details are right. |
Flagged records are also listed in a HubSpot dashboard. Seen together they show patterns, so a form or an integration that keeps causing problems can be found and fixed at the source.
- A red Data Flag means two fields disagree
- Fix the fields so they match: the flag clears itself
- Never untick a flag by hand
From the week of 28 October 2026, country and state on company records are dropdowns rather than free text, so every country is written the same way and reports pick them all up.
| Before | Now | Notes |
|---|---|---|
| Country/Region country, free text | Country country_dropdown | A standard list of countries. United Kingdom and United States at the top, the rest alphabetical, with a search. |
| State/Region state, free text | State (US only) state_us_only | The 50 US states plus Washington DC. Only for US companies. |
| Country/Region Code, State/Region Code | Removed | No longer needed. |
For the UK and everywhere outside the US, leave State blank and fill in City. Contact records keep their own Country/Region, which hasn't changed.
Country names follow the international ISO list, so a few read differently from what people tend to type: Netherlands (Kingdom of the), Türkiye, Korea (the Republic of), Viet Nam. United Kingdom and United States are written exactly as before.
- Pick the country from the list
- State only for US companies
- UK and elsewhere: fill in City
Five terms, used the same way in every report, dashboard and conversation. They're built on the fields in D1.
| Term | What it means |
|---|---|
| Total Database | Every company in HubSpot. |
| TAM | Every media or events business, of any type and any size: B2B and B2C, independent, private equity backed, publicly traded, corporate groups, and private equity funds themselves. Suppliers to media and events, companies that have told us they aren't a media business, and unclassified companies sit outside it. |
| SAM | B2B media or events businesses in the UK or the US with 11 or more staff, independent, private equity backed or publicly traded, plus private equity funds of any size. B2C is in the TAM but not the SAM. |
| Target accounts | Accounts the sales team has chosen to win as paying clients, where Target Account is set to true. A company is "assigned as a target account". |
| Customers | Anyone who has bought something from us. |
Unless a report says otherwise, it covers the UK and the US together. A report can cut further, for example the TAM in the US, but it says so, and the definition underneath doesn't change.
A group counts once. A parent and its media subsidiaries are one row, under the highest company in the chain that isn't a fund, so a fund that owns ten separate companies gives ten rows. The group is in the SAM if any company in it meets the criteria.
The TAM and SAM describe the market, so a company turned down as a target account stays in them. Duplicates don't: AI enriched copies waiting for review, and subsidiaries already counted through their group.
- Total Database: every company
- TAM: every media or events business
- SAM: B2B media and events with 11 or more staff, plus PE funds
- Target accounts: chosen by the sales team
- Customers: anyone who has bought from us
A few rules that keep the clean-up from coming undone.
- Most information already has a field. Check D1 before asking for a new property.
- A blank shows the gap. A guess looks like a fact, and nobody checks it again.
- Never remove contact-company associations in bulk. They were added for a reason, and removing them drops contacts out of lists such as the SAM. Changing the primary company is fine.
- Link two companies as parent and child only where one consolidates the other's accounts.
- Check D1 before asking for a new property
- Leave it blank rather than guess
- Never remove contact-company associations in bulk
- Parent and child only where accounts are consolidated
Seven steps that set HubSpot up for you. Most come with a video under two minutes.
| Step | What to do | Video | HubSpot guide |
|---|---|---|---|
| 1 Your account | Michele sets up your user and sends you an invitation by email. | ||
| 2 Log in | Go to app.hubspot.com, enter your work email and sign in with Microsoft. | Log in to HubSpot | Log in to HubSpot |
| 3 Second check | In Settings, go to General, then Security, and set up two-factor authentication with a passkey or an authenticator app. Keep the backup codes somewhere safe. | Set up your second check | Set up two-factor authentication |
| 4 Your profile | Click your profile picture in the top right, then Profile & Preferences. Check your name and add your phone number. | Manage your profile and preferences | |
| 5 Outlook | In Settings, go to General, then Email. Connect your inbox with inbox automation on, then your calendar, and install the HubSpot Sales add-in when HubSpot offers it. In the HubSpot pane in Outlook, turn on Log email so your emails are logged by default. | Connect Outlook, Log your emails | Install the HubSpot Sales add-in |
| 6 Teams | In Settings, go to Integrations, then Connected Apps, and open Microsoft Teams to check that your Teams account is linked. Under Notifications, tick Contacts and companies, Deals and Tasks in the Microsoft Teams column. | HubSpot in Teams | Connect HubSpot and Microsoft Teams |
| 7 Your phone | Install HubSpot from the App Store or Google Play, sign in with Microsoft and allow notifications. | HubSpot on your phone | Install the HubSpot mobile app |
All the set-up videos are in the Onboarding checklist folder on SharePoint.
- Invitation from Michele
- Log in with Microsoft
- Set up your second check
- Check your profile
- Connect Outlook and turn on Log email
- Link Teams and its notifications
- Install the app on your phone
Short videos on the work you do every day in HubSpot. Watch them in any order.
| Video | What it shows | Section |
|---|---|---|
| Find and read a record | How to search, and what each part of a company record tells you. | 00 |
| Log your emails | How to log emails from Outlook on the contact, company and deal. | 02 |
| Meetings and calls | How to log meetings and calls, and their outcomes. | 02 |
| Tasks and follow-ups | How to set the next step, so nothing is forgotten. | 01, 02 |
| Add a company and a contact | Search first, fill in the forms, link the contact to its company, and what to do when a contact changes company. | 03, D7 |
| Work a lead | Create a lead, move it through the stages, and qualify it to a deal or disqualify it with a reason. | 04, 05 |
| Create a deal | The right pipeline, the fields to fill in, and how to move a deal through its stages. | 06, 07 |
| Templates and snippets | How to use the emails and text you write most, from Outlook. | 17 |
| Share a document | How to send a tracked link instead of an attachment, and see who opened it. | 17 |
| Your saved views | How to make and save the views you need for your role. | 00 |
How HubSpot works, in six parts: set-up, the filing cabinet, the objects, daily work, sales content, and views and lists. Click through it here: the drawers, tabs and steps all work.
Anything you need from HubSpot goes through a ticket, so it is tracked, it does not get lost, and we can see what keeps coming up.
- Go to CRM, then Tickets.
- Switch to Board view and select the HubSpot Tasks and Requests pipeline.
- Add a ticket in the New column.
- Give it a clear title, a short description of what you need and why, a priority, and a link to the record if the request is about a specific contact, company or deal.
Creating it from the New column fills in the pipeline and status for you, so there is nothing else to set.
- CRM → Tickets → Board view → HubSpot Tasks and Requests → add to New
- Title, description, priority, link to the record
- New → Working On → Waiting on requester → Completed