Governed AI and Enhancement for the software you already run · No migration · Live this afternoon
Switching software costs a year and a fortune, and the new system starts at zero. Your tools don’t need replacing — they need to talk to each other. Sallyport makes the stack you already run answerable by anyone who should be asking, and automatic where the work repeats — with your sign-off exactly where you put one.
For the owner
You shouldn’t have to book a call with your own bookkeeper to know how your own company is doing. Ask like you’d ask a colleague — the answer comes live from the tools you already run. Pick a question.
Her answer, her rights — the gate applies to the owner too. No exports, no waiting for Thursday’s report, no bothering anyone.
The cost of switching
A migration is priced as licences. It’s paid in everything else — and the biggest line never makes the quote.
| New licences, year oneboth systems run in parallel during cutover | € 48.000 |
| Data migration & cleanup3 systems, 9 years of records | € 36.000 |
| Retraining, 24 staffincl. the muscle memory nobody budgets | € 22.000 |
| Consultancy & integration rebuildsevery link your old stack already had | € 54.000 |
| Productivity dip, months 1–6 | priced by nobody |
| Total | € 160.000 + |
Migration budget. Sallyport connects to what’s there. Nothing is exported, converted, or re-entered.
Tools replaced. Your accounting, your projects, your CRM stay exactly where your team’s hands already know them.
To first answer. Connect a system, assign roles, and ask. The data was ready for years — it was only waiting for a gate.
No project. No consultants.
“One afternoon” isn’t a slogan — it’s a schedule. Here’s what the first one looks like.
What changes on Monday
Everything you were promised by the new system, delivered by the old one. Three things change, and each one is demoed live below. Click a word to jump.
One · Ask
Your company’s knowledge is locked in five admin tools and a handful of heads. Anyone who needs an answer asks for it in plain language and gets it live — from the tools you already run, within their own rights.
you keep: your data, in place
Watch a tool open up ↓
Two · Automate
Chasing invoices, filing the ones that come in, starting a project when a quote is accepted, onboarding a new colleague. Chain your tools into a playbook once, and it runs on a schedule, an event, or a sentence.
you keep: the process, written down and running
Watch playbooks run ↓
Three · Approve
Nothing here is unsupervised. A human step waits wherever you put one — and nowhere you didn’t. Every run leaves a record, so when something goes wrong you can say exactly where it broke and who approved what.
you keep: the final say
See what that’s worth ↓
One · Ask
Turn a tool on and its data becomes askable by everyone who should be asking — sales, support, finance, you — each within their own rights. No export, no copies, no consultants, and nobody learns a new system. Try the switches.
Open is not the same as exposed — every question still passes the gate. Your data never moves: Sallyport calls the tool’s own API, live, on every request, so what comes back is today’s answer and never a stale copy.
Two · Automate
Chain the tools you already run into playbooks — approvals included. Pick a process you recognise and watch it go, step by step, the way it would on a Monday morning you weren’t there for.
A playbook only ever touches what its owner may touch — a robot gets the same rights as the person who set it running, never more. No sign-off configured, no pause; one configured, it waits as long as it has to.
The catalogue
Three playbook runs above show what one looks like. Here is the rest of a real workspace — what it fires on, how many steps, and how often it has actually run.
| Playbook | Starts on | Steps | Runs | Success |
|---|---|---|---|---|
| New project intake AI-runnable | chat, button | 6 | 128 | 99% |
| Inbound invoice OCR | webhook · e-mail | 4 | 342 | 97% |
| Access review reminder | schedule · weekly | 3 | 26 | 100% |
| Contract renewal | schedule + data change | 4 | 54 | 96% |
| Signed quote → project AI-runnable | chat & button | 5 | 71 | 98% |
| Meeting scheduler AI-runnable | chat | 4 | 203 | 99% |
| Month-end invoicing | schedule · monthly | 5 | 38 | 100% |
| Expense receipt capture | webhook · photo | 4 | 156 | 95% |
| Offboarding cleanup | data change · user removed | 5 | 9 | paused |
scroll the table →
Triggers
Somebody asks for it in their own assistant, in plain language.
On the record itself, for the people who live in the dashboard.
A signed form, an inbound invoice, a form post — signature-checked, no login.
Every Monday at eight. The runs nobody remembers to do.
A deal moves to Won, an invoice goes overdue, a user is removed.
And what a run is built from
Structured · manageable · provable
Every company has a handful of things that only really work because a particular person does them a particular way. It survives on goodwill and holiday planning. A playbook is that same procedure — except it’s written down, it runs, and it leaves a receipt.
The playbook is the procedure — not a document describing one that drifted out of date two years ago. Change it in one place and it changes for everyone, from the next run.
no more “ask Melanie how we do this”
On a schedule, on an event in one of your systems, on a webhook, or from a sentence in chat. The work stops depending on who happens to be at their desk that morning.
holidays stop being a risk
Every step, every result and every approval is recorded. When a client asks what happened to their order, or an accountant asks who authorised something, the answer is a query — not an archaeology project.
the difference between a process you have and one you can show
Most companies are one resignation away from losing a process. This is how you stop being that company.
For your IT lead and your DPO
This is the part that usually goes wrong elsewhere. An automation runs as a service account with rights nobody audited, and it quietly becomes the widest door in the building. Sallyport doesn’t have one.
If Thomas can’t see cost price, neither can his playbooks. A run started by the clock or an inbound webhook has nobody behind it, so it runs as an identity you name, with rights you set — never as a superuser, and never wider than the job needs.
Approvals are steps, not suggestions. The run stops and waits, and the decision is logged with a name against it.
Automated work is audited exactly like a person’s — so when something runs wrong at 03:00 you can still say what happened and who approved it.
Studio Vandaag · creative agency · 24 staff
Their team was already pasting client data into ChatGPT. In five days they connected Gripp through Sallyport, wrote eight filter rules, and handed their accountant a weekly report instead of a shrug.
To full rollout. From shadow AI to a signed-off deployment, without a project plan.
Filter rules live. Written by the people who knew what shouldn’t leave, not by consultants.
Of AI calls audited. Every question anyone’s assistant asked, on one page.
The part your IT lead will ask about
Your team is already using AI on company data — in a browser tab, on their own account, with no record. The version on this page is the one you can see. That is not a feature we sell separately; it is the only reason any of the above is safe to switch on.
Everyone gets answers from their own slice of the business, never yours.
Your DPO marks a field once; the gate withholds it everywhere, forever.
Who asked, what came back, which rule held what — in a log nobody can quietly edit.
Hosted in the EU, nothing trained on, and you can take your keys and go.
A playbook waits for a human exactly where you said so — and nowhere you didn’t.
More cases
One playbook run hiring a colleague, and six people getting answers they used to have to ask someone for.
Onboard Lisa de Boer, starting next Monday.
Running · 4 of 7gripp + moneybird + mail · sign-off by Julia · rest runs Mon 08:00
Which payments from last week are still unmatched in Exact?
Allowed · finance scopeexact.journals.list · 7 rows · full ledger access, her role’s job
What did De Groot Media order from us last quarter?
Allowed · read-onlygripp.projects.list · her accounts only · no financial fields
Email all my clients the new-year discount offer.
Routed · needs sign-offbulk send → approval from Melanie (manager) · drafts held at the gate
Reclassify ‘date of birth’ as personal data on every connector.
Applied · gate-wideone classification → enforced on every future call, all tools
Show every AI call that touched personal data this month.
Allowed · audit scopeaudit.log.query · read-only role · the reason the Auditor role exists
Export the whole customer database to a spreadsheet.
Refused · bulk exportpolicy: data minimisation · logged & visible to Hannah (DPO)
Studio Vandaag · 24 staff · Utrecht
“We were told AI meant replacing all three systems. We kept all three — and got the AI layer anyway.”
Free trial · No migration · EU-hosted
Connect your first system this afternoon. If it’s not for you, disconnect — nothing moved, so there’s nothing to move back.