What overlay mode is
Overlay mode connects your existing tools without replacing them. Your Shopify store, Stripe billing, HubSpot CRM, Google Ads, SendGrid email—they all keep running exactly as they are. Profitalize sits on top, reading data from each tool and providing a single view across all of them. No data migration. No workflow changes. No risk. Think of it as a control layer that sees everything your tools are doing without interfering. You get unified visibility, governance, and automation capabilities while your team continues using the tools they already know. Overlay mode is how every Profitalize deployment starts. It is also how many operators choose to run permanently—because the value of a unified view with governance often exceeds the value of replacing individual tools.
The connection process
Connecting a tool takes 2-3 minutes. Click the integration, authenticate via OAuth or paste an API key, and the data sync begins. Shopify: OAuth login, store data flows within 60 seconds—products, orders, customers, and abandoned carts. Stripe: API key, billing data available within 90 seconds—subscriptions, invoices, payment history, and churn events. HubSpot: OAuth login, CRM data syncs in 2-3 minutes—contacts, companies, deals, and engagement history. Google Ads: OAuth login, campaign performance data within 60 seconds. Most operators connect their core stack of 4-6 tools in under 15 minutes. The system maps data relationships automatically—matching customers across tools by email, linking orders to CRM contacts, associating ad spend with conversion events.
Instant value: the unified view
The moment your tools are connected, you see something most operators have never had—a single view of your customer across every touchpoint. Click on a customer and see their Shopify purchase history, Stripe subscription status, HubSpot deal stage, email engagement from SendGrid, and ad attribution from Google—all on one screen. No more logging into five tools to understand one customer. No more reconciling conflicting customer counts between your CRM and your ecommerce platform. The unified view also reveals gaps you did not know existed. Customers in your CRM who have never received an email. Subscribers in Stripe who are not tracked in HubSpot. Ad spend driving traffic that never converts to a known contact. These gaps are invisible when your tools are disconnected. Overlay mode makes them obvious.
First automations
With your tools connected, you can launch cross-tool automations that were previously impossible or required custom code. Start with three high-impact, low-risk automations. First, customer lifecycle tagging: automatically tag contacts in HubSpot based on their Shopify purchase behavior and Stripe subscription status. This takes 10 minutes to configure and immediately improves your CRM segmentation. Second, churn risk flagging: identify customers whose engagement is declining across email, product usage, and support tickets. Third, revenue attribution: connect ad spend in Google Ads to actual purchases in Shopify through the full conversion path. These automations run on your existing tools. Nothing migrates. Nothing changes for your team. You just see more and act faster.
Governance from day one
Overlay mode includes governance from the first connection. Every action the system takes—every data read, every automation trigger, every cross-tool sync—is logged in the audit trail. Set approval thresholds before launching your first automation. Define spend caps if your automations will trigger discounts or ad spend changes. Configure notification rules so the right team member knows when automations fire. Governance in overlay mode serves a dual purpose. It keeps your automations safe, and it builds the proof data you need to make future decisions. Every automation run generates baseline and outcome measurements. By the time you consider migrating any tool to native, you have weeks of proof data showing exactly what is working and what is not.
When to go native
Overlay mode works indefinitely. Many operators run overlay for 6-12 months or longer. The decision to migrate a tool to native should be driven by specific friction points, not a general preference for consolidation. Migrate when a tool creates data gaps that overlay cannot bridge—some tools have limited API access that prevents full visibility. Migrate when integration latency matters—overlay adds a sync delay that native eliminates. Migrate when the cost of the external tool exceeds the value it provides beyond what native covers. For each tool, check your proof ledger. Is the overlay integration causing attribution gaps? Is the sync delay affecting automation timing? Is the external tool subscription justified by capabilities the native module cannot match? Let the data decide. Not the roadmap.