Price
Quoted per project
A written quote after discovery, before any work starts.
Custom AI Integrations · After the plan
AI that works
inside the tools
you already use.
Sometimes a roadmap item needs more than advice. We connect AI to the tools and workflows your company already uses: an assistant that answers from your own documents, an automation between tools, or AI connected to your CRM, email or helpdesk. Set up in your accounts, with the access and data rules your team agreed.
The useful detailsQuoted per project. Each project is scoped and quoted in writing before any work starts. It usually follows an AI Readiness Assessment or a consulting engagement, so we already know your tools, your data rules and which task is worth connecting.
No card needed. Nothing is built until you approve a written scope and quote.
Custom AI Integrations
Your tools, connected carefully.
Your documents
Your workflows
Your access rules
Scoped and quoted per project
AI + a human touch
Usually after
An assessment
An AI Readiness Assessment or a consulting engagement.
Yours to keep
Your accounts
Built in your accounts, documented, with admin access kept by your team.
What this is, and what it isn’t.
What this is
- AI connected to tools you already use, for a specific task
- Scoped tightly enough to test properly and explain in plain language
- A person checking the output wherever it reaches a client or a decision
- Written documentation and training for the people who use it
- Security and data settings agreed before anything is connected
What we don’t do
- Build standalone apps, customer-facing products or software from scratch
- Resell software or push a particular vendor
- Replace your IT provider or run your infrastructure
- Automate decisions about people, such as hiring, or professional advice, without a person deciding
- Connect AI to information you haven’t approved
- Promise a number of hours saved
Kinds of integration.
Generic examples that apply in most industries. What makes sense for you depends on your tools and your data rules.
01 · Your documents
An assistant on your own documents
Answers staff questions from the documents you choose, such as procedures, policies, templates and past proposals, and shows which document each answer came from. It only sees what you put in its library.
02 · Workflows
Workflow automations
The repeated steps between tools. For example: a web form comes in, AI summarizes it, and it lands with the right person with a draft reply to review. Or meeting notes become action items in your task tool.
03 · CRM
AI connected to your CRM
A summary of a client’s history before a call, follow-up emails drafted from your notes, or incoming records tagged and tidied. A person approves anything before it goes to a client.
04 · Email
Email and shared inboxes
Incoming requests sorted and labelled, key details pulled into a spreadsheet or system, and replies drafted for someone to check and send.
05 · Helpdesk
Helpdesk and support tools
Suggested replies drawn from your own help articles, tickets tagged and routed, and long threads summarized when a case changes hands.
06 · Reports
Recurring documents
First drafts of the reports and documents you produce on a schedule, built from the data you already keep, in your own format, for a person to review.
How we work
- Discovery. We confirm the task, the tools involved, who will use it, what information it touches and what “working” means. This usually builds on what the assessment or consulting work already found. You get a written scope and quote.
- Design. A short written design in plain language: what connects to what, where information goes, what a person checks before anything leaves, and what is out of scope. You approve it before we build.
- Build. In your own accounts, using the tools you already pay for where they can do the job, such as the automation built into your CRM or office suite. Any new tool or paid service is named in the quote first.
- Test. First on made-up or non-sensitive examples, then on normal cases and the awkward ones. You see the results and sign off before it goes live.
- Handover. Plain-language documentation: what it does, where it lives, who owns it, and how to switch it off. Admin access stays with you.
- Training. The people who will use it learn how it works, what to check every time, and what to do when the output is wrong.
Security and data handling
- Business accounts your organization controls, never personal ones
- Each connection gets only the access the task needs
- We check the AI provider’s data settings, such as retention and model training, and show you before you approve
- Your AI use policy decides what information can go in
- Passwords and keys stay in your systems’ own settings, not in documents or email
- A documented way to switch it off and remove access
No AI use policy yet?
Then that comes first. Connecting AI to company information without agreed rules moves the risk around rather than removing it. The AI security work covers the policy, the approved-tool list and the account settings to match.
See AI securityGOOD QUESTIONS. STRAIGHT ANSWERS.
Integration questions
Still have something on your mind?
Talk to a real personDo we need an assessment first?
Usually, yes. Most integration work follows an AI Readiness Assessment or a consulting engagement, because that is where we learn your tools, your data rules and which task is worth connecting. If you have already done that groundwork, tell us on the Fit Call and we’ll say honestly whether you can skip ahead.
How is it priced?
Per project. After discovery you get a written quote, and no work starts until you approve it. What moves the price: how many tools are connected, what information is involved, how many review steps are needed, and how much testing and training it takes. Any ongoing licence or usage fees for third-party tools are yours, and we name them in the quote.
Which tools do you work with?
We start with what you already pay for, such as Microsoft 365, Google Workspace, and CRM or helpdesk tools that offer a documented way to connect. If a tool can’t be connected safely, we’ll tell you rather than work around it.
Who owns what you build?
You do. It is set up in your own accounts, documented, and your team keeps admin access. You can switch it off or hand it to someone else at any time.
What happens when a tool changes or something stops working?
The documentation tells your team how to pause it and who owns it. If you want us to stay on hand after handover, that is agreed and priced in the quote. It is not assumed.
Are you a software agency?
No. We connect AI into the tools and workflows you already use. We don’t build standalone apps, customer-facing products or software from scratch. If that is what you need, we’ll say so and suggest you talk to a developer or agency.
Will this save us a set number of hours?
We don’t promise that. Before we build, we agree one or two things you can track, such as how long the task takes before and after. Then you decide whether it was worth it.
A CLEAR NEXT STEP STARTS HERE
Talk through one task worth connecting.
Bring the task and the tools involved. We’ll tell you honestly whether an integration makes sense, or whether training, an assessment or a simpler fix should come first.
Free 30-minute call with our founder · Video call, camera optional