Your whole working day, in orbit around one surface.
OnePilot is the surface and framework. TreasuryCentral is its one shipped edition, live on SAP. Coverage figures are illustrative of category scope, not measured benchmarks; Gartner and other figures are attributed where they appear.
Applications
On SAP today, and beyond it
OnePilot is not limited to SAP, or to finance. TreasuryCentral is the one shipped edition, live on SAP today; the platform composes whatever a team works with, from wherever they have access: ERP, banking, market data, email, Teams, spreadsheets, anything with an API. One governed surface across all of it, one login and one audit trail instead of ten tabs and ten passwords.
Five more use cases already run on the platform, no card required: Intercompany Funding Request, Cash Flow & Exposure Hub, Bank Statement Generator, Credit Data Hub and ESG Data Hub.
Intercompany Funding Request LiveCash Flow & Exposure Hub LiveBank Statement Generator LiveCredit Data Hub LiveESG Data Hub POC
The Digital Co-Worker
Your team and its Digital Co-Workers
The Digital Co-Worker is a feature of OnePilot, not a separate product. It is the agent that works with your team inside a dedicated space: it drives the solution, watches every run, fixes what breaks, and brings you the decisions.
The solution executes the deterministic steps, the same result every time. The Digital Co-Worker drives every step across your systems. You keep the judgment.
An agentic team, not one bot
Specialised agents, each briefed for its part of the work.
Every app and use case has a space where your team and its Digital Co-Workers run it together: chat, alerts, fixes, orchestration. The Digital Co-Worker monitors every run where a person would, raises and records alerts, fixes data issues, and hands you the exceptions. Nothing fails in silence, and a person stays in charge. A colleague, not a black box.
Governance
Governed on SAP, end to end
A Digital Co-Worker reaches exactly what the person it works for can reach, and nothing else. The controls a regulated finance team needs are built into the surface.
Bounded autonomy
The Digital Co-Worker acts only within the permissions and limits you set. Access outside that boundary is absent, not dimmed.
Human authority
A person owns the moves that matter, and can review, override or stop the work at any point.
Four-eyes and segregation of duties
Whatever initiates a step never approves it. Approvals and separation of duties sit on the actions that need them.
Robust and fail-safe
Tested before it runs, it behaves predictably, and safe-stops or rolls back on error.
Traceable and explainable
Every action and data change is logged: who, what, when, why. Traceable and explainable, end to end.
Monitored by exception
Outputs are watched in real time. Anomalies go to a person; the rest just runs.
Governed to EU AI Act principles · 360° audit trail · ISO 27001 & SOC 1 Type II · people own the moves that matter.
It orchestrates; it does not become the system of record. The book of record stays in SAP, execution on the trading platform, market data through the hub.
The problem
Why does a treasurer's day become tab management?
Because the work is scattered across systems that do not talk to each other: SAP, two bank portals, a trading screen, market data, email and a spreadsheet.
So the numbers get re-keyed between them, and the day goes to moving data instead of using it. OnePilot puts the data in one governed place, so the day shifts back to using it: deciding, not re-typing.
~1,200
app and site switches the average worker makes in a day.
Harvard Business Review, 2022
up to 40%
of productive time lost to switching between disconnected apps.
American Psychological Association
~340
SaaS apps in a large enterprise, so any single-suite answer is partial.
Productiv, State of SaaS, 2024
Answers
Questions finance teams ask
Direct answers on what OnePilot and TreasuryCentral are, how the applications work on SAP, and how this compares to the tools you already know.
What it is
OnePilot is Brisken's governed, no-code platform for running a team's work on one surface. Each user composes the apps, data and spaces their work needs, and permissioned Digital Co-Workers do the repetitive work across all of it.
It is a framework in three layers: the framework IT sets up once, the spaces a user builds in plain language, and the Digital Co-Workers that act within that user's permissions. It connects to whatever a team uses, from ERP and banking to market data, email and spreadsheets; SAP is one example. TreasuryCentral, live on SAP today, is its first scoped edition.
TreasuryCentral is the one shipped edition of OnePilot, live on SAP today. It puts the treasurer's whole day on one surface: cash, FX, market data, trades, bank files and remittances, governed end to end.
Each task moves from a string of logins to one glance: cash reconciled overnight by exception, payment runs staged for four-eye release, the board pack drafted to your template.
The applications
BST is OnePilot's FX and trade-execution application, live on SAP. It brings exposure, market data and execution onto one surface and logs every action back into SAP under four-eye control.
The Market Data Hub brings live market data into SAP in the context where it is used, so a rate sits next to the position it affects rather than in a separate terminal.
The Remittance Advice Gate has an agent read incoming remittances and structure them into SAP cash application, removing the manual re-keying. The agent prepares the entries; a person approves them.
SAP, governance and how it compares
No. OnePilot orchestrates on top of SAP. The book of record stays in SAP, execution on the trading platform, and market data through the hub.
Each of those covers a slice: search finds across tools, suite assistants help inside one suite, and agent platforms act beside the old tools. OnePilot is the surface the user actually works from, reaching into ERP, banking and market data, with agents carrying the user's exact permissions across every source.
It orchestrates rather than becoming the system of record, and it can consume what point tools build rather than adding another tab to the estate.
Start with one team and the workflow that matters most to them, set up as a single scoped space, then add apps and spaces as the work grows. TreasuryCentral, the treasury edition live on SAP, is one example of where a first edition starts; the same path works for any team and the systems they use.
Contact the team to scope a first space and see the surface run a real job end to end.
See it running on SAP
TreasuryCentral is live with customers on SAP today. Watch the surface run a money-critical job end to end, or reach the team to arrange a walkthrough.
The day is spent moving between disconnected apps, re-keying the same numbers, and losing the thread. The market's two answers, faster search and one more point tool, leave the other ten apps exactly where they were.
The cost, in numbers
~1,200
app and site switches the average worker makes in a day.
Harvard Business Review, 2022
up to 40%
of productive time lost to switching between disconnected apps.
American Psychological Association
~340
SaaS apps running in a large enterprise; any single-suite answer is partial.
OnePilot is not a fixed product; it is a framework in three layers. The framework is set up once; the spaces and the Digital Co-Workers are yours, changed in plain language.
1
Brisken and IT, once
The framework
Connectivity, permissions, security and boundaries. Set up once, it makes the surface safe to build on and keeps every space inside the same governed perimeter.
2
You, continuously, in plain language
Your spaces
A canvas of widgets that pull in whatever you work with, from wherever you have access. Build as many as the work needs: a day's flow, a recurring job, an occasional task. No build queue, no IT ticket.
3
You direct; the framework constrains
The Digital Co-Workers
Digital Co-Workers see and act across everything in your spaces, strictly within your permissions. You set the rules and approve the exceptions; the Digital Co-Worker does the busywork, by exception, underneath.
Composed, not coded
Integration moves from the IT ticket to a plain-language ask. Describe the space you want, for example "build me a morning cash space", and the widgets compose onto the canvas, each pulling live from a connected source: cash position, FX exposure, bank files, email and Teams approvals, the board pack, market data. The same surface builds a close space, a deal space, an operations space.
The framework constrains; the user directs. A Digital Co-Worker carries the same access limits as the person it works for, with the six controls a regulated finance team needs to standardize on it.
Bounded autonomy
The Digital Co-Worker acts only within the permissions and limits you set. Access outside that boundary is absent, not dimmed.
Human authority
A person owns the moves that matter, and can review, override or stop the work at any point.
Four-eyes and segregation of duties
Whatever initiates a step never approves it. Approvals and separation of duties sit on the actions that need them.
Robust and fail-safe
Tested before it runs, it behaves predictably, and safe-stops or rolls back on error.
Traceable and explainable
Every action and data change is logged: who, what, when, why. Traceable and explainable, end to end.
Monitored by exception
Outputs are watched in real time. Anomalies go to a person; the rest just runs.
Certified and governed
Governed to EU AI Act principles · 360° audit trail · ISO 27001 & SOC 1 Type II · people own the moves that matter.
Most software makes the user adapt to the application. OnePilot inverts it: the surface adapts to the user, and the AI lives inside that surface with the same reach and limits as the person.
The inversion
Dimension
Application-centric
User-centric
Who adapts
The user bends to the application
The surface adapts to the user
Where work happens
Across ten disconnected apps
On one composed surface
Who integrates
IT, by ticket and project
The user, in plain language
What the AI does
Bolted onto one function at a time
Acts across every space, by exception
Coverage
One suite, one slice of the day
ERP, banking, market data, mail, Teams
The market covers slices; OnePilot covers the surface
Coverage shows each category's scope of the working day. The figures are illustrative of category scope, not measured benchmarks.
Search and context layersGlean22%
Gives
Permission-aware search; finds things faster across your tools.
Leaves
The ten tools stay in place. It finds; it does not become the place you work or execute.
Ecosystem-bound assistantsM365 Copilot, Gemini for Workspace38%
Gives
Deep AI inside one suite, where most desk work already happens.
Leaves
Shallow and ungoverned the moment work crosses out of the suite into ERP, banking or market data.
Agent platformsAgentforce, Copilot Studio44%
Gives
Agents that act, not just answer.
Leaves
The agents sit beside the old tools; there is no single workspace the user works from.
Workspace and app buildersNotion, Airtable, Taskade40%
Gives
Light composable spaces; easy to assemble.
Leaves
Little deep ERP, treasury or market-data integration, and no permissioned agents across live systems.
AI app and auto-buildersLovable, Base44, Replit, v0, Bolt30%
Gives
Generate apps from a prompt, fast.
Leaves
Point solutions with low governance and no unified surface. They add to the estate; OnePilot can consume what they build.
OnePilotThe surface that closes the ring100%
Gives
A composable, user-built surface that becomes the one place you work, reaches into ERP, banking and market data, and carries agents with your exact permissions across every source.
Holds the line
It orchestrates; it does not become the system of record. The book of record stays in SAP, execution on the trading platform, market data through the hub.
TreasuryCentral is OnePilot scoped to the treasurer, live on SAP today. It grounds the framework in a real, money-critical job: each task moves from a string of logins to one glance.
The treasurer's day, before and on OnePilot
07:30Morning cash position
TodayLog in to two bank portals and SAP, export, reconcile balances by hand in a spreadsheet.
On OnePilotCash across banks and SAP, reconciled overnight by exception, on the surface when you sit down.
DailyPayment runs, without the keying
TodayRemittances retyped into cash application, payments keyed and chased across systems.
On OnePilotThe agent reads remittances, structures them into SAP, and stages the run; you release under four-eye.
Month-endThe board pack, drafted
TodayPull figures from five places, paste into slides, format to the template, version by email.
On OnePilotThe agent pulls the figures and drafts the pack to your template; you review and adjust.
In the momentFX execution in context
TodaySwitch to the trading platform, check exposure in another tab, execute, log it back by hand.
On OnePilotExposure, market data and execution on the same surface, the action logged and governed automatically.
One surface, one conversation, work done
01Open a space
The review space, with the figures and the template already in view.
02The agent pulls the figures
Cash, exposure and market data, current and reconciled, from the connected sources.
03It builds the deck
Drafted against your template, ready to review and adjust.
04It drafts and sends
The review email written for the room; it goes on your word.
Scope it to a role, don't rebuild it
Live on SAP todayTreasuryCentral
The treasurer's day in one workspace: cash, FX, market data, trades, bank files and remittances, on SAP, governed end to end. Live with customers now.
IllustrationFinance and controlling
A close-and-reconcile space: the numbers and the surrounding work on one surface.
IllustrationSales and account management
A deal space: pipeline, account history and the next action together.
IllustrationOperations and shared services
A request-handling space, the intake and the systems in one place.
IllustrationExecutive and cross-functional
One morning surface across functions, drafted by the agent overnight.
The four role spaces are illustrations of the pattern, not a launch list. TreasuryCentral is the one live, shipped edition.
The same surface answers a different question for each person who touches it. The relief is what makes it get used.
Today
Ten tabs, the same numbers re-keyed, the day spent moving data instead of using it.
OnePilot gives
One surface, the mundane work gone; the day shifts to judgment and the exceptions that need a person.
Today
Every change to how the team works is an IT ticket and a wait.
OnePilot gives
Automate the team's own work in plain language, no ticket, no build queue.
Today
A backlog of integrations to build and own, and shadow tools springing up around them.
OnePilot gives
One governed framework, defined once; the breadth is composed on top without new code to maintain.
Today
Ungoverned assistants reaching across systems with unclear access.
OnePilot gives
Digital Co-Workers that access exactly what the user can, no more, with four-eye, segregation of duties and a full audit trail.
Today
AI licences signed and then barely used; spend without adoption.
OnePilot gives
Adoption, because people want to use it. A platform that gets used renews and expands.
Why this matters
Software gets bought and not used. The constraint on enterprise AI is adoption, not capability. OnePilot sells relief, the mundane work taken off people and put in one governed place, which is what makes a platform get used.
$2.5T
forecast worldwide AI spending in 2026.
Gartner
30%+
of generative-AI projects abandoned after the proof-of-concept stage.
Gartner
40%+
of agentic-AI projects expected to be cancelled by 2027.
Gartner
OnePilot is Brisken's governed, no-code platform for running your work in SAP. One surface where you compose the apps and data your work needs, and permissioned Digital Co-Workers do the repetitive work across all of it. Everything on this map orbits it.
One surface, not ten tabs
Instead of moving between SAP, two bank portals, a trading screen, market data, email and a spreadsheet, the work lives on one surface you assemble yourself. The numbers stop being re-keyed between systems, and the day shifts from moving data to using it.
Framework, spaces, Digital Co-Workers
1
Brisken and IT, once
The framework
Connectivity, permissions, security and boundaries, set up once. Every space stays inside the same governed perimeter.
2
You, in plain language
Your spaces
Compose the widgets and data your work needs, as many spaces as the work needs. No build queue, no ticket.
3
You direct; the framework constrains
The Digital Co-Workers
Digital Co-Workers act across your spaces, strictly within your permissions, doing the busywork by exception.
Live today
OnePilot is the framework. TreasuryCentral is its one shipped edition, live on SAP with customers now: the treasurer's whole day, cash, FX, market data, trades, bank files and remittances, on one governed surface. The other editions on this map are illustrations of the same pattern.
OnePilot composes whatever you have access to, from wherever it lives. It is not tied to SAP, or to finance. The surface reaches into the systems you already use and brings them onto one canvas, with Digital Co-Workers that carry your exact permissions across all of them.
What it reaches
SAP and other ERPsBank portals and filesMarket data: Bloomberg, LSEG, 360T, OANDA, CMETrading platformsEmail and TeamsSpreadsheetsAnything with an API
SAP is one source, not the boundary
TreasuryCentral, the shipped edition, runs on SAP today, so the first proof is in SAP treasury. The platform itself is source- and department-agnostic: the same surface composes a sales desk, an operations queue or an executive workspace from whatever those teams have access to.
Contact the team
Tell us a little about your setup and we will be in touch. TreasuryCentral is live on SAP today.