Case Study · Financialbot
From complex data assets to new data-driven solutions
Financialbot.com AG already operated a substantial data platform. The challenge was to combine existing data, new sources and business ideas in a way that could support technically robust and commercially viable solutions.
Björn Wesarg, founder of Wingmen Experts, worked with Financialbot.com from late 2018 until spring 2021 at this intersection of business, product and technology. The work included close collaboration with the technical board member and the CTO.
The starting point
Financialbot already held extensive company, financial and job-market data. At the same time, additional crawling and social-media data was to be incorporated and new data-driven business opportunities explored.
The central question was therefore not which technology to introduce next.
It was about determining which data could be combined meaningfully, which commercial use cases could emerge from it, and what solution architecture was required to support them.
Bringing business ideas, data and architecture together
Working with the technical board member and CTO, the functional and technical foundations for new platform capabilities and the resulting solution architectures were developed.
By combining different data sources, new use cases emerged in particular across three areas:
Account-Based Marketing
Identifying and analysing companies and relevant buying centres more precisely.
Sales Intelligence
Making existing data assets usable for new sales-related applications.
Recruiting
Identifying and analysing companies and candidate profiles more effectively across different data sources.
Aligning business and engineering around the same objective
The work went beyond the technical design of individual platform functions.
Business requirements had to be understood, technical possibilities assessed realistically, and commercially viable solution concepts developed from both.
That required different perspectives to be aligned: management, business development and software engineering.
Financialbot later described this role as an important link between technology, product and business.
The delivery structure also had to scale
Alongside product and solution architecture, the foundations for additional development capacity were established.
Together with the technical board member and CTO, requirements and evaluation criteria for international development partners were defined. The selection and integration of external teams were also supported.
This meant product development, technical architecture and the delivery structure required to support them were considered together.
The result
Existing data assets and additional data sources were turned into new data-driven product approaches and use cases for Account-Based Marketing, sales intelligence and recruiting.
At the same time, structures were established to support the further expansion of development capacity.
The collaboration developed to the point where Financialbot offered a permanent continuation of the relationship and, in addition, an opportunity to participate in the company as a shareholder.
“Particularly impressive was his ability to understand business requirements quickly, assess technical possibilities realistically and turn them into commercially viable solution concepts.”
Former Board Member
Financialbot.com AG
Written reference available on request.
What this case means for Solution Architecture today
Existing systems and data assets increasingly meet new requirements, new data sources and new business ideas. The decisive question is rarely purely technical.
The key questions are:
- What business problem needs to be solved?
- Which requirements follow from it?
- Which existing data and systems can be used?
- What needs to be added or integrated?
- How can this become a technically robust and commercially sensible solution?
Connecting business requirements with technical solution architecture is now a core part of how Wingmen Experts works.
Facing a similar challenge?
When existing systems, new data sources, AI requirements or new business lines come together, business requirements and technical architecture should be considered as one problem rather than separately.
Book a Clarity Call