Internal knowledge search
Search over procedures and policies, with sources and access control.
RAG systems →For operations teams
Automation and AI for operations teams.
We build the systems that keep the back office running: answers from your procedures with sources, internal requests routed to the right team, and a clear list of every automation and AI tool you run. Each system has a named owner on your team.
Who it is for
Does this sound like your team?
Good fit
- People update the same data in several tools by hand.
- Internal requests arrive in chat and email, and some get lost.
- Nobody has a full list of the automations and AI tools you pay for.
- New starters wait days for their accounts.
Not sure yet?
The Technical Diagnostic maps your systems, data and workflows in 2–3 weeks and tells you what to build first.
See the Technical Diagnostic →Examples
What we can build for operations teams
Each example links to the service that builds it.
Request triage
Internal requests triaged and routed to the right team.
AI agents →Automation and AI register
Every automation and AI tool listed with its owner, its access and its monthly run cost.
Automation & integrations →Accounts for joiners and leavers
New employee accounts and access set up across tools from one form, and removed when they leave.
Automation & integrations →Tools
Built with
- n8n (cloud and self-hosted)
- Make.com
- Airtable
- LlamaIndex
- Python
- APIs and webhooks
Proof · from the blog
We document a real RAG project in public, step by step: the series “Hey Dad, tell me how to RAG!”.
Not sure where to start?
Where to start
5 minutes · free · no sign-up
Readiness check
Ten questions about your systems, data, workflows and documents. You see where you stand and where we would start.
Start the readiness check →2–3 weeks · fixed scope
Technical Diagnostic
A review of your systems, data and workflows. You get an audit report and an engineering roadmap you can use with any team.
See the Technical Diagnostic →How every project runs
From diagnostic to a system your team owns
- 01
Technical Diagnostic
2–3 weeks: audit report and roadmap.
- 02
Build in sprints
4–6 weeks each, documented as we go.
- 03
Hand over to a named owner
Documentation, a runbook per tool and training for the person on your side who owns it.
- 04
Ongoing support, if you want it
Monitoring, fixes and small builds. We act as the second line behind your owner.
FAQ
Frequently asked questions
Not sure where to start? The Technical Diagnostic is the first step for every build.
Can internal search respect access rights?
Yes. Access control is part of the build, so people only get answers from documents they are allowed to open.
What goes into the automation register?
Each automation and AI tool, the person who owns it, what it can access and what it costs to run each month.
Can it run self-hosted in the EU?
Yes. n8n can run on your own infrastructure, so data stays where you decide.
How long does it take?
We start with the 2–3 week Technical Diagnostic. The build runs in sprints of 4–6 weeks.
Tell us what slows your team down.
A 30-minute call. We’ll tell you what we’d build first.
What happens next
- 130-min callWe look at your situation and tell you what we would build first.
- 2Technical Diagnostic2–3 weeks, fixed scope: audit report and roadmap.
- 3Build in sprints4–6 weeks each, documented and handed over.