Who it's for
One engine. Three shapes of tenant.
A person, a founder and an organisation need very different things from an agent team. What actually changes between them is not the technology — it is where the gate sits and who is standing at it.
Shape one
A person — the chief of staff
You are not short of intelligence. You are short of a second person who holds the thread while you are in a meeting: the reply you owe, the thing you promised on Tuesday, the document you keep meaning to read.
What it does
- Reads what arrives — mail, attachments, documents — and files it where you will find it, with a one-line summary rather than a wall of analysis.
- Keeps a running list of what you owe and what you are owed, and surfaces it before the deadline instead of after.
- Drafts in your voice: the follow-up, the decline, the brief. You send it.
- Answers questions about your own record — "what did I agree with them in March" — from files, not from memory.
Where the gate sits
At the outbound boundary. It drafts anything and sends nothing. Nothing goes out under your name, to anyone, without you seeing the exact words first. That single rule is what makes the rest safe to let run unattended.
Be warned about the honest limit: a personal assistant is the easiest thing to demonstrate and the hardest thing to make worth paying for. If this is all you want, a good assistant in a chat window will cover most of it for the price of a subscription. Gibreen earns its keep when the work touches a system — which is the next two shapes.
Shape two
A founder — delegating jobs, not prompts
The difference between a chat assistant and an agent team is the unit of work. You do not ask an employee to "summarise this"; you hand them the supplier reconciliation and expect it done by Thursday. That is the unit Gibreen is built around.
What a job looks like
A job is a file. It has an owner, a cadence, a plan with steps, a record of every run and a list of the questions it raised. It survives restarts, it can be handed to a different agent, and you can read it without opening the product.
✓ Good candidates
- Work that repeats on a cadence and has a right answer.
- Work that is mostly reading several systems and reconciling them.
- Work you currently do late at night because delegating it costs more than doing it.
- Work where a mistake is visible and correctable within a day.
✗ Bad candidates
- Anything where being wrong is silent — the error you would not notice for a quarter.
- Judgement that depends on relationships nobody has written down.
- Work that is genuinely novel every time. There is no pattern to learn.
- Anything you would not be willing to review for the first month.
Where the gate sits
At the money and the commitments. Read everything, draft everything, act on nothing that spends, promises or publishes. Most founders widen this after a month or two — for a specific agent, on a specific act, with a spending limit — and they widen it because they have watched it work, not because they were asked to trust it.
Shape three
An organisation — roles performed, not tools provided
This is where Gibreen is actually different, and it is the shape we build for first. An organisation does not want an AI tool. It wants a role performed: someone who chases the overdue invoices every Tuesday, someone who prepares the month-end file, someone who answers "where is that order".
A role has the things a job description has
What it is responsible for
Written in a file, in sentences, by you. Not a prompt buried in a settings panel — a charter that a new manager could read and understand.
What it may touch
Named systems, named operations. A grant it does not hold is not a rule it is asked to follow — it is a call that does not exist for it.
What it must ask about
Per act, not per agent. "May post a draft journal entry" and "may post to the ledger" are two different permissions and are held separately.
What it leaves behind
Every run, decision, question and refusal, in plain text under version control — reviewable by a person who does not have a login.
Why this matters more than it sounds
Under the oversight duties now landing in European and Gulf regulation, the artefact an auditor asks for is not a clever architecture diagram. It is evidence that a human decided — with the alternative that was considered, the recommendation that was given, and the timestamp. Most agent platforms can show you a log of what the model did. Rather fewer can show you the moment a person said no, and why.
Where the gate sits
Wherever your existing delegation of authority already puts it. This is the design principle: an agent should not have authority a person in that seat would not have. If your bookkeeper cannot approve a payment, neither can the bookkeeping agent — and that is configured once, in a file, rather than remembered by everyone.
Honestly
When Gibreen is the wrong answer
We would rather say this now than in week three of an engagement.
- You want self-serve. There is no signup button and there will not be one soon. If you want to try something this afternoon, there are good products that will let you, and we will name them on a call.
- You are a Microsoft shop that wants an agent registry. Agent governance is now a line item on a bill you already pay. Buy that. It is a better deal than anything we could build for you.
- You want a person-shaped chatbot for your customers. That is a different product category with mature vendors who price per resolution.
- Nobody in your organisation will answer a question within a day. This is the one that actually kills projects. The gate is the mechanism, and a gate nobody stands at is just a queue that grows.
Talk to us
Start with a conversation, not a signup
Gibreen is not sold from a pricing table. Tell us which system of record you run and which job is eating your week, and we will tell you honestly whether this is a fit — including when it is not.