Scoped in writing. Governed by tier. Yours on exit.
Every Agentisk system is built the same way. What it does is written down before we build. What it may decide is agreed before it runs. And what it produces belongs to your firm from day one. This page is the method, in full, because a system you cannot inspect is a system you should not buy.
You will know what it does, what it never does, and exactly what leaving looks like, before you sign anything.
One page states what the system does. The same page states what it does not.
01A written scope, first
The chasing, the checking, the logging, the reporting, named in the scope schedule before a line is built. On the same page, the things the system will never touch. No judgement calls. No client money. No advice.
02Tiers agreed, then built
Every automated step is assigned to a tier before the build starts, and the tier sheet is a term of the engagement. What the system may and may not decide is contract, not configuration.
03A fixed setup, then it runs
We configure the function to your process, your templates and your tone, typically inside two weeks. Then it runs, and we run it.
Nothing replaced. Nothing migrated. Nothing held.
01Your systems stay
The build runs alongside your case system and your existing checks. Work arrives by email and secure upload and leaves by export. No rip out, no retraining your office, no migration weekend.
02Your suppliers stay yours
Identity and screening checks remain with the provider your firm chooses and contracts. We work with the outcome of a check. We never sell you the check.
03Your record from day one
Everything the system does feeds the record we will produce for you each month. It is yours while we work together, and it leaves with you if we part.
Written for the person who has to sign it off.
01UK and EU hosting
Every engagement runs under a data processing agreement written for a regulated reader, with every sub processor named to you before anything runs. Nothing is added silently.
02Your client data trains nothing
It is processed to run your workflow and for no other purpose.
03Named access
The people who can touch your build are named to you, and access ends when you say it ends.
The exit is designed before the entrance.
01Monthly after setup
The retainer renews because the monthly report earns it, not because a term traps you.
02Handover, not hostage
On exit, your data and your record are exported and handed over. What we built to serve your firm does not get to hold your files.
Three refusals, in every engagement, at any price.
Every product. Every client. No exceptions.
-
01
A system that makes a regulatory judgement
Decisions your firm cannot delegate are presented to your named person with the inputs assembled and the field empty. The system never generates, suggests, scores or ranks the answer, and never drafts the reasoning.
-
02
Anything that touches client money
Invoicing, chasing and cash visibility, yes. Holding, moving or reconciling client funds, never.
-
03
A system we then assess
We never assess what we build, and we never make the judgement we automate. Independence is the point, not a policy.
If a request would cross one of these lines, we decline the work. That is the method holding, in front of you, before you are a client.
Six questions inside the booking. Two answer them all, four are yours to skip.
We build to take cost and time out of the work your firm cannot bill for. The first two decide what we show you. The rest sharpen it, and anything you would rather keep for the call, keep for the call. If the answers tell us we are the wrong fit, we will say so and you keep the thirty minutes.
01Which job eats the most time nobody bills for
Chasing documents to open a new file, keeping an open file current, or getting invoices paid. This one picks what we show you.
02What does that job currently run on
A case management system, email and spreadsheets, or a mix of both. This one decides how we show it running alongside what you already have.
03Roughly how many new client files do you open in a month
A band is enough, under ten, ten to thirty, or more. It sizes the hours at stake, and if you would rather keep your numbers for the call, leave it blank.
04Who does that work today
One of the people who bill, an assistant, a shared inbox, or nobody in particular.
05When a client stops replying, or a document never arrives, how do you find out
Someone notices, a spreadsheet flags it, or it surfaces when the file is next opened. This is usually where the hours are hiding.
06Who else, if anyone, should be in the room
Add them as a guest when you book, or forward the invitation after. The person who does the work sees what a principal never sees.
The six above sit inside the booking form, so nothing is asked twice. Thirty minutes, and we show you your own admin running.