For Proptivity · November 2026

A sales engine for Proptivity

Who to get in touch with this week, and why.

0:00 / 2:09
Read the full proposal below
The proposal · 7 pagesDownload PDF

On a phone, tap any page to open the PDF, or pinch to zoom.

Summary of proposed solution · For Proptivity
Prepared by Eleanor, FounderPill · November 2026

Who to get in touch with this week, and why.
Answered every Monday.

HubSpot is great at sending the email, and ChatGPT can write one. Telling your team who to get in touch with this week, and why, takes the facts joined up: your own data, CoStar, coverage readings and public records. That is what the sales engine does. On the right is an example of what it would show, using 70 St Mary Axe.

Example · Monday · Your best lead this week19 / 19 signals

70 St Mary Axe, EC3

An illustration, built from the report you've seen, scored on the suggested 19 signals
WhoStephen Doogan, Asset Director, Capreon
Why nowWiredScore re-certification under way
The gapYour measured coverage: 13 / 100, 49% poor
Proof3 occupiers already talking to you
BonusSame owner's 280 Bishopsgate scores 8 / 100
"Hi Stephen, with 70 St Mary Axe up for WiredScore re-certification, three of your occupiers have already asked us about indoor signal. Our measured data puts it at 13 out of 100. Worth 20 minutes to see the readings, and how one plan could cover 280 Bishopsgate too?"
Approve and send
Edit
Introducing the sales engine

A system built for Proptivity that sits alongside HubSpot.

It joins up the data you already have with outside sources, and every Monday tells your team who to get in touch with, why, and what to say.

01 · JOINSYour data, in one pictureContacts, buildings, coverage readings, CoStar flags and public records
02 · PICKSWho, and why nowRanks every building on the signals you choose and finds the right person
03 · DRAFTSA note about their buildingYour team approves or edits it in a couple of minutes
04 · SENDSYou take the meetingSent, followed up and booked in HubSpot, with a one-page brief
Getting a tune out of HubSpot

HubSpot is great at what it does, and it stays. Getting the most from it is the hard part: its sequences send whatever you give them, so someone has to keep feeding them the right facts, by hand, every week.

01

What wins a building lives outside HubSpot

Your coverage readings, CoStar events and who decides for each building aren't in it today.

p. 2
02

You can type it in, and keep typing

Your team can add the fields, one building at a time. Within weeks it's stale: LISA, Moderna and the 280 Bishopsgate sale all landed in two weeks.

p. 3
03

Or sequences go out generic

One template and the same steps for everyone, built on whatever was typed in last.

p. 3
04

The sales engine keeps HubSpot fed, every Monday

Every building re-checked against the latest from each source, and HubSpot told who to contact, what to say and when. Your team gets on with selling.

pp. 2–3
Same HubSpotno Enterprise upgrade needed
Minimal trainingbuilt to be easy to understand
About 8 weeksfrom an agreed start date
Proptivity · Sales engine · Proposal, November 20261
HubSpot's role

HubSpot does the sending.
The sales engine does the knowing.

HubSpot is where your emails, sequences, replies and bookings live, and that stays. It can hold all of this, but only if someone lives in HubSpot keeping it up to date, which is what HubSpot wants. The facts that win you a building (who's in it, how bad the signal is, what's about to change) come from outside it. Your team is better spent with customers and prospects.

What each can do

HubSpot aloneHubSpot + engine
Send emails, sequences and follow-ups✓✓
Book meetings into reps' diaries✓✓
See each building as one record: owner, agent, every occupier and contact✕Enterprise only✓
See your measured coverage for that building✕✓
Know about a fit-out, sale or lease event✕✓
Spot an out-of-office, pause, and pick up when they're back✕sequence carries on✓
Rank every building on the signals you choose, weekly✕✓
Write a note with the building's real storyPartly✓

HubSpot can hold any of these as a field, if someone keeps it up to date by hand. The engine fills them in for every building, every week. It keeps the building picture itself and writes the facts onto the right contact as standard fields, so no Enterprise upgrade is needed.

How it fits together

Your database · 45,000 contacts
CoStar · events your team flags
Ookla · where signal fails
Public records · owners, planning
HubSpot · every past touch
+ anything else · not a fixed list
→

The engine

  1. Picks the building
  2. Finds the person and the reason
  3. Drafts the note
  4. Reports what's working as results build up
→
HubSpotRep approves. HubSpot sends and books.
→
MeetingWith a one-page brief on the building or opportunity
You decide the signals. I'll suggest a starting set of 19, such as a fit-out, a lease event, or "we're already talking to a tenant in this building". You choose which to keep, add or drop, and how much each one counts. Sources aren't a fixed list either: whenever you find a new source, report or signal that works, it can be added. Each signal is only as fresh as its source: CoStar events as your team flags them, public records as they're published.

What gets checked each week

Your team, by hand
The buildings someone gets to
The engine
Every building, every signal you choose

Illustrative: each square is a building in your database.

Proptivity · Sales engine · Proposal, November 20262
What the sales engine adds

Same HubSpot, same seats.
A very different contact record.

