If it has an API, it is in scope.
Built with you during onboarding, and included with an annual Team plan. Connected before you go live.
Every software company promises integrations and then ships the four its largest customers asked for. Knack takes the opposite approach: every meeting produces a structured record, and we connect that record to whatever you already run. A custom CRM, an in-house system built a decade ago, a warehouse, or the spreadsheet that somehow runs the business. We build the connection during onboarding and it is included with an annual Team plan.
Why we do this instead of a logo grid
A field sales business runs a stack nobody could predict: a CRM, a scheduler, an invoicing tool, a spreadsheet that is quietly load-bearing, and often something built internally that everyone is afraid to touch. No vendor is going to ship native connectors for that combination.
The usual outcomes are both bad. Either you wait forever for your tool to reach the top of someone's roadmap, or you get a shallow trigger in a generic automation tool and are left to build the rest yourself.
We are a product team inside an AI agency, which means building the connection is work we do anyway. So we do it as part of onboarding rather than pretending the problem does not exist.
What a finished meeting gives you to work with
Everything the appointment produced is available as a structured record: the recap, the full transcript with timestamps, the action items, the extracted fields such as quoted price, objection type, competitors named, commitments and outcome signal, plus the customer, the rep and the visit itself.
That means the connection almost never has to call back for more, and it can be as simple or as selective as you want. Some teams push the whole record into a warehouse. Others fire a single alert when a competitor's name is said, or when a quote goes above a threshold, and ignore everything else.
Things teams actually ask us to build
Push the visit into a CRM: Salesforce, Pipedrive, Zoho, ServiceTitan, Jobber, or something in-house.
Post the recap into the Slack or Teams channel that runs the day, so the office knows how an appointment went before the rep is back in the truck.
Alert on a specific trigger: a competitor named, a price above a threshold, an objection type you are tracking this quarter.
Append every visit to BigQuery, a Postgres warehouse, Sheets or Airtable, for teams whose real reporting does not live in a CRM dashboard.
Trigger the operational next step: create the job, schedule the follow-up, send the proposal, open the ticket.
Where the data goes, and where it does not
These are recordings of conversations inside customers' homes, so this deserves a straight answer. A connection sends only what you configure it to send, to a destination you own. If your security posture requires it, the automation layer can run inside your own infrastructure rather than ours, which is usually what makes a security review straightforward rather than a project.
And if a system genuinely has no API, tell us anyway. Sometimes there is a seam, an export, a webhook, or a database we can read. Sometimes there is not, and we will say so plainly rather than sell you a setup fee for something that cannot work.
Do you really connect to anything?
If it has an API, yes, and that covers almost everything a business runs today. Where there is no API we look for another seam: an export, a webhook, a database we can read. Occasionally there is nothing, and we tell you that rather than take a setup fee for work that cannot succeed.
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.
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.
What exactly can you send to another system?
Anything the meeting produced: the recap, the timestamped transcript, action items, the extracted fields such as quoted price, objection type, competitors, commitments and outcome, plus the customer and the rep. You choose which of it leaves.
Can the connection run inside our own infrastructure?
Yes, and for some businesses that is the deciding factor. The content is recordings from inside customers' homes, and keeping the automation layer within your own boundary is usually what turns a security review from a project into a conversation.
What if we change CRM later?
We rewire it. That is the advantage of treating connections as something we build with you rather than a fixed list: switching your CRM is a configuration change on our side, not a reason to leave.
Who maintains the connection when an API changes?
We do. It is part of the plan, not a one-time delivery you inherit responsibility for.
Want this one first?
Design partners decide what gets built next, and what it does.