← Industries

Banks · Wealth managers · Financial platforms

Put AI to work in financial services.

Improve onboarding, advisor workflows and document-heavy operations with product design, engineering and evaluation in one team.

Swiss headquarters · ISO 27001:2022
Security and delivery information

Wealth product screens showing a portfolio, net worth and advisor insights.
Design the product around the people who use, review and operate it.

Selected financial work

The product, the decisions and our role.

Explore financial product delivery alongside AI workflow work. Each case explains what it demonstrates and the context behind it.

Where to start

Start with the work your team needs to improve.

01 / Operations and onboarding teams

Onboarding that keeps the reviewer in control

Documents arrive in different formats. Staff re-enter information, resolve conflicts and chase missing evidence.

Connect document intake, suggested fields and exception review in one workflow, with the supporting source close to each decision.

Agree what to measure: handling time, rework, missing evidence and the quality of suggested fields.

Discuss an onboarding workflow

02 / Wealth, product and advisor teams

Financial information people can use

Clients and advisors move between portals, documents and colleagues to find the information they need.

Bring portfolio views, communication and document-grounded assistance into the product experience you already operate.

Agree what to measure: task completion, source accuracy, user understanding and adoption.

Discuss your financial product

03 / Technology and AI teams

Know how your AI behaves in use

A live system needs a dependable way to identify incorrect answers, regressions, rising cost and failure conditions.

Establish representative evaluation cases, operator review and release criteria around the system your team already has.

Agree what to measure: answer quality, permissions, failure handling, latency and cost per task.

Discuss an evaluation

A defined first engagement

Know what you are buying.

These are two ways to begin. Each has its own scope and decision; neither requires you to commit to a later build.

Proof of Value

Prove one workflow before extending it

Agree a bounded workflow, test it with representative data and users, and make the next investment decision from the evidence.

What you bring
Bring the current process, access to the people using it and an agreed route to representative data.
What you receive
A working slice, evaluation baseline, known constraints and a recommendation for the next decision.
Typical duration
Typically 1.5-2 months
Full engagement details →

Evaluation & Assurance

Evaluate a system already in use

Review quality, failure conditions and operating signals in a live system, including one built by your team or another partner.

What you bring
Bring the system context, existing tests and the quality or operating questions you need to resolve.
What you receive
Representative tests, quality and cost signals, failure analysis and a prioritised improvement plan.
Typical duration
Initial assessment typically 1.5 months
Full engagement details →

Already know what needs to be built?

Start with Product Build & Scale. If the priority is still being decided, AI Strategy & Readiness helps shape the direction.

Before work starts, the proposal sets out scope, fees, deliverables, client dependencies and acceptance criteria. Continuing delivery and operation are agreed around the product and your team.

Before we begin

Questions about working together.

A few practical details for the people making the decision.

Can you work with our existing product and team?

Yes. An engagement can focus on an existing product, a prototype or a live AI system. We agree the interfaces, responsibilities and access with your internal team and any other delivery partners.

Product Build & Scale
Do we need to share client data to start a conversation?

A high-level outline is enough for the first discussion. We agree confidentiality before reviewing sensitive material. Any later access to documents, systems or representative data is scoped with the relevant owners and reviewers.

Security and data-handling information
How are scope, fees and completion agreed?

The proposal defines the work, deliverables, fees, client dependencies and acceptance criteria. Each of the four engagements is available independently. A Proof of Value does not commit you to a subsequent build.

Compare engagement options
What can our technical and procurement teams review?

The financial brief, work summaries, evaluation worksheet and security overview are available to download. For a questionnaire, certificate or delivery-specific information, use the request details on our Trust & Security page.

Download review resources

Bring the right people into the decision

Useful material for your team’s review.

Share the brief with your sponsor, the worksheet with your technical team and the security overview with your reviewers.

Your next step

Bring one workflow and the decision you need to make.

Tell us what exists, who uses it and what needs to improve. We will identify the relevant senior lead and discuss the scope, evidence and dependencies together.

People and delivery information

Sunny Gambhir
Founder & Designer-in-Chief
sunny@windmill.digital

For technical context, speak with the technical team. For questionnaires and delivery controls, see Trust & Security.

We agree confidentiality before reviewing sensitive architecture, customer information or documents.