AI integration
AI in your tools. Not a chat on the side.
Reply within 1 business day · No commitment
What this avoids
- An AI tool bought, never wired into the work.
- Workflows still manual — quotes, follow-ups, files — while the data is already there.
- An “AI project” with no scope, no pilot, no one who decides.
How we work
Three stages. Someone who already knows your estate, if you are on managed IT.
Scoping
Which workflow, which tools, who uses them, what we leave alone. A written scope before anything is installed.
- Priority use case
- Tools and sources
- Who signs off
Workflows & integration
We connect AI to what exists — mail, files, the job — rather than adding another screen.
- Workflow automation
- Existing connectors
- Rules and access
Project delivery
Pilot, training, usage rules. Not a PoC that dies in a drawer.
- Pilot then rollout
- Short training
- Follow-up after go-live
Sensitive data
AI study on isolated hardware
Your files cannot go to a cloud? We index a representative sample on our loan hardware — wired to a repo you own, or wiped after delivery. Paid engagement, separate from the 30-day AroBox trial.
Written scope
Which mail, which documents, who signs off, how long. Not the whole stack — only what is needed to decide.
Your repo or wipe
Set up on a repository you own if you prefer. Otherwise certified erasure when the study ends — documented procedure.
Deliverable & next step
Report: viable use cases, risks, recommendation. Option to move to the 30-day trial or on-site AroBox deployment.
- nFADP framework — processing agreement on request.
- Inference on private Arobass infra in Switzerland, or entirely on the loan hardware.
Not the IT estate audit (managed IT). Not the free AroBox trial. Quote after scoping.
A typical workflow
Signed quote → file → follow-up
Office or fiduciary — 8 to 20 seats
Someone signs. You need a file, then a chase if nothing comes in. Today that hangs on one person and their inbox.
- 01
Quote signed
The approved document starts the rest — no more hand-copying into a “to file” folder.
- 02
File created
In the right place, with the team’s access. Not a Drive nobody can navigate.
- 03
Scoped follow-up
No payment by the due date: a reminder under your rules — not a bot that spams.
We start from Microsoft 365 or Google, already in place.
Example of a mission, no client name. The exact workflow is scoped at the audit.
Included
- +Written scope (use case, tools, out of scope)
- +Integration on the existing stack and automation of the chosen workflows
- +Project delivery: pilot, training, usage rules
Out of scope
- −The managed-IT retainer (separate offer, same house)
- −Vendor licences and third-party subscriptions (on quote)
- −Training a model on your corpus — we configure, we do not train
Train the team first?
Staff awareness, nLPD, legal and tax framing. A session before you open the tools to everyone.
AI trainingAlready an estate to keep running?
Managed IT remains the contract. AI integration is a separate, scoped mission — usually simpler if we already know your tools.
See managed ITScope the workflow before you buy another tool.
No-commitment audit. We start from your tools. Work on quote — not a managed-IT retainer in disguise.
Reply within 1 business day · No commitment