The OpsUPLOOP platform

One set of records, your permissions, and AI that works within them

Every module stands on the same base: your own instance, one set of records and each person’s permissions, with AI working inside all three. Choose modules on the modules page; this page is what they share.

The assistant connection uses MCP, the Model Context Protocol. This is AI for business operations, not AIOps, which is an IT-monitoring category. Read the guide.

Your own instance

Scorchsoft deploys and hosts a separate OpsUPLOOP for your business, or deploys it into your own environment when it is made to measure. Your records are not stored alongside other customers’.

One set of records

Customers, contacts, deals and people are shared by every module, so nothing is typed twice and every module sees the same picture.

Each person’s permissions

Access is set by role and by what each person owns, and it applies the same way in the app and through an AI assistant.

Access for everyone who needs it

Show people across the business the records they need, scoped to their role, without buying everyone a CRM seat to see a few of them.

Permissions

One customer, seen the right way by each person

Access follows each person’s role and what they own. The founder sees the whole account, finance sees the money, and a salesperson sees their next step, without anyone copying a spreadsheet or buying extra CRM seats to look.

The same rules apply to an AI assistant acting for that person: it can only answer from what they could open themselves, and says what it left out.

IllustrationOne customer, five starting points: each role sees its part of the same record.
AI assistants

Ask Claude or ChatGPT about your business

Most teams paste information into a chatbot one conversation at a time. It can’t see your records, forgets between sessions, and has no idea who is allowed to know what. Connected to OpsUPLOOP, it works from your records instead, within the permissions of the person asking.

MCP connection

Works with Claude, ChatGPT and other clients that support the Model Context Protocol.

Per-person permissions

Each connection acts as its user, with the same access as in the app.

Scoped tools

Read and write tools are granted separately; every write is recorded.

Built-in assistant

Conversational access to your records and research tools inside OpsUPLOOP.

IllustrationYour own assistant, your records, each person’s permissions.
How it works
  1. Connect your assistant

    An administrator issues a scoped connection for each person.

  2. Ask in plain English

    “Which milestones slip this month, and who owns them?”

  3. It answers as you

    Using only the records your role can read, and saying what it left out.

  4. Act, with controls

    Supported edits are recorded. Posting letters and raising invoices are never available to an assistant.

Chat, agents and guardrails

More than an assistant: agents that do the work

Your own assistant reaches in over MCP when you ask. Hosted agents are given jobs and get on with them. Both stay inside your instance and each person’s permissions.

IllustrationAn agent at work: a trigger, several steps with real tools, and a stop where a person decides. No one had to ask it.
Chat

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

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.

Guardrails

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.

Limits

What an assistant can never do

AI does the legwork across every module. Actions that reach customers or money stay with people.

  • Letters created through an assistant can never be sent by it
  • Billables created through an assistant can never raise an invoice on their own
  • Paid enrichment needs explicit confirmation
  • Scheduled agents research and draft, filling review queues for people
Why one set of records

The sum is more than the parts

Sales data, planned billing and delivery ownership are each useful. In one place, each makes the others better, and gives AI the context to help your firm decide.

Customers shape prospecting

Your customers, profiled by sector and size, show Outreach which companies to research and write to next: the same pond as your best work.

Won work shapes the forecast

Planned billing on won work sits alongside a Monte Carlo forecast of the pipeline, so you forecast from what is secured, not only what might close.

Ownership reaches the money

Whoever owns a customer in Delivery can see and chase their billing, and raise it too if you allow, within the same permissions hierarchy.

AI that sees across it all

Connect Claude or ChatGPT over MCP and it answers from sales, billing and delivery together, as the person asking and within their permissions.

Stairway to success

Where is your organisation with AI today?

Choose the closest description. The platform is built to move a firm up these steps, one at a time.

  1. 0 Step zero No formal AI adoption

    People use personal tools without agreed safeguards. Start with one approved way in, on your own records.

  2. 1 Approved AI access Little regular use

    Claude or ChatGPT connected over MCP, each person within their permissions.

  3. 2 Informal professional use Useful, but personal

    Assistants that answer from your real records, not guesses or copied spreadsheets.

  4. 3 Shared best practice Role-based training

    Your criteria written once and used by everyone: rubrics, report types, definitions of good.

  5. 4 Reusable agents Connected tools

    Agents that run on their own: research, scoring, drafting, call analysis, campaigns.

  6. 5 Embedded workflows Measured value

    Agents inside the daily work, with outcomes tracked: scores, letters, billing, ownership.

  7. 6 AI-first strategy Mastery across culture and strategy

    OpsUPLOOP made to measure as the hub of your operations and your data strategy.

Adviser support to help you implement. Moving from step 3 to 4 and beyond is where most firms want help. Scorchsoft’s Managed AI & Automation Improvement Programme works through it with you.

What stands on it

Four modules, one base

The OpsUPLOOP platform Your own instance and records · Permissions per person · Claude and ChatGPT over MCP

Start with any one module. The others use the same records when you add them.

Questions
Is OpsUPLOOP an AIOps tool?

No, OpsUPLOOP is not an AIOps tool. AIOps is AI for IT operations: incident detection and monitoring. OpsUPLOOP is operations software for the business side: sales, customers, billing and people.

Can the assistant see everything?

No. Each connection acts as a named person, with that person’s permissions, and tells you when it has left something out.

Can AI make changes?

Some. Supported edits are recorded and can be reviewed. Actions that reach customers or money, such as posting letters or raising invoices, are not available to an assistant.

What do we need to connect Claude or ChatGPT?

A Claude or ChatGPT plan that supports custom connectors, and an administrator on your side to issue connections.

See it on your own workflow

Tell us which module you would start with: Outreach, Sales, Billing or Delivery. We will show you that part of OpsUPLOOP, set up the way your firm works.

Book a demo

30 minutes, with the people who build it. No slides.