HubSpot sees every email. It has never seen the meeting.
Built with you during onboarding, and included with an annual Team plan. Connected before you go live.
HubSpot logs the emails, the calls and the video meetings, because software can see all three. The in-person appointment is the one activity it cannot capture, so it arrives as a note someone typed from memory, if it arrives at all. Knack records the visit on the rep's phone and logs it to the deal: a note with what was said, the quoted price and objections as properties you can report on, and the next step as a task. We connect it during onboarding.
The hole in the HubSpot timeline
Open any deal that was won in person and read the timeline. Emails, a couple of calls, maybe a meeting HubSpot created from a calendar invite. Then a gap where the ninety minutes that actually decided the deal should be, and after it a note that says something like "met on site, sent quote."
That gap is not a HubSpot failure. There is genuinely nothing for it to log: no email thread, no call recording, no video meeting. The activity happened in a building HubSpot cannot reach.
It matters more than it looks, because everything downstream is built on that timeline. Deal-stage reporting, forecast accuracy, and any analysis of why deals are lost are all reading a record with its most important event missing. The quote typed from memory a day later is also, quietly, often wrong.
What Knack writes to HubSpot
The visit itself, as a note engagement on the deal and its associated contacts and company, so it lands on the timeline in the right place and in the right order rather than as a free-floating record.
The structured fields as custom properties, which is what turns this from a nicer record into something you can report on. Quoted price, objection type, competitor mentioned, outcome signal and next-step date become properties, so a HubSpot list or report can answer questions like which objection type correlates with lost deals in a given region.
And the next step as a task, so the follow-up exists in HubSpot rather than in someone's memory.
We associate with the records you already have rather than creating new ones. Nobody wants a meeting tool quietly generating a second copy of every customer.
| From the meeting | HubSpot object | Why |
|---|---|---|
| The visit summary | Note engagement on the deal | Lands on the timeline where the gap is today |
| Attendees | Contact associations | The people in the room, linked to the record |
| Quoted price | Custom property | Reportable, so you can compare quoted against closed |
| Objection type | Custom property | Group lost deals by why, not just by stage |
| Competitor named | Custom property | See who you actually lose to, by segment |
| Outcome signal | Custom property | An early read from the room rather than the rep's optimism |
| Next step and date | Task | The follow-up exists in HubSpot, not in someone's memory |
| Follow-up email | Email engagement | Sent from the rep's address, logged on the thread |
Who this is for
Field teams whose company already runs sales on HubSpot: commercial contracting, medical device, industrial and wholesale, plus home services businesses that outgrew a job-management tool and moved to a real CRM.
The common thread is a sales motion where the meeting is in person but the pipeline is managed somewhere that assumes it was not. That mismatch is invisible until someone tries to work out why a quarter went badly and finds the record has nothing in it.
Why does an in-person meeting need to be in the CRM at all?
Because everything downstream reads the timeline. Deal-stage reporting, forecasting and lost-deal analysis all work from a record that is missing its most important event.
Will it create duplicate contacts or deals?
No. We associate with the records you already have, matching on the deal and its contacts, rather than creating new ones.
Can we choose which properties get written?
Yes, and it is worth choosing deliberately. A commercial contractor usually wants quoted price and competitor; a medical device team often cares far more about objection type and who was in the room.
How long does it take?
It is part of onboarding, not a later phase. Your connection is working before you go live, because a meeting intelligence tool that is not wired into where your work already happens is a tool your reps will stop opening in three weeks.
Is there a setup fee?
Integration setup is included with an annual Team plan. We connect Knack to what you run as part of onboarding, and it is working before you go live. Genuinely unusual work, such as an in-house system with no documented API, is quoted separately, and we will tell you that on the call rather than after.
Does this work with HubSpot's free CRM?
The objects involved, contacts, companies, deals and note engagements, exist across HubSpot tiers, though custom properties and some automation depend on your plan. We check your plan during setup and tell you exactly what you will get on it.
Want this one first?
Design partners decide what gets built next, and what it does.