# Partners: five systems, one interface for every advisor

> Partners ran five financial systems from five vendors. A shared microfrontend layer gave advisors one interface and let each module ship on its own.

- Canonical: https://techmates.io/en/case-studies/partners
- Client: Partners
- Industry: Financial services
- Published: 2026-08-19
- Services: Custom software development
- Technology: Financial platform

---

## Five vendors, five interfaces, one advisor network

Partners is a financial advisory group in Czechia and Slovakia, now expanding to Romania. Its advisors move between CRM, a lead exchange, contract and commission workflows and client portals every working day.

Each of those five systems came from a different vendor and looked different. An advisor learned five interfaces to do one job. Internal teams ran and maintained five separate systems, each with its own way of handling financial and customer data. Partners wanted one experience without rewriting five working systems.

### What advisors and internal teams needed

- One interface across advisor and client workflows
- Financial and customer data handled to the same security standard everywhere
- A foundation that holds across several markets

### What the architecture had to leave alone

- Five vendors and five release cycles
- Distinct business logic in CRM, leads, contracts, commissions and portals
- Coordination across many teams and applications at the same time

## A shared layer instead of a replacement

We designed and implemented a microfrontend architecture across all five systems. A microfrontend splits a user interface into modules. Each module shares the same patterns and components; each one ships on its own path.

We set the shared approach first and then applied it system by system, workflow by workflow. The architecture was half the job. The other half was coordinating change across the teams and vendors who own the underlying systems, and we brought methods from earlier large programs to that.

### Advisers see one system

The five applications now share a common user-interface layer and one architectural approach for future change. An advisor moves between CRM, leads and contracts as though it were one environment, while the systems underneath keep their own responsibilities.

### Teams release one module at a time

A module goes live without releasing the whole platform. Releases stop waiting on each other, and each system's business logic stays where it was.

> Collaboration with Techmates is at a very high level. Their approach to the project is not so much on the supplier-customer axis, but rather on the level of 'partners who have a common goal,' which I, as a project leader, extremely appreciate because it is definitely not common with other suppliers and it greatly facilitates mutual collaboration and cooperation.
> — Petr Bartoš, Co-founder & COO, Partners

## One technical approach for whatever comes next

Partners has a shared microfrontend architecture, one interface across five systems and modules that deploy independently. The next change to any of the five starts from the same foundation instead of a new integration.