The complete solution · Core 3
Tailored automation on our base infrastructureMap. Score. Rank. Build in order.
The fastest route to value.
Value in weeks, not at the end of a project. Each automation pays for the next.
3 kinds of process, as people actually do them.
We sit with each department and write the work down. Who receives what, what is checked, who signs, where it is filed.
Dynamic processes
The daily activities people improvise. Different every time, depending on the case.
Background automation
The repetitive processes. Document processing, onboarding, compliance, monitoring.
Front-office client life cycle
The client's own journey. Identification, digital signature, engagement, upsell and cross-sell.
Where a process needs a qualified signature, Clerk OS uses a qualified trust service provider. Signatures on the apps page →
What Clerk OS covers out of the box, and what it does not.
Every mapped process is held against the out-of-the-box coverage. You pay for building only what is specific to you.
Every process of every department. Inputs, checks, approvals, outputs.
50+ automations of daily employee activities. More than half of the daily back-office processes.
The processes specific to the institution. Its systems, its forms, its decisions, its clients' journey.
Each uncovered process goes to step 3, with its owner, its volume and the systems it touches.
Value against complexity. The low-hanging fruit first.
- Value. Hours today, people, frequency, the cost of a mistake, what the client feels.
- Complexity. Systems touched, data needed, approvals, exceptions.
- Rank by low-hanging fruit. The least complex with the most value first.
- Draw the line where effort would exceed value. Above it is built. Below it is recorded.
The ranking is the delivery plan. Agreed in writing, with the price, before any work.
| Process | Value | Complexity | Order | Why |
|---|---|---|---|---|
| Incoming filings read against the rulebook, findings drafted | 5 | 2 | 1 | Highest hours. One document source. The rules already in a pack. |
| Onboarding pack classified and screened, review queue prepared | 4 | 2 | 2 | Daily volume. Clear checklist. Evidence per item. |
| Monthly supervisory report assembled from the ledgers | 4 | 3 | 3 | High value. Needs 2 system connections first. |
| Client signature and consent on the client's phone | 3 | 2 | 4 | Quick to build on Clerk Sign. Value grows with volume. |
| Committee minutes into tracked decisions and tasks | 2 | 1 | 5 | Mostly covered out of the box. Done in passing. |
| Legacy archive migration with re-keying | 2 | 5 | — | Below the line. Recorded, not built. |
A case handler's day, before and after.
- 08:30Sorts 40 messages by hand. Finds the 6 that belong to open cases.
- 09:30Pulls documents from 3 systems. Re-keys the party data into the template.
- 11:00Reads the filing. Checks the rules from memory and a PDF. Writes the findings from scratch.
- 14:00Drafts the letter. Hunts for the last template. Asks which numbering applies.
- 16:30Chases 2 signatures by email. Updates the register by hand. The audit trail is the mailbox.
- 08:30The inbox is sorted. The 6 case messages are filed, replies drafted, waiting for approval.
- 09:00The case file is assembled from mail, documents and the core record.
- 09:30The filing was read against the rule pack overnight. The handler reviews the findings.
- 11:00The letter is drafted in the current template. The handler edits, approves, sends.
- 11:30Signatures requested from the case. Register updated by the agent. Every step sealed. The afternoon is for the hard cases.
The day is qualitative. It shows what moves from the handler to the agent, not a measured saving. Measured results come from your pilot.
Custom agentic upgrades on the OS, one by one.
Each process in the ranking becomes an agent in Clerk OS. Your roles, your approval chains, your templates. Then the next one.
The process in plain language, with the team that does it. Inputs, checks, approvals, outputs, exceptions.
A specialised agent on the base infrastructure. It reads from and writes back to your systems.
Against the acceptance criteria in the scope. The department signs off.
The agent joins the console. The next process starts. Value arrives in weeks.
Inside your systems, on your premises, by one accountable team.
The agents work inside your workflows, not beside them.
Integration
- ERP, core banking, policy and fund administration
- Document stores and archives
- Identity, mail and calendar
- Read from and write back to where your records are
Machines that run, not a pilot that ends.
Implementation
- Nodes installed and sized to your load. Air-gapped if required
- Clerk OS fitted to your processes, roles and templates
- Your fine-tuned model on your nodes
- Teams trained on site, in every department
One team for the nodes, the system and the model.
Support
- On site and by secure channel
- Model retrained, agents extended as you change
- Updates as files you apply yourself
- One on-premises supplier in your register. Your governance remains yours
Adoption is work too. We stay for it.
An automation nobody uses returns nothing. We work with your people until the system is theirs.
Champions
The most enthusiastic adopter in each department, trained.
One person per department knows the system best. First to receive every new agent. The team learns from a colleague.
Usage quality
Monitoring of how the system is used.
Which agents run, which wait, where approvals pile up, where people route around it. Reviewed with the champions.
Continuous adaptation
Working with employees on adaptation and improvement.
Processes change. People find better ways. We keep mapping, scoring and building, under support.
In writing, with the price, before any work.
- Scope. The process map, the split, the scoring, the ranking. In writing, with the price.
- Pilot. The first process in the ranking, on your files, with acceptance criteria.
- Deploy. Nodes installed and Clerk OS fitted. Agents built in order, teams trained on site.
- Improve. Champions, usage quality, continuous adaptation. Model retrained under support.
Priced per engagement. Reference calls, architecture notes and the outbound-connection list on request.
- The model: weights, training record, held-out results
- The agents: every custom upgrade, on your infrastructure
- The integrations: to the systems you already run
- The record: the Trust Log of everything the system did
- The machines: stations, machines or nodes, in your building
Stated plainly: leaving means keeping all of it. Updates would stop. The work would not.
Own your intelligence.
Mapped with you. Built in the order that pays. Kept improving with your people.
info@finqup.com · scoped in writing · a pilot first