Quantfolio
How it works
Wealth managersHybrid advisory for private banking at scaleBanksAdvice and savings across the retail bankInsuranceSavings and pension products, automated
PartnersBlogBook a demo
How it works
Who it's for
Wealth managersBanksInsurance
PartnersBlogBook a demo
Quantfolio
Company
AboutContactBook a demoPartners
Who it's for
Wealth managersBanksInsurance
Resources
How it worksAIBlogPrivacy PolicyTerms of Use
© 2026 Quantfolio AS·Org. nr. 915 210 600·Page updated 28 September 2026
FeaturesClients
  • Overview
  • The platform
  • Clients
    • Client types
    • Client information
    • Client activities and data
    • Accounts and orders
    • Documents
    • Lookups and flow logic
  • Flows
  • Investment engine
  • PDF templates
  • Accounts and orders
  • Integrations
  • AI
  • Compliance
  • 3rd party solutions
  • FAQ
  • Overview
  • The platform
    • Introduction & purpose
    • One platform — five ways to operate it
    • Get started
  • Clients
    • Client types
    • Client information
    • Client activities and data
    • Accounts and orders
    • Documents
    • Lookups and flow logic
  • Flows
    • Introduction to flows
    • How flows are built
    • Pages — internal vs public
    • Components
    • Flow examples
  • Investment engine
    • Introduction & purpose
    • Portfolio collection
    • Datasets and calculations
    • Risk models
    • Financial situation models
    • Portfolios and portfolio modes
  • PDF templates
    • Introduction & purpose
    • Commonly used templates
    • Signing
  • Accounts and orders
    • Introduction & purpose
    • Working with your other systems
  • Integrations
    • Introduction & purpose
    • Commonly used integrations
  • AI
    • Introduction & purpose
    • Guardrails
    • The different agents
    • Agent workflows
    • Agent audit trail
    • AI models
    • Quantfolio Platform MCP
    • Connect your other systems
  • Compliance
    • Introduction & purpose
    • Suitability
    • KYC and AML
    • Flow approvals
    • Flows review
    • Audit trail
  • 3rd party solutions
    • Introduction & purpose
    • Morningstar
    • Idura (formerly Criipto)
    • Trapets
    • ENIN — company lookups
    • Sumsub — identification
    • Whereby — meeting links and transcription
  • FAQ
    • Clients and your CRM
    • Product data
    • Accounts and orders
    • AI guardrails
  1. How it works
  2. Clients

Clients

Person, company or group — the system of record for the client relationship, where every flow, document and activity lands.

Client types

At the core of the platform you find your clients. The platform supports three client types you can log to the system:

  • Person
  • Company
  • Group

When you work with clients that are groups, you can construct a group from its members, and each group can have one representative. If you use a representative for a group, that person is the target for information collection through flow instances, and the person asked to sign.

Client information

Each client record comes with fields you can log information against — system fields, plus custom fields you define yourself.

You decide which fields you collect on a client, what you expose in lists, and how you present the client cards.

Fields are filterable and sortable, so you can build views over any segment of your book.

Client activities and data

The platform lets you create and log activities and data against a client, in the same way a standard CRM does. Four activity types carry the relationship:

  • Meetings — planned ahead or logged after the fact, with the meeting note written on the record. Hold the meeting through the built-in Whereby integration and its transcript lands on the client too — or upload a recording from a meeting you held elsewhere and have it transcribed.
  • Calls — the same two ways: plan a call before it happens, or log one that already did, with notes against it. A recording you upload is transcribed like any other file.
  • Documents — everything that belongs to the client in one place — uploaded and logged by an advisor, or produced by a flow.
  • Notes — whatever does not belong to a meeting, a call or a document: a handwritten note typed up, what was agreed in passing, a reminder for whoever picks the client up next.

None of this is filing for its own sake. A meeting note, a transcript, a signed document — each one becomes context the platform's agents can use when they work on that client, inside the same guardrails your advisors work under.

Related

  • Whereby — meeting links and transcription
  • Are you a CRM system?

Accounts and orders

The client record also holds the money side of the relationship: what the client owns, what is being bought and sold, and on what terms. It is organised in four concepts:

  • Accounts — where the client's holdings sit, with positions and cash. A client can own several, and each can be linked to the goal it serves.
  • Orders — the buys and sells that take an account from what it holds to what was advised.
  • Saving plans — the client's recurring contributions, and the products they go into.
  • Mandates — for discretionary clients, the terms an account is managed under.

All four are filled from your portfolio management system, so the platform works from what the client actually holds — not from numbers an advisor retyped.

That is what lets you build dedicated flows for following up the client across the whole relationship, not just the first piece of advice: the annual review that opens on today's holdings, a top-up to a saving plan, a change of mandate.

Related

  • Accounts and orders
  • Integrations

Documents

Documents sit on the client record two ways: uploaded and logged as an activity, or produced by a flow. Anything a flow generates — a suitability report, an offer document, a client agreement — is built from your own PDF templates and stored against the client.

Every template is styled to your brand profile — your logo and colours — so what the client receives looks like it came from you, not from a software vendor.

Related

  • PDF templates

Lookups and flow logic

Much of what you need to know about a client is already held somewhere else. Instead of asking the client for it, look it up against trusted third-party sources:

  • Identity — verify the client with their national eID through Idura, or with document checks and a liveness test through Sumsub.
  • PEP and sanctions — screen the client live as a flow runs, against sanctions lists, PEPs and their relatives and close associates, through Trapets.
  • Company data — registry records, financial history and ownership structures for company clients, through ENIN.

Client information also drives the flow itself, through conditional display and other flow logic. Show a section only to company clients, add due-diligence questions when the client is a PEP, skip what is already known, or cap the risk score for a minor where regulation sets a maximum.

Related

  • 3rd party solutions