July’s headline is Partner Connect: the CRM-native way of working that your team has had for a long time is now your partners’ too, on their own CRM, in their AI assistant, in their chat tools. Alongside it, AI took over more of the busywork, and two APIs opened the actions that move a program to the rest of your stack.Introw’s whole premise is that the CRM stays the source of truth and everyone works where they already are. Your side of that has been true since the start. July closed the other half of the loop: the partner works from their own systems too, with both CRMs staying systems of record. The rest of the month leaned on AI for the busywork around it, and opened up the two actions that move a program - submitting a form and nudging a partner - to anything in your stack.
Partner Connect: the in-CRM experience, now for your partners too
Working partners without leaving HubSpot or Salesforce is not new for your team; it is how Introw has always worked. What is new is that your partners get the same thing on their side, and more. An Introw card renders on the partner’s own HubSpot or Salesforce record, showing which vendor is on the deal and the live status from your side. From that card the partner links their opportunity to yours, so two pipelines move as one shared deal, or registers a deal that does not exist on your side yet. Partners can now also edit a linked deal straight from HubSpot. One click on the same card opens the co-sell view with the shared timeline and deal coaching, or the entire portal, signed in, with no password to remember. Their CRM is one of the three surfaces Partner Connect covers, next to their AI assistant (Claude, ChatGPT, or any MCP client) and their chat tools (Slack, Teams, WhatsApp), and for a partner with a real sales operation it is the one that changes the relationship: you get real estate on the record their sellers open all day, instead of a portal they forgot the password to. Partner teams get their own workspace with a rebuilt join flow that prefills their organisation and walks them through setup step by step, and you invite a partner straight from a deal you are co-selling. Nobody likes logging into a partner portal, and every point of friction there shows up in adoption. Meeting partners on the surfaces they already work is the work-where-you-are bet applied to the partner’s side of the partnership, with both systems of record staying authoritative (CRM-native). See Partner Connect, Partner CRM, Enable Partner Connect and link a deal, and Register instead of link.Smarter, on-brand certificates
Certificates can now generate an on-brand AI background image and be issued as your organisation rather than only as an individual. It is a small touch that makes enablement feel like part of your brand, with the design work handled by AI instead of your team, which is the AI-native bet applied to something you would otherwise never staff. See Create a certificate and Generate a certificate with AI.One request for marketing funds
Partners now submit a single, fund-agnostic marketing-funds request without having to know which budget it belongs to, and your team assigns it to the right fund at review. Which budget a request maps to is exactly the kind of internal detail partners should never have to learn. Partners can even file the request in plain language and have an AI agent fill the form for them, and every approval step runs agentic review with a human in the loop, which is the AI-native bet removing busywork so a lean team can run more funds with less overhead. See Marketing funds intake.Submit any form from your own systems
Every Introw form is now callable over the API, so a submission can start in your own product, an internal tool, a script, or an agent instead of a person opening a form. It is the same form: the same CRM automation, the same attribution, the same approval queue. Intake stops being something only humans can trigger, which is what lets a large partner’s own systems feed your program directly rather than asking their team to re-key data you already have. The form’s Share form dialog gained an API tab that hands you a runnable snippet plus every field id, so there is nothing to reverse-engineer.partnerId takes the Introw id or the partner’s CRM id, so you drive it off whichever id you already store. A companion GET /api/v1/forms/{formId}/schema returns the same field list from code, with each field’s value type and the allowed values of every picklist, so an integration adapts to a form change instead of breaking on it, and picklist labels are now accepted on submit and resolved to the CRM value. It is composability in practice: Introw as a building block in your stack, not a destination. See the headless vision for where that leads. See Submit a form via the API and the Form submissions API.
Nudge partners at scale, from anywhere
Comments are now an API too, and this one is bigger than it sounds. One call posts a comment on a partner, a deal, a ticket, a task, a form submission, or a commission payout, and the partner is notified on the channel they already use. The signal to chase a partner almost never lives in Introw: it is in a stage-age query, a health score, a certification expiry, an unsigned order form, or an agent’s read of your pipeline. Now whatever holds that signal can act on it, attributed to a real person on your team, with the reply landing in the same thread. Ten thousand partners is ten thousand calls, not ten thousand emails somebody had to write. An agent can do the chasing itself and still leave a human in the loop, which is the AI-native bet applied to follow-up, and because the nudge lands on the record and travels to Slack, Teams, or email, it is work-where-you-are rather than one more portal notification. Comments accept Markdown, andisInternal keeps a comment to your own team. See Nudge partners at scale via the API and the Comments API.
Edit CRM fields wherever you work partners
CRM fields are editable from Introw again, and now everywhere it counts: inline on the partner list and the People list, and on the individual partner and contact records, where the Partner Info card and a person’s fields section show the same columns you configured on their list. You can also relabel a field for partner-facing views without touching the CRM. Fixing a region, moving a lifecycle stage, or correcting a job title is an inline edit on the record your team is already looking at, instead of a trip into the CRM and back. There is no Introw copy of the value to reconcile: what you see is the CRM’s, and what you type becomes the CRM’s, which is CRM-native at its smallest scale. See Show and rename CRM fields and Work a partner record.Internal comments on the same thread
Your team can now post a comment as Internal instead of Everyone, keeping it on the record but invisible to the partner and silent on notifications. Deal strategy, pricing latitude, and risk notes belong on the deal, not in a side channel where the next person to pick it up will never find them, and internal comments are marked in the activity log so nobody has to guess whether a note was shared. Partners have no such control: everything they post stays visible to both sides. See Collaborate on a shared deal.Limit a form’s CRM dropdown without breaking the sync
A form field mapped to a CRM picklist gets its options live from your CRM. You can now hide specific options from a given form while keeping that sync intact. The control is deliberately opt-out: everything shows unless you uncheck it, so an option your team adds in the CRM later appears on the form automatically instead of silently going missing. That is the both-halves answer to a real trade-off, where the alternative was a hand-typed list that drifts from the CRM the moment someone adds a value. Partners see a short, relevant set of choices; your CRM stays the source of the list. See Build and publish a form.Quotes that go out in the partner’s name
A deal’s quote configuration gained a Seller setting: leave it on your organisation, or set it to The partner so the partner’s own company details appear as the seller. A reseller sells to their customer in their own name and on their own paper, and a vendor-branded quote exposes the relationship. Line items also gained Show pricing, so you can show partners which products are on a deal without sending any monetary values at all, for programs where the partner owns the commercial conversation. See Let partners build and send quotes on a deal.A fourth way to discount
Products now offer Custom discount alongside No discount, Partner based, Tier based, and Custom price. It lets a partner set a discount percentage while your unit price stays put, so the line item carries both numbers and the discount is explicit and reportable, where a custom price leaves the margin implicit. The discount method selector was rebuilt around the five methods and is now shared with bulk edit, so you can apply one across a whole catalog. See Discounts.Consent-aware email tracking
Regulators in France and Italy now require recipient consent before email open and click tracking is used, and Introw handles it for you automatically. Tracking is decided per recipient at send time from the country data in your CRM: affected recipients get emails with no tracking in them at all (no open pixel, links pointing straight at their destinations) while the rest of your audience keeps full engagement analytics. It is the CRM as the source of truth doing compliance work, with the posture an enterprise-grade program expects on by default. Nothing to configure. See the full spotlight: Consent-aware email tracking.Also new
- Line charts are now clickable: click a point on a line, multi-line, or stacked-area chart and the drilldown opens scoped to that point, narrowing the date range on a time axis or filtering on the value for a property axis. A spike in a trend is one click from the records behind it. See Report builder.
- Every AI call now routes only to model providers with zero data retention that also do not train on prompts or responses, enforced centrally so no feature can opt out by omission. Being AI-native should not mean handing over your data. See AI Agents.
- Salesforce attribution can now use the Opportunity’s standard
AccountIdas the partner property, which fits distributor and reseller models where the Account on the opportunity is the partner rather than the end customer. See Attribution in Salesforce. - Document translation now covers filenames too, and you can manage each asset’s locale variants in the detail panel, so global content stays tidy for the enterprise-grade programs that run across regions. See Translate an asset.
- Server-side sorting, filtering, and pagination keep the Users table fast even on large teams, part of staying enterprise-grade as headcount grows. See Team management.
- Pending submissions can be accepted or declined in bulk: select them in the inbox, write the message to their partners once, and each submission still runs its own CRM automations, notifications, and approval steps. A reseller program reviewing forty order forms a week no longer pays forty round trips for it, which is low total cost of ownership applied to the daily grind rather than to setup. See Submissions & Approvals.