A sales engine for Proptivity
Who to get in touch with this week, and why.
On a phone, tap any page to open the PDF, or pinch to zoom.
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.
70 St Mary Axe, EC3
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.
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.
What wins a building lives outside HubSpot
Your coverage readings, CoStar events and who decides for each building aren't in it today.
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.
Or sequences go out generic
One template and the same steps for everyone, built on whatever was typed in last.
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.
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 alone | HubSpot + 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 story | Partly | ✓ |
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
The engine
- Picks the building
- Finds the person and the reason
- Drafts the note
- Reports what's working as results build up
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.
And it reports what's working
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.
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.
A regular report on what's working, useful beyond outreach. For example, which job titles to target in LinkedIn ads.
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.
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.
Find the people in each building
Pull data together, run research steps
Verified emails and mobiles
Spot moves, hires and changes
Connect the tools together
Draft the notes
Send, follow up, book
a month, before signal tools and before anyone's time to connect and run them
Your real options
| Option | Who does the work | Cost | What you get |
|---|---|---|---|
| AI research by hand | Your sales team, every week | Their selling time | Reports, not meetings |
| Run the subscriptions above | Someone to connect and run seven tools | £450 to £700 a month, plus their time | Tools that don't know your buildings |
| Hire a junior BD team | Two people researching, emailing and calling | £25k to £30k each a year, plus National Insurance | Coverage, once they're trained and managed |
| Hire a specialist or agency | Someone you don't have yet | Around £25k up front | An engine, then who runs it? |
| Built and run by FounderPill | Me: build, run, improve | From £2,475, then mostly on results | Meetings, 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.
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.
1 · Success fee
No meetings, no success fee. Paid on results you can see in the diary.
2 · Partner deal
Paid like your referral partners, with a build fee because deals take time to close. Nothing monthly; invoiced once you've been paid.
3 · Fixed fee
One fixed price, owned outright, with no share of results.
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.
The detail, for whoever runs it day to day
What happens in the 8 weeks
- 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
- Contacts, buildings, coverage and CoStar flags in one picture
- Match each contact to the right building
- Check the matches by hand on a sample
- 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
- 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.