Role cards

This is what you hire from.

Every GRABS worker is proposed on one page: the Role Card. Read it the way you would read a candidate, but without the fiction of a CV. No invented experience, no borrowed metrics. Six parts, all in the language of the job, including the two most CVs leave out: exactly what it is permitted to touch, and exactly what it needs from you.

The flagship hire

The first number we chase is debtor days.

The team it ships with →

Role Card

SMEs

Credit Controller

Authority A1 to A2 within caps

Runs your sales ledger to ground: reminders, statements and a polite escalation ladder until the cash is in.

Ships with the SME backbone

Knowledge

What it knows. Yours, from the vault, not a model's general recollection.

Your payment terms, and each customer's paying history
The difference between a slow payer and a genuine dispute
When a written chase should become a phone call

Skills

What it can do, written as tasks a manager would recognise.

Drafts firm, on-brand reminders and statements
Sequences an escalation ladder that stays professional
Reconciles what has been paid against what is owed
Separates disputes from delays and routes them to a person

Behaviours

How it conducts itself when the work is ambiguous.

Persistent without ever being rude
Never lets an invoice age in silence
Escalates the judgement calls rather than guessing

Tools

What it is permitted to use, and nothing beyond that.

Your sales ledger, read only
Email, through its own address and your approval queue
Your reminder and statement templates

Authority

How far it can go before it must ask. Enforced in code, not by instruction.

A1 to A2 within caps

Works the ledger freely, releases through an approval queue, hard limits enforced in code.

Co-factors

What the role needs from you for it to work at all. Stated up front.

A named approver who clears the queue
Read access to the ledger
Your payment terms, written down once

Debtor days is a number every owner already tracks, the chase is work nobody wants, and the ladder never sleeps. It is the clearest first hire in the catalogue, which is why it leads it.

The catalogue.

One flagship role per vertical. Open any card to read it in full. Every role ships inside a team, with strategy and governance included as standard.

Operations Accountancies

Records Chaser

The January saver: chases every client document ahead of every deadline, so compliance season stops being a panic.

Role Card

Accountancies

Records Chaser

Authority A1 to A2 within caps

The January saver: chases every client document ahead of every deadline, so compliance season stops being a panic.

Ships with the Practice team

Knowledge

What it knows. Yours, from the vault, not a model's general recollection.

Which records each entity owes, and by when
The statutory calendar across the whole client book
Who actually holds the paperwork inside each client

Skills

What it can do, written as tasks a manager would recognise.

Builds the chase list against every deadline
Sends escalating, on-brand reminders that get a response
Tracks what is in and what is still outstanding
Flags the clients who will not respond, early

Behaviours

How it conducts itself when the work is ambiguous.

Relentless about lead time, never the last minute
Never lets a deadline arrive with records missing
Hands the partner a clean status, not a surprise

Tools

What it is permitted to use, and nothing beyond that.

Your practice management system, read only
Email, through its own address and your approval queue
The statutory calendar and your chase templates

Authority

How far it can go before it must ask. Enforced in code, not by instruction.

A1 to A2 within caps

Chases freely within limits; anything client-facing can be set to approval-first.

Co-factors

What the role needs from you for it to work at all. Stated up front.

A partner or manager who owns escalations
The client list with contacts, current
Access to the deadlines register

Intelligence Recruitment

Screener

Matches CVs to the spec with written reasoning, screened with occupational-psychology rigour. Humans decide.

Role Card

Recruitment

Screener

Authority A0 / A1

Matches CVs to the spec with written reasoning, screened with occupational-psychology rigour. Humans decide.

Ships with the Desk team

Knowledge

What it knows. Yours, from the vault, not a model's general recollection.

The role's defined criteria, agreed before screening starts
The difference between a hard requirement and a nice-to-have
What adverse impact looks like, and how to watch for it

Skills

What it can do, written as tasks a manager would recognise.

Maps each candidate against the agreed criteria
Writes the reasoning behind every shortlist decision
Monitors the shortlist for adverse impact
Surfaces the borderline candidates for a human to weigh

Behaviours

How it conducts itself when the work is ambiguous.

Assesses against defined criteria, never a hunch
Shows its working on every single decision
Defers the hiring call to a person, always

Tools

What it is permitted to use, and nothing beyond that.

Your ATS or CV store, read only
The agreed criteria sheet for the role
A scoring sheet it fills in, never sends

Authority

How far it can go before it must ask. Enforced in code, not by instruction.

A0 / A1

Supervised to approved-output. A recruiter makes every decision; the worker only reasons.

Co-factors

What the role needs from you for it to work at all. Stated up front.

Criteria agreed in writing before screening starts
A recruiter who owns every decision
Access to the role spec and the CV pool

Operations Law

Bundler

Turns a box of documents into a paginated bundle, a chronology and an index, ready for the fee-earner.

Role Card

Law

Bundler

Authority A1

Turns a box of documents into a paginated bundle, a chronology and an index, ready for the fee-earner.

Ships with the Fee-Earner Support team

Knowledge

What it knows. Yours, from the vault, not a model's general recollection.

Bundle conventions and pagination expectations
What belongs in a chronology, and in what order
The structure a court or counsel expects to receive

Skills

What it can do, written as tasks a manager would recognise.

Collates and de-duplicates the documents
Builds an accurate chronology from the papers
Paginates and indexes to a consistent standard
Produces a bundle a fee-earner can use without rework

Behaviours

How it conducts itself when the work is ambiguous.

Meticulous about order and completeness
Never invents a document or a date
Flags gaps plainly rather than papering over them

Tools

What it is permitted to use, and nothing beyond that.

The matter's document store, read only
Your bundle format and pagination standard
A working area of its own, never the master file

Authority

How far it can go before it must ask. Enforced in code, not by instruction.

