# Connect what you already run. Nothing migrates. Your knowledge, your performance data, and the channels your locations work in, read at the source with the permissions they already have. It reads, and where you allow it, it writes back. ### CONNECTIONS · ADD A SYSTEM ● CONNECTING ● CONNECTED #### Mindbody Scheduling · 214 locations OAUTH **SCOPES YOU GRANT** ✓ Appointments and capacity READ ✓ Client visit history READ ✓ Create a booking, held for approval WRITE ### READING AT THE SOURCE no copy stored “**How booked is next week?**” 62% booked. Read from Mindbody one second ago. - **Your content stays where it is. So do your systems.** You have been asked to choose between the best tools and one system that sees everything. **The document you fix on Tuesday is the answer your network gets on Wednesday**, with no migration, no sync job, and no cleanup project first. - **No content migration** Your SOPs stay in Drive, SharePoint, or your LMS. It reads them in place, at the version live today. - **No data warehouse** Performance data is read at the source when a question needs it. Nothing is copied and nothing goes stale. - **No cleanup first** You do not reorganise your documentation before anything works. It reads what you have and tells you where the gaps are. - **No consolidation** Keep the POS your operators like, the LMS your training team built, and the CRM your development team runs on. ## Knowledge, data, channels, and the systems where the work gets done. Eight categories, 250+ systems, connected at the source. Proprietary platforms and internal databases connect through the API, typically inside two weeks. ### ERP & FMS The franchise systems your network runs on. - FranConnect - ServiceTitan - Mindbody - Zenoti - Thryv + more ### Drives & storage Every document your brand has written, wherever it lives. - SharePoint - Google Drive - Dropbox - Box - OneDrive + more ### LMS & training Courses, certifications, and brand standards. - TalentLMS - Docebo - Trainual + more ### POS & transactions What sold, when, and at what ticket. - Toast - Square + more ### Accounting P&L, invoices, payments, and royalties. - QuickBooks - Xero + more ### CRM Who your locations talk to, and what happens next. - Salesforce - HubSpot + more ### Video & comms The channels your teams already meet and talk in. - Microsoft Teams - Slack + more ### Marketing Campaigns and brand assets, drafted on brand. - Mailchimp - Constant Contact + more --- **The integrations we don’t have, we build.** Franchise networks run on software nobody else has heard of, and a directory can only ever list what exists today. Anything missing gets built as a custom connection through the API, so coverage is a question of time rather than of whether your stack qualifies. ## Reading is what most platforms mean by integration. **EZee Assist acts.** A draft written back to your marketing tool, a ticket opened in your service desk, a task assigned in your scheduler. Every write waits for the approval you set, and lands in the system your team already works in. ONE SOFT WEEK AT STORE #3314 SYSTEMS TOUCHED - Reads next week's capacity from Mindbody 62% booked, 340 clients lapsed past 90 days READ - Drafts the reactivation offer in Mailchimp Brand-approved template, 340 recipients, unsent WRITE HELD FOR OWNER - Opens the follow-up task in Microsoft Teams Assigned to Dana R., the coach for West territory WRITE - Logs the approved spend against QuickBooks Local marketing budget, with the owner's approval attached WRITE Owner approved at 6:50pm. Every write landed in the system that owns it, with a record of who allowed it. ## It cannot show someone what their own system would not. Connections inherit the permissions already set in the systems they read from, plus the role and location rules you set here. One question, asked by three people at the same minute. **ONE CONNECTION · 11:20AM** “How did last week close against target?” - Shift lead Store #118 SEES Their own location's schedule and the policy behind it DOESN’T - Owner Store #118 SEES Everything above, plus their P&L and their team's hours DOESN’T Any other location's numbers - District manager West territory SEES All twelve locations in their territory, compared DOESN’T Territories they don't manage **Inherited, not rebuilt** It reads what your systems already enforce. Read-only by default. Write access is granted per system, never assumed. Logged with the answer: Who asked, what they could see, which sources were used. Revocable. Disconnect any system at any time, since nothing was copied. --- ## Send us your stack. We’ll tell you what connects. List what your locations run and we’ll show you exactly what it reads, what it can write back, and what that changes in the first week.