You can add these fields to HubSpot today. Filling them in, and keeping them right, is the work. Here is the same contact with and without the sales engine.

Example: Stephen Doogan, 70 St Mary AxeSame HubSpot, same seats. The only difference is what the engine writes in.
Without the engineContact record
Stephen Doogan
Asset Director, Capreon
BuildingResearch which building they runBY HAND
Indoor coverageFind the readings, type them inBY HAND
Why nowCheck CoStar every weekBY HAND
Occupiers askingSearch past emails and notesBY HAND
Same ownerCross-check ownership recordsBY HAND
The fields can be added. Filling them is the legwork: for every contact, again every week, or they go stale.
With the engineContact record
Stephen Doogan
Asset Director, Capreon
Building70 St Mary AxeENGINE
Indoor coverage13 / 100, 49% poorCOVERAGE DATA
Why nowWiredScore re-certificationCOSTAR
Occupiers asking3 already talking to youHUBSPOT HISTORY
Same owner280 Bishopsgate, 8 / 100COVERAGE DATA
Next step: approve a specific email, sent this week
Now repeat it for every building, every weekEvery contact at every building in your database, re-checked weekly as tenants, owners and readings change.
The engine does this for every building, every MondayChecked, filled in and up to date before your team starts the week.

And it reports what's working

Builds up over time
Patterns as results build up

A fixed sequence sends the same steps until someone stops to review it. The sales engine tracks every send and reply, and as results build up it reports what's working, such as which days, messages or triggers get replies, so you can adjust.

Spots the patterns
Who actually responds

Which job titles reply, whether landlords or managing agents engage more, which triggers turn into meetings. It finds the patterns across every building, every week.

Reports back
Insight you can use elsewhere

A regular report on what's working, useful beyond outreach. For example, which job titles to target in LinkedIn ads.

It reads every reply, including out-of-offices. A HubSpot sequence keeps to its timetable, so someone on leave can get two or three follow-ups before they're back. HubSpot's own guidance says out-of-office replies generally don't stop a sequence. The sales engine holds the next email until their return date, adjusts the message, notes "away until [date]" on the HubSpot record, and tries the stand-in if the auto-reply names one.

The sales engine can't make the sale. It gets your team the right conversation, with the right person, at the right time.

Example uses the 70 St Mary Axe facts from page 1. Out-of-office behaviour: HubSpot Knowledge Base, "Unenroll contacts from a sequence", checked November 2026.

Proptivity · Sales engine · Proposal, November 20263
The other ways to do it

How other organisations try to achieve this.
A tool for every job, and someone to run them all.

Some sales teams get here by subscribing to a specialist tool for each job. Each is good at one thing. Together they're costly, and keeping them all connected and up to date takes real time every week. And the tools keep changing: one widely shared 2026 post mapped newer challengers overtaking established tools in nine categories, from data sourcing to workflow building. Here is a typical selection for two reps, at monthly list prices.

1Prospecting database£190

Find the people in each building

LinkedIn Sales Navigator
Apollo
2Enrichment and workflows£145 to £390

Pull data together, run research steps

Clay
3Contact details£45

Verified emails and mobiles

FullEnrich
Prospeo
4Signal monitoringQuote

Spot moves, hires and changes

Common Room
Unify
5Automation£20 to £50

Connect the tools together

n8n
Make
6AI writing£40

Draft the notes

ChatGPT Business
Claude
7CRM and sequences£0, already have it

Send, follow up, book

HubSpot
Subscriptions alone, 2 reps
£450 to £700

a month, before signal tools and before anyone's time to connect and run them

Your real options

OptionWho does the workCostWhat you get
AI research by handYour sales team, every weekTheir selling timeReports, not meetings
Run the subscriptions aboveSomeone to connect and run seven tools£450 to £700 a month, plus their timeTools that don't know your buildings
Hire a junior BD teamTwo people researching, emailing and calling£25k to £30k each a year, plus National InsuranceCoverage, once they're trained and managed
Hire a specialist or agencySomeone you don't have yetAround £25k up frontAn engine, then who runs it?
Built and run by FounderPillMe: build, run, improveFrom £2,475, then mostly on resultsMeetings, every week

None of these tools know your buildings, your coverage data or your CoStar flags. The real choice is who joins it all up, and whether they're paid up front or from results.

Proptivity · Sales engine · Proposal, November 20264
Fees

Pay on meetings, pay on deals,
or pay once.

Here are three ways I've structured this kind of work before. They're a starting point, not the only options: I'm open to a conversation about what works for both of us.

Pay on meetings

1 · Success fee

Build, typically 8 weeks£2,475
My time running it each weekIncluded
Per qualified meeting£X, to be agreed

No meetings, no success fee. Paid on results you can see in the diary.

Pay on deals

2 · Partner deal

Build, typically 8 weeks£2,475
My time running it each weekIncluded
Per deal from an engine-flagged building5%
Minimum term18 months

Paid like your referral partners, with a build fee because deals take time to close. Nothing monthly; invoiced once you've been paid.

Pay once

3 · Fixed fee