Works the bundle freely; output is reviewed before it leaves the firm.

Co-factors

What the role needs from you for it to work at all. Stated up front.

A fee-earner who reviews before anything leaves
Access to the matter documents
The court or counsel requirements for the bundle

Revenue Financial services

Renewals Chaser

Works the renewal book so nothing lapses silently, and the adviser keeps the client.

Role Card

Financial services

Renewals Chaser

Authority A1

Works the renewal book so nothing lapses silently, and the adviser keeps the client.

Ships with the Adviser Support team

Knowledge

What it knows. Yours, from the vault, not a model's general recollection.

The renewal calendar across the whole book
Which clients are at risk of lapsing, and why
The adviser's voice and the firm's process

Skills

What it can do, written as tasks a manager would recognise.

Tracks every renewal date without exception
Drafts timely, on-brand outreach for the adviser
Flags at-risk clients before they go quiet
Keeps the book moving without nagging

Behaviours

How it conducts itself when the work is ambiguous.

Never lets a renewal slip unnoticed
Respects the adviser's relationship with the client
Leaves the advice, and the signature, to the adviser

Tools

What it is permitted to use, and nothing beyond that.

The renewals book, read only
Email drafts in the adviser's process, released through the queue
The firm's templates and approved wording

Authority

How far it can go before it must ask. Enforced in code, not by instruction.

No regulated advice, ever. The worker chases and drafts; the adviser advises and signs.

Co-factors

What the role needs from you for it to work at all. Stated up front.

An adviser who owns every client conversation
The renewal calendar, current and complete
The firm's compliance wording, signed off

Operations Banks

KYC Preparer

Assembles the KYC file, runs the list screening and drafts the summary, ready for a human to decide.

Role Card

Banks

KYC Preparer

Authority A0 / A1

Assembles the KYC file, runs the list screening and drafts the summary, ready for a human to decide.

Ships with the Back Office team

Knowledge

What it knows. Yours, from the vault, not a model's general recollection.

What a complete KYC file must contain
The screening lists, and what a hit actually means
The bank's risk policy and its thresholds

Skills

What it can do, written as tasks a manager would recognise.

Gathers and orders the file evidence
Runs list screening and records the result
Drafts the summary for a human reviewer
Logs every step so the file is audit-ready

Behaviours

How it conducts itself when the work is ambiguous.

Never makes the risk decision, only prepares it
Leaves a complete, attributable audit trail
Flags anything ambiguous up the line

Tools

What it is permitted to use, and nothing beyond that.

The onboarding case file, scoped to the case
The screening lists the bank already licenses
A file checklist it completes, never approves

Authority

How far it can go before it must ask. Enforced in code, not by instruction.

A0 / A1

Supervised to approved-output. A human decides and signs every outcome.

Co-factors

What the role needs from you for it to work at all. Stated up front.

A reviewer who decides and signs every outcome
Access to the case documents
The bank's risk policy, in writing

Operations Retail and e-commerce

Returns Triage

Categorises every return and drafts the resolution inside policy, so the public backlog clears fast.

Role Card

Retail and e-commerce

Returns Triage

Authority A1

Categorises every return and drafts the resolution inside policy, so the public backlog clears fast.

Ships with the Shopfront team

Knowledge

What it knows. Yours, from the vault, not a model's general recollection.

Your returns policy, and exactly where its edges are
What is a restock, a refund, or a reject
Your brand tone, the one customers see in public

Skills

What it can do, written as tasks a manager would recognise.

Categorises every RMA accurately
Drafts policy-compliant resolutions
Routes the exceptions to a person
Answers in your voice, even under volume

Behaviours

How it conducts itself when the work is ambiguous.

Stays inside policy without being asked twice
Escalates the edge cases instead of forcing them
Keeps the tone on-brand under pressure

Tools

What it is permitted to use, and nothing beyond that.

Your returns queue and order history, read only
Reply drafts in your voice, released through the queue
Your returns policy, encoded with its edges

Authority

How far it can go before it must ask. Enforced in code, not by instruction.

Drafts and categorises freely; resolutions release through an approval queue.

Co-factors

What the role needs from you for it to work at all. Stated up front.

A named person for the exceptions
The returns policy, written down with its limits
Access to the RMA and order systems

Governance Groups and family offices

Programme Office seat

One accountable view across every team and entity: the rollup, the registers and the concurrency discipline.

Role Card

Groups and family offices

Programme Office seat

Authority A1

One accountable view across every team and entity: the rollup, the registers and the concurrency discipline.

Ships with the Programme Office

Knowledge

What it knows. Yours, from the vault, not a model's general recollection.

Every team's status, owner and wave
The registers: decisions, risks and experiments
Where the concurrency limits bite, and why

Skills

What it can do, written as tasks a manager would recognise.

Rolls up a portfolio report every week
Keeps the registers current, not stale
Enforces the concurrency rules before they break
Gives one accountable view across the group

Behaviours

How it conducts itself when the work is ambiguous.

Nothing resolves in conversation and dies there
Reads only its owner's vaults, never across boundaries
Surfaces risk early, while it is still cheap

Tools

What it is permitted to use, and nothing beyond that.

Each team's status and registers, read only
The rollup format the owner has agreed
The registers: decisions, risks, experiments

Authority

How far it can go before it must ask. Enforced in code, not by instruction.

Reads across one owner's teams only. No instance ever reads across client boundaries.

Co-factors

What the role needs from you for it to work at all. Stated up front.

An owner who reads the weekly rollup and acts on it
Access to each team's status, granted per team
An agreed definition of what counts as a risk

The card for your process does not exist yet.

These are the flagship roles. Yours is written from your process, which is what the diagnostic is for: one week, and you keep the card whatever you decide.

Book a diagnostic Browse the teams