AI agents that do the work.
On infrastructure you own.
Workmate is a private, single-tenant deployment of AI agents for one organization. It works in Microsoft Teams or Slack, connects to the systems you already run, and every action it can take is switched on by you.
Legal said no to general AI. The work is still waiting.
Most mid-market companies are in the same place. Staff already use consumer AI on their own accounts. IT runs on Microsoft or Google. Legal has blocked anything that sends company data to a vendor it has not reviewed. There is a list of use cases, and none of them are running.
Agents with one job each, on a runtime you control.
A Workmate deployment is four things, and you own all four. The base deployment covers up to four agents and four connectors on one channel. More is scoped in the Blueprint.
See. Record. Refuse.
An overlay can log an action. Only the runtime can refuse it. Three controls come with every deployment, switched on from day one.
Single tenant is the deployment model, not an upgrade tier. Your deployment runs on hardware you own or a server provisioned only for you. Model calls go to hosted providers under your own accounts, on terms that bar them from training on your data. No other client's data touches any part of it.
What is running today. What is not.
Enterprise buyers ask the same questions in every security review. Here are the answers before you ask.
Blueprint. Pilot. Scale.
We do not promise a go-live date before the Blueprint. We put one in writing after it.
Priced per organization. Owned by you.
One deployment fee for the build, then a flat monthly for operations. Scoped to your organization after the Blueprint. Not per seat, not per token.
- Single-tenant deployment on infrastructure you control
- Microsoft Teams or Slack native
- Agents and connectors scoped to your organization
- Capability gating, approval routing and action records
- Managed and iterated by ShooflyAI, reported against your KPIs
- You own the code, the data and the infrastructure
Workmate is not for everyone.
A private deployment only works when someone inside owns it. If any of these apply, we are not the right fit yet.
Every agent needs an owner who approves its first actions and reviews the record. Without that person, the controls have nobody to route to.
We do not hold it yet and we will not pretend otherwise. If a certification is a hard gate for you this quarter, we are not the right fit yet.
Workmate does work inside your systems. If what you need is question and answer over a set of documents, that is a smaller build, and we will tell you so.
Questions from every security review.
What is a Workmate deployment?
A private, single-tenant deployment of AI agents for one organization. It runs on hardware you own or a server provisioned only for you, works in Microsoft Teams or Slack, connects to the systems you already run, and every outbound action is switched off until you enable it.
Where does it run and where does the data go?
On your hardware or a server provisioned only for your deployment. Model calls go to hosted providers under your own accounts, on terms that bar them from training on your data. No other client shares any part of your deployment.
What can an agent do without asking?
Read and summarize what you have connected it to. Anything that changes a record, sends a message, or publishes is off at the code level until you enable that specific capability, and most clients keep an approval step in front of it.
Which channels and systems does it connect to?
Microsoft Teams and Slack are the primary channels, with WhatsApp for field teams. Connectors are built per deployment for the systems you run: Microsoft 365 or Google Workspace, your CRM, accounting, storage and forms. The base deployment covers up to four agents and four connectors. More is scoped in the Blueprint.
Do we own it?
Yes. The code, the data and the configuration are yours outright, on infrastructure you control. If you stop working with ShooflyAI, the deployment keeps running. Monthly operations are a service you can cancel, not a license that switches the system off.
Are you SOC 2 certified? Are you HIPAA compliant?
Not yet on SOC 2, and we have not commissioned a third-party penetration test. What exists today: a documented threat model, single-tenant isolation, capability gating and approval routing in the runtime, and a 72-hour breach notice in our agreement. If your procurement requires SOC 2 today, we will tell you so on the first call. Health data engagements are scoped case by case under a BAA.
What does it cost?
A deployment fee for the build, then a flat monthly for operations, support and iteration. Priced per organization after the Operating Blueprint, not per seat and not per token. The Blueprint is $6,000 and is credited in full if you proceed.
Start with the Blueprint.
One company-wide assessment that maps the function, the systems, the controls and the order to build in. Credited in full if you proceed. Bring your IT and legal leads to the first call.
or email jonathan@shooflyai.com