Separate connector access, proposed configuration and approved changes before adapting one CRM to different industries.
By Tej Pandya, founder of GrowEasy.ai
I expect more vertical software to become a setup choice on a shared core. For builders, the important question is what happens between "tell us your industry" and "save these changes".
A model can suggest qualification questions. That does not make it safe to rewrite fields, permissions or live records. Treat the suggestion as a proposed configuration, with a review step before it touches the system of record.
Put a typed configuration between the model and the CRM
For an illustrative training-company setup, the proposal might contain a course field, preferred start date, an intake question and a human-handoff rule. An interior-design setup might propose project location and room type instead.
Keep each proposal explicit: field name, type, purpose, allowed values, required status and which workflow uses it. A free-text prompt is not a migration plan. Check the proposal against the CRM's supported objects and the customer's existing fields.
MCP access does not grant permission to change the schema
HubSpot's remote MCP server is generally available. Its April 2026 changelog lists read access and create/update access separately. Supported writes include contacts, companies, deals, tickets, line items and products; some other objects remain read-only.
The connection uses OAuth 2.1 with PKCE and respects existing HubSpot user permissions. When sensitive data is enabled, Activity objects are blocked through this MCP server. None of that release establishes automatic industry-specific schema rewriting.
Build against the tools and permissions actually available to the connected account. If a required operation is unavailable, show that limit instead of generating a plausible tool call.
Preview the difference and test it with fictional records
A useful preview compares the current configuration with the proposal. Show added fields, renamed fields, changed validation and affected reports. Do not hide a destructive change among harmless labels.
Run fictional leads through both versions. Check that qualification, handoff and reporting still mean what the owner expects. Keep the old configuration available, and define how to recover if a change is wrong. These are design recommendations, not a claim that we have shipped this system.
Keep specialist logic outside the generic setup promise
SAP's generative-UI article points toward task-specific interfaces, but also stresses live system-of-record data, familiar structures and complex business logic. A generated form does not replace those foundations.
The goal is a shared core that can express different workflows, not a model pretending every industry's rules are interchangeable. Keep unsupported industries and untested integrations visibly untested.
Sources: https://developers.hubspot.com/changelog/remote-hubspot-mcp-server-is-now-generally-available ; https://news.sap.com/2026/03/why-is-generative-ui-the-new-frontier-for-business-software/
Top comments (0)