TemplatesGet a demo →Book a meeting

Pension operations, with the working shown

13 flows for the work a fund’s operations team does every day: member questions, retirement applications, contributions that arrive late or short, and the reports the board reads. Every figure comes from your own systems and is quoted exactly, and anything that reaches a member waits for a person.

Your administration system, read-onlyYour plan documentsEvery run recorded with its steps, time and model costA person approves what reaches a member

AI Factory · Retirement application review · run 1225a real run on synthetic data · recorded Sep 11, 2026
A fileThe document
RetrieveRetrieve274 ms3 passages
AnswerAnswer3.8 s
Ask a personAsk a person
Answer shownAnswer shown1 ms
Answer shownHeld back
5 of 6 steps ran4.1 s end to end$0.009 model costDrag the canvas, or any step, to move it around.

The work, template by template

Open them in the catalogue

Each opens in the builder as a working flow. Point it at your plan documents and your administration system, and press Test.

Contributions, checked before anybody asks

See the template

Every weekday at 07:00, it reads what each employer owed against what arrived, totals the shortfall in a table step rather than in a model, and writes up the exceptions — quoting the figures, never recalculating them.

What it hands back, in the product’s Output view: the totals, the exceptions in a table, and a person to assign it to. A demo workspace; the employers and amounts are synthetic.

What a fund’s risk committee will ask

Answered from how the product works, not from a slide. The full list of controls is on the security page.

Every figure comes from your systems
A query against your own ledger or administration system, totalled by a table step in code. The model explains the result and is told never to state a number the table does not hold.
Nothing reaches a member unapproved
Replies to retirement applications and member communications stop at an approval step, which says what approving will do before anyone decides.
Only the records the reader may see
Answers are built from sources the person asking is allowed to read, and database steps use a read-only connection you set up and can revoke.
Every run on the record
Its input, each step’s output, how long it took, what the model cost and who decided — kept with the run, and in the audit log.
A run stopped for a person. Before anyone approves, the product says what approving will actually do — here, that nothing leaves the system.

Asked in every evaluation

Does it replace our pension administration system?
No. It reads from your administration system through a read-only connection, and that system stays the system of record.
Will it calculate a member’s benefit?
No. The templates are written never to state a benefit amount, a payment date or an entitlement the sources do not give. Where a figure is needed, it quotes the one your systems already hold.
Our database is not laid out like the template.
The database steps carry example queries, and you point them at your own tables. The checks, the approvals and the write-up stay as they are.
Can we see it on our own plan documents?
Yes. We open a template in the builder, connect it to a sample of your documents and data, and run it with you.

Start with the queue that costs your team the most time

Bring one process — member questions, retirement applications or contribution exceptions — and we run the nearest template against your own material.