Proscendia

AI agent consultancy · built in the open

We build the
AI agents
that do the work.

Most companies have bought AI that gives advice. We build the kind that finishes the job — inside your systems, with your permissions, and with a record of everything it touched.

Book a call

What we build

Four kinds of work, one outcome

Every engagement ends the same way: something that used to need a person now runs on its own, and the person does something better.

Agents

Agents that finish the work

Not a chatbot that answers questions. An agent that reads your data, decides what to do, and writes the result back into your systems — then tells you it is done.

Automation

The weekly grind, rebuilt

The multi-step process someone on your team does by hand every week. Rebuilt as something that runs itself and only interrupts you when it genuinely needs a decision.

Integration

AI wired into what you already run

MCP servers and integrations that give an agent safe, permissioned access to your existing software. Your accounts, your access rules, no copy of your data sitting somewhere else.

Tooling

Internal tools people actually open

Desktop and command-line tools built around how your team really works, rather than another dashboard that gets bookmarked once and forgotten.

Work

Built in the open, so you can check

Two of these you can read the source of right now. You should not have to take an agency's word for whether it can build.

ClaudeGate

12 stars

TypeScript · CLI

Switches an AI coding setup between Anthropic, OpenRouter, Z.AI, Kimi K2, Novita AI and custom endpoints with a single command. No config editing.

Read the source on GitHub →

Cowork

23 connectors

Tauri · Rust · React

A desktop AI assistant carrying 50+ skills, 10 subagents and 23 MCP connectors across multiple providers, with browser automation and messaging built in.

Read the source on GitHub →

How it runs

Four steps, and you can stop after any of them

  1. 01

    A call, and an honest answer

    Thirty minutes. You walk me through the work that eats your team’s week. I tell you whether an agent is the right answer — including when it is not.

  2. 02

    One workflow, working

    A prototype on your data, doing one real job end to end. You watch it run before you commit to a build.

  3. 03

    Built to survive contact

    Permissions, audit trail, error handling, monitoring. The difference between a demo and something you can put in front of a customer.

  4. 04

    Handed over, not held hostage

    Your team runs it. You get the code, the documentation and the training — and me on call when the work changes.

A head start

You are not paying for the groundwork

The connectors, skills and orchestration your build needs already exist and already work. That is time you do not have to buy twice.

23systems already wired up — mail, files, chat, browser
50+agent skills ready to use on day one
6AI providers supported, so you are never locked to one
10agents able to work a job in parallel

Straight answers

Questions people actually ask

What is an AI agent, and how is it different from a chatbot?

An AI agent completes a task; a chatbot answers a question. A chatbot might tell you which invoices look overdue. An agent reads the invoices from your files, checks which are past terms, drafts the chase emails, sends them, and logs what it did. The difference is whether the work is finished at the end or handed back to you as a suggestion.

How much does it cost to build an AI agent?

A working pilot on your own data costs $2,400 to $4,500 and takes one to two weeks. A production build across two or three systems is typically $8,000 to $22,500 over three to six weeks, and running costs after launch are usually $50 to $450 a month. What moves the price is how many systems the agent touches and what a mistake would cost.

How long before we see something working?

You see one workflow running on your own data before you commit to a full build. The prototype stage exists precisely so you are not asked to trust a description — you watch it do the real job first, and stop there if it is not right.

Can an AI agent access our company data safely?

Yes, when it uses your existing accounts and permissions rather than a copy of your data. Agents built here connect through the Model Context Protocol using credentials your business already controls, so the agent can only reach what the account it runs as could already reach. Every read and write is logged as it happens, and you can revoke access the same way you would for an employee.

Do we have to replace our current software?

No. The agent works inside the tools you already pay for — email, file storage, calendars, chat, the browser. Replacing working software to accommodate AI is usually a sign the AI has been sold to you the wrong way round.

What happens when the agent gets something wrong?

You see it, because nothing runs in a black box. Every action is logged as it happens, agents are built with explicit approval steps for anything consequential, and work can be stopped mid-flight. The right question is not whether an agent will ever be wrong, but whether you will find out before it matters.

How is this different from Zapier, Make or n8n?

Those tools follow rules you write in advance; an agent decides what to do at the time. If your process is genuinely fixed — this trigger, always that action — a no-code automation tool is cheaper and you should use one. Agents earn their cost when the work needs judgement: reading an unstructured email, deciding which of six things it is, and handling it accordingly.

Which AI provider do you use?

Whichever suits the job, and you are never locked to one. The open-source tooling behind this agency already supports Anthropic, OpenAI-compatible endpoints, OpenRouter, Z.AI, Kimi K2 and Novita, and switching provider is a configuration change rather than a rebuild. That matters when prices and model quality move as fast as they currently do.

Who owns the code when the project ends?

You do. Engagements end with handover: the code, the documentation and training for your team, so you are not renting access to something you paid to have built.

You have no client case studies. Why should we trust you?

Because you can read the code instead of taking a reference call. ClaudeGate and Cowork are public on GitHub with their full commit history, so the engineering behind this agency can be inspected before you spend anything — which is more evidence than most agencies will give you from a logo wall.

Start here

Tell me what your team does by hand

Thirty minutes, no deck. If an agent is the wrong answer for your problem, I will say so on the call and you will have lost half an hour.

Book a call