Baumann & Partners, 2025

The investor questionnaire moves from paper to the portal.

The AFB data-entry flow is implemented in the layout of the new customer portal, multilingual and accessible, instead of standing alongside as a separate application flow.

Building a project like this View project

Step 2 of 7: data reconciliation of personal data with salutation, academic title, last name, first name and birth name.

Step 3 of 7 of the investor questionnaire: quick assessment with selectable tiles for bonds, bond funds, equities, equity funds, unit-linked life insurance and certificates.

Screens

This is how it looks.

A selection of screens from the product. Swipe through.

Data verification of personal details with salutation, academic title, last name, first name and birth name, with step navigation above. — Data verification before the actual questionnaire

Reference bank details section with account holder, bank, IBAN and BIC, below it a note on how to verify the authenticity of the page. — Reference bank account, including proof of authenticity

Quick assessment of knowledge and experience: tiles per asset class, one of which is selected. — Quick assessment: only the selected item is explored further

Expanded question block about equity funds with selection areas for experience duration and trading frequency. — Deep dive by asset class

Problem

The initial situation.

The investor questionnaire is regulatorily mandatory, but ran outside the portal and, as a separate application flow, would have meant a break in the customer experience.

Solution

How we solved it.

Piparo builds the capture flow directly into the layout of the new customer portal, multilingual and accessible, and set up the remote test environment so the customer can review the flow themselves.

Result

What came out of it.

Two of three questionnaire variants are done; the rollout is scheduled in the shared roadmap behind end-customer access and the accessibility release. Working together continues in the biweekly Jour Fixe.

Effect in figures

Which was measurable in the end.

01 In progress Questionnaire in the portal

02 August 2025 Engaged

03 Multilingualism and accessibility Included in the contract

Information

How it was built.

Platforms: Web (responsive)
Tech Stack: React
Remix
Keycloak
OpenProject
RHEL test environment
Architecture: The AFB data-entry flow builds on the existing customer-portal frontend (see project BPonline). Data storage and custody systems (IBO, FINOVA) sit with the customer or with infrastructure partner BOZZ respectively; piparo is responsible for the frontend. The remote test environment runs on a customer-side Linux server (RHEL, among other things with Tailscale and Cockpit), set up in a joint session with IT and the infrastructure partner.
Duration: Since August 2025, ongoing

Also suitable

Further projects from our portfolio.

Bolzfieber, 2021

A football community that we build and run ourselves.

2021 Live since, in operation

piparo.party, 2024

25 offline party games on one device.

25 Games, offline

GlowingBlox, 2022

Real-time multiplayer board game for iOS and Android.

iOS + Android In-house product, paused

Next step

Do you want to build something similar?

30 minutes is usually enough to find out whether we are the right people for your project.

Arrange an initial consultation View more projects