Connected to the systems you already run
OpsUPLOOP doesn’t ask you to replace your CRM or your accounts. Each instance is connected to what your firm uses. These are the connectors running today.
CRM
Insightly
Leads, opportunities, history and tasks, synchronised both ways.
Or no CRM
Your instance can hold leads and deals itself, depending on how it is set up.
Accounting and payments
Xero
Invoices, recurring templates, statements and paid status.
Stripe
Card payment links for payment requests.
Outreach and data
Print and post
Approved letters printed and posted through a mail provider, with delivery states.
Enrichment suppliers
Company and contact data from suppliers you choose, with confirmation before paid lookups.
Website visitor intelligence
Company-level visitor identification, matched to your CRM.
AI
Claude, ChatGPT and other MCP clients
Your own AI connects to OpsUPLOOP over MCP, on desktop or phone, each person with their own permissions and a scoped connection.
Hosted agents
Agents that run inside your instance on schedules and triggers: campaigns, research, scoring, call analysis, customer profiles.
Language models
Research, scoring, drafting and call analysis through a provider’s business API (OpenAI and Anthropic), with usage tracked.
Marketing and hosting
Google Ads
Offline conversion upload from your qualified leads.
Facebook Lead Ads
Leads arrive in OpsUPLOOP with their campaign.
AWS
Read-only hosting inventory and cost allocation to customers.
Your accounts, your credentials, your instance
Connections use your own accounts with each supplier. They are set up with you, in your instance, and only what the modules you use need is connected. Actions that depend on outside data check it first: a chase, for example, confirms the invoice is still unpaid before it goes.
We use a different CRM or accounting system. Does that rule us out?
Not necessarily. Each instance is connected to what that firm uses, and the connector is part of setting it up. If there is no connector yet, building one is part of a made-to-measure setup. Tell us what you run and we’ll say plainly what that involves.
Can OpsUPLOOP run in our own environment?
Yes. Scorchsoft hosts each instance by default, and can deploy it into your own environment instead. We agree what that involves before you commit.
Do we need all of these?
No. You connect only what the modules you use need. A firm starting with Billing needs its accounting system, not a mail provider.
Who pays for third-party usage?
Usage costs from suppliers, such as postage, paid enrichment or AI usage, are yours and are shown to you. Nothing is spent on paid enrichment without confirmation.
Connect your AI to it, and let its agents work
OpsUPLOOP connects AI in both directions. Your own assistant reaches in over MCP, and hosted agents work inside your instance, each within the permissions of the person they act for.
Your AI, connected
Claude or ChatGPT, on your desktop or phone, connects over MCP and answers from your records, as you, within your permissions. You ask; it answers and can take supported actions.
Agents that work in the background
Hosted agents are given a job and get on with it: the nightly campaign agent, research and scoring as each enquiry lands, call analysis, customer profiles. Several steps, real tools, nobody asking.
Ring-fenced and guardrailed
Every agent and assistant runs inside your instance and each person’s permissions. Work that reaches a customer or touches money stops in a review queue; some things AI can never do.
MCP tools across every module
Leads, calls, opportunities, campaigns, invoices, billables, customers, feedback, ownership, objectives and team structure. Read and write tools are granted separately, and every write is recorded.
A connection per person
An administrator issues each person a scoped connection. Their assistant sees what they can see in the app, and says what it left out.
Things AI can never do
Post a letter, raise an invoice from a billable it created, or spend on paid enrichment without a person confirming.
New connectors, built onto the same platform
These are the connectors running today. If your firm relies on a system that isn’t here, Scorchsoft can build the connector as part of a made-to-measure setup, feeding the same records and permissions as everything else. Over time OpsUPLOOP can become the hub your other systems report into, and part of a wider data strategy if you have one.
- Connectors run with your own accounts and credentials
- Hosted by Scorchsoft, or deployed into your own environment
- We say plainly what a new connector involves before you commit
Tell us what you run
We’ll show you what OpsUPLOOP would connect to, what it adds, and what it would ask of your team.
30 minutes, with the people who build it. No slides.