Find an internal answer
Help a colleague find the relevant policy, procedure or project detail, with a link to the source.
If the information is missing or disagrees, the question goes to its owner.
A colleague asks a question.
The answer is spread
across five places.
We build custom AI agents for research, customer questions and sales preparation. An agent can choose steps and use approved tools to complete a task. You decide what it can read, what it can do and when a person must approve.
Getting ready for a meeting or answering a customer often starts with a search: the CRM, an old email, a shared folder, someone else’s notes.
Start with one recurring task. We test it with the documents, questions and languages your team actually uses.
Help a colleague find the relevant policy, procedure or project detail, with a link to the source.
If the information is missing or disagrees, the question goes to its owner.
Bring together earlier conversations, product details and account history, then prepare a suggested reply.
Your team reviews sensitive replies and any promises to the customer.
Gather the agreed sources, organise the findings and help update a working memo.
Your team’s conclusions stay separate from the AI’s research.
These are examples of possible projects. We agree the tools, access and checks with you before building.
Here is how an internal assistant could prepare a meeting brief. It uses the information and tools you have chosen for that job.
A colleague requests a brief for a meeting.
Check which records that colleague can access.
Gather relevant account details and notes.
Show the brief with sources and open questions.
Ask for any required approval and save the agreed result.
Missing documents, conflicting information and broken connections need a clear explanation. The agent stops or asks the responsible person. It cannot give itself more access to finish the job.
Reading an email, drafting a reply and sending it are separate permissions. We agree them before connecting live tools.
We first check whether your existing software or a straightforward automation can do the job. Custom development makes sense when the task needs different steps, company information and tools that an existing solution cannot bring together.
| Task | Who stays in control |
|---|---|
| Read information | Use the records available to that person and show the sources. |
| Prepare a draft | Label it as a draft, with the facts behind it. |
| Send a message or change a record | Show what will happen and ask for approval where needed. |
| Move money or grant access | Keep outside the agent’s default job, with separate authorization and checks. |
Our investment-memo project shows AI helping with research. The support project shows the account information a useful assistant needs.
New information updates the memo’s research sections while the analysts’ own conclusions stay intact.
See the investment-memo project Related work / Customer supportA rule-based workflow brings account details and ownership into a support alert. It shows the kind of context an assistant can build on.
See the support projectWe agree what the first version should do, how to check it and who will look after it. Then we work through it with your team.
We write down one task, its users, sources, connected tools and permitted actions. The brief names what stays outside the project and which decisions need a person.
Together we choose everyday and difficult requests from your work. We agree how to judge useful answers, supporting sources, correct actions and cases the agent must pass to a person.
We build the agreed task and check results against those examples. Tests include missing information, denied access, failed tools and misleading instructions. We verify saved results in the connected system.
You receive the build, setup documentation, approval rules and test findings. We show your team how to correct or pause the agent, and agree who monitors it and what support is included.
We agree which records each role can use and what happens when a document is removed or someone’s access changes.
We identify the AI providers, connected tools and storage used for documents, conversation history and activity records.
Keep a record of proposed actions, approvals and results, with a way to pause the agent or deal with a failed step.
You own what we build from day one. We agree who manages accounts, reviews answers and watches usage costs. Provider subscriptions and ongoing support are set out separately. Changes to models, instructions or sources need testing.
If the steps are always the same, an automation may be enough. An agent can help when the next step depends on the question or the information it finds. We compare options around the job.
They should only see what their role allows. We agree and test access for each group, including what happens when permissions change.
We can build answers with source links and test whether those sources support the answer. We also check how it handles missing, conflicting or old information.
We agree that with you. Reading, drafting, sending and changing records can each have different rules. A reviewer needs to see the proposed action before approving it.
We try normal tasks, misleading documents, requests it should refuse and failed connections. Then we check what it actually did, including whether it respected access and approval rules.
We test German, French, Italian or English against the work you need it to do. The examples should reflect your team’s terminology and documents.
We explain which providers process them, where they are stored, who can access them and how long they are kept. We check the connected services as part of the same setup.
First projects start from CHF 4,800 for one agreed task. Scope depends on source quality, integrations, permitted actions, languages and testing. Before building, the proposal confirms deliverables, timing and acceptance criteria. AI usage, hosting, subscriptions and ongoing support are shown separately where needed.
You might start with phone calls, investment research or sales preparation. These roles can overlap. A sales team may also need help handling calls.
Help callers with routine questions, arrange a callback or follow up on an agreed customer task. We test the languages and handover to your team.
The outcome: The caller knows what happens next, and your team has the details.
Explore voice agents Investment teamsBring company research together, prepare memo updates and help get ready for portfolio reviews. Sources, dates and CHF/EUR figures stay easy to check.
The outcome: Analysts can begin with the findings and open questions in one place.
Explore investment agents Sales teamsPrepare account briefs, turn meeting notes into next steps and draft follow-ups in the customer’s language. Your salesperson checks the work before it goes out.
The outcome: More context for the conversation and less admin around it.
Explore sales agentsWe agree the tools, languages and actions for each project, including when a person takes over.
Bring one recurring task, the tools and information it uses, and a few real examples. We’ll discuss what an agent could deliver, what needs approval and whether an existing tool would be enough.
Book a first call