Build, typically 8 weeks£16,540
My time running it each week£150 / month
On meetings or dealsNothing

One fixed price, owned outright, with no share of results.

What counts as a qualified meeting: a conversation with the right decision-maker for the building, found through the research, who has replied positively and wants to talk. Not a receptionist. We'd agree the exact definition, and the fee, together.
Minimal trainingBuilt to be easy to understand: it runs in the background, your team approves and gets a booked meeting with a one-page brief.
Kept runningMonitoring, fixes and routine tuning are included. New sources, tools or features are quoted separately.
Typical timelineAbout 8 weeks from an agreed start date, pausing over Christmas, and depending on access to your data. Plan on page 6.

Adding tools or features beyond this scope is quoted separately. Tool running costs of about £50 to £150 a month are paid by Proptivity directly to the providers, on top of every option.

Proptivity · Sales engine · Proposal, November 20265
Appendix

The detail, for whoever runs it day to day

What happens in the 8 weeks

Week 1Kick-off and agree
  • Kick-off with your team
  • You choose the signals and how much each counts, from a suggested 19
  • Agree the sources and get access
  • Agree the messaging and tone with you
  • Define a qualified meeting
Weeks 2 to 3Join the data
  • Contacts, buildings, coverage and CoStar flags in one picture
  • Match each contact to the right building
  • Check the matches by hand on a sample
Weeks 4 to 6Build and connect
  • Scoring and note-writing, tested on 50 buildings
  • Connect HubSpot: approvals, sequences, replies, booking
  • Get each part talking to the next
  • Live by around week 6
Weeks 7 to 8Test and tune
  • Full weekly run
  • Adjust from the first replies
  • Hand over the one-page briefs and weekly report
  • Then a monthly review of results

A typical timeline. Weeks count from a start date we agree together and pause over the Christmas break. It depends mostly on how quickly we can get access to your data.

Running costs, paid by Proptivity to the providers

Automation platform (n8n), runs the engine weekly£20 to £50
AI usage (Anthropic), pence per note£10 to £30
Data store, the joined-up building picture£0 to £20
Web and news search, spotting fit-outs, sales and moves£20 to £50
Total a month, excluding VAT. An estimate until the build is costed. Excludes your HubSpot subscription£50 to £150

How results are counted · a starting point, open to discussion

What counts: a qualified meeting with a decision-maker at a building the engine flagged, from outreach it started, who replied positively and wants to talk
Tracking: the engine tags every building and contact it flags in HubSpot, so each meeting's source is clear
Partner deal (option 2): £2,475 build; no monthly fee; 5% of each deal from an engine-flagged building, closed within 18 months of first contact, invoiced once you've been paid. Deals already in your pipeline are excluded. 18-month minimum term; the engine stays FounderPill's, and can be bought outright for £16,540 if you end it early
Success fee (option 1): £2,475 build; running included; a fee per qualified meeting, to be agreed, invoiced monthly
Fixed fee (option 3): £16,540, owned outright; £150 a month to run it each week
Running (all options): monitoring, fixes and routine tuning to keep the agreed engine working. Beyond scope: new sources, tools or features are quoted separately
Assurance: on options 1 and 2, beyond the build fee, you only pay for results
CoStar: your team decides what to flag from CoStar; we'll confirm with CoStar what your licence allows

This proposal is valid until 18 December 2026. Prices checked November 2026 and exclude VAT. HubSpot prices vary by plan and contract; we'll confirm against your account. The engine uses HubSpot's API, included in every plan.

Proptivity · Sales engine · Proposal, November 20266
Appendix · Service blueprint

The difference isn't effort. It's reach.

Buildings checked each week
A shortlist→Every one
Signals per building
A few→Every signal you choose
A new tenant, fit-out or sale
If noticed→The same week

Today: HubSpot, with your team joining everything up

Reaches the buildings someone gets to
1Pick buildings
2Find the reason
3Write
4Send
5Replies
6Qualify
7No reply
8Book
9Prepare
Prospect
A template email
Replies
Books
HubSpot
Loads emails
Sends
Logs reply
Booking page
Your team
Builds a listthe ones you know
Checks CoStar and signalone at a time
Writes a templatesame for everyone
Reads each one
Judges fitcase by case
Moves onlead goes cold
Digs up history
No engine
Two separate maps

With the sales engine: your team approves, confirms and takes the meeting

Reaches every building, every week
1Pick buildings
2Find the reason
3Write
4Send
5Replies
6Qualify
7No reply
8Book
9Prepare
Prospect
A note about their building
Replies
Books
HubSpot
Queues it
Sequence sends
Logs reply
Right rep's diary
Your team
Approves
Confirms
Takes the meeting
Engine
Ranks every buildingevery signal you choose
Builds the casecoverage, CoStar, occupiers
Drafts the notespecific to them
Sorts the replyout-of-offices too
Drafts the answer
Tries the next personnothing goes cold
Avoids clashes
Writes the brief
Your teamEngineAutomaticLine of visibility: the prospect sees only the top rowNothing happens here today
Proptivity · Sales engine · Proposal, November 20267