Finance / FinTech
We design and develop digital solutions for financial services, insurance and lending companies and FinTech startups. We build online application forms, calculators, customer portals and custom systems, combining good UX with data security and a reliable architecture. We simplify processes that should feel simple to the user — even when complex rules, integrations and business requirements are running underneath.
Our clients in finance
Software for finance: security, compliance and an application customers finish
In finance, it's not only about whether the system works. Data security, reliability, transparent processes and user convenience matter just as much.
We design financial apps and systems to cut out unnecessary steps, make decisions easier and guide users through the whole process — from first contact to submitting an application, making a payment or handling documents.
A financial application is a path of trust
Customers don't abandon an application because it's long, but because halfway through they stop understanding why they're giving more information and what will happen to it. Designing these paths means justifying every field: what's mandatory and why, what can be pulled from public registers instead of asking, and where to show a real person who can help finish the conversation.
In restructuring and finance-related services, the mechanics are the same, only the stakes are higher: customers come to you in a difficult situation and want a preliminary answer before they share their details. A calculator or a short qualifying form gives them that answer straight away, and filters out cases that are outside your scope.
Auditability, permissions and maintenance
In a financial product, you have to be able to reconstruct who changed what and when — in customer data, in the application status, in a settlement. We launch the event log together with the first version of the system. Separately, we define permissions: who can see customer data, who can change it and what remains in the log after that change.
The second issue is maintenance. We set up monitoring, alerts and an incident response procedure together with the rollout, and we release changes so they can be rolled back within minutes. We treat application security as part of the scope, not as a final stage.Case studies in finance
Fewer abandoned applications thanks to a simpler path to financing
Client: Horyzont Capital
Industry: Finance / FinTech
A website that builds trust in the firm from the very first contact
Client: KMR Restrukturyzacje
Industry: Law / LegalTech
„The biggest change was automated scheduling and budget management — our marketing started running more smoothly. They know the technologies they work with really well and can give good advice.”
Michał Słotwiński — Head of Customer Success, Semcore
Review from ClutchThe basics
How is a FinTech project different from a regular digital product?
FinTech is any software that touches money: payments, settlements, scoring, application processing, corporate finance management. The technology is the same as in other projects — what makes the difference is the cost of a mistake, because here it has financial and regulatory consequences, not just reputational ones. That's where requirements come from that are optional elsewhere but a precondition for launch in finance: a full audit trail, operations that are safe against the same request being repeated, separation of permissions and encryption of sensitive data.
The second difference is pace. The "ship fast and fix it later" approach has limited use here. Some things have to be right the first time, because a fix after the fact means correcting settlements, not updating a screen.
How we work
How do we run financial projects?
We start by mapping the process as it really is — with the people who carry it out, not from a description in the rulebook. This gives us a list of places where data is retyped by hand or waits for someone's decision, and that list sets the order of work. Then we draw the line: what our system does, and what stays with the institution, the payment provider or the accounting system. That line determines the scope of regulatory requirements, and it's worth drawing before the first line of code.
We build with a strong focus on testing the paths where money is involved, and on an event log from day one. The rollout is preceded by work on data that closely resembles the real thing — not on a sample.
On your side are the regulatory requirements of your business, agreements with institutions and decisions about the scope of data. On our side are architecture, development, testing and deployment.
The timeline depends on the number of integrations with external institutions — their schedules and verification processes can take longer than the build itself.
Decisions
Decisions to make before the first screen is built
What data you really store. Every field with sensitive data comes with obligations. The cheapest protection is not storing what you don't need — and that's a product decision, not a technical one.
Who is the source of truth for the balance. Your system or the institution's. Two equal sources mean discrepancies that have to be reconciled by hand, and that's the most expensive kind of operational work.
What happens when an operation fails halfway. It sounds like a technical question, but it's a business one: do we roll back or leave it to be investigated, who sees it and after how long. Without an answer, the system will decide for you — by accident.
What not to do. Don't put off the event log — adding it after the fact won't recreate the history. Don't test on production data. And don't plan a launch for a fixed date if there's a verification on the institution's side along the way.
Scope
Financial products built on trust
We create digital products that make it easier for customers to deal with financial services. For Horyzont Capital, we designed a simpler path for applying for financing, cutting out unnecessary steps. In other projects, we used calculators and forms that help users get from their problem to the right service faster. For Mikulewicz Ostaszewski and Jabłoński & Wspólnicy, we built restructuring calculators with automated forms that shorten the path from a financial problem to a consultation.
We can also start a new product idea with a prototype or MVP to validate the key assumptions before building the full system.
What we build
FinTech apps, calculators, online applications and customer portals
We design, among other things:
- web and mobile apps for FinTech,
- online forms and applications,
- financial calculators,
- customer portals,
- document management systems,
- payment and external API integrations,
- custom systems that support financial processes.
We design every solution around a specific business process, instead of fitting the company into a ready-made template.
Conversion
How we design an application form
We split the path into short steps with visible progress, save the application as it's being filled in and explain next to each field why we're asking for it. We move the most sensitive questions to the point where the user has already invested some time, and we pull some of the data from public registers instead of asking the customer. At the end comes honest information: when the decision will be made and who will be in touch.
That's how we built the application path for Horyzont Capital — and that's also where we measured how well these mechanics work.
FAQ
Questions we hear from the financial industry
- We build web and mobile applications, online applications, financial calculators, client portals and custom systems supporting financial processes. We tailor the product scope to the business model and user needs.
- Yes. We design integrations with payment providers, accounting systems, CRMs, user verification services and other APIs needed in the product. Specific capabilities depend on the chosen vendors and their requirements.
- We address security from the architecture design stage. This covers data storage, encryption, access control, audit trails and securing communication with external systems.
- Yes. If the product is at an early stage, we can start with a prototype or MVP covering the most important business process. This allows the solution to be validated before investing in a full system.
- We store amounts in the smallest unit as integers — pennies, not pounds with a decimal. Floating-point numbers can't precisely represent many decimal amounts, and after thousands of operations the difference shows up in a report rather than in a single transaction. The second element is the principle that a balance is the sum of ledger entries, not a separate column that gets overwritten: that way any discrepancy can be traced back to a specific operation.
- Legal and licensing requirements should be defined by the client's legal or compliance team. We then help translate those requirements into architecture, features and system behaviour.
- Yes, and it's often the most sensible first step. The form then acts as a separate layer: it collects data, validates it and passes it to your system via API or CRM integration. You gain a new channel without touching the core, and after a few months you have data on where people drop off — and only then decide whether to go further. One condition: the system must have some way of accepting data from outside.
- A calculator or online form is usually a few weeks' work. A client portal with login, documents and case history — a few months. External integrations have the biggest impact on the timeline: identity verification, payments and qualified signatures all require the vendor's own approval process, which can take longer than the build itself. We prepare an estimate after a short workshop to establish the system boundary.
Let's build digital products for your company together
Other industries
SEE ALL8 CASE STUDIES
Real Estate / PropTech
For developers, real estate agencies, rental operators and PropTech companies, we build systems that bring order to sales, rentals and property data. We build custom CRMs, listing portals, booking systems, customer portals and analytics tools, among other things - integrated with the solutions your team already uses.
5 CASE STUDIES
Construction / ConTech
In construction and ConTech, we work with contractors, developers and design firms. We build construction project databases, job management systems and websites that bring order to B2B communication. Digitization arrives later here than elsewhere, so the starting point is often replacing paper and spreadsheets with one coherent system with a change history.
3 CASE STUDIES
Education / EdTech
We build e-learning platforms and LMS systems for EdTech startups, universities, training companies and language schools. Here, success is measured by completed courses, not by the length of the feature list — so we start with the learner's journey: the first visit, visible progress and getting back to learning that was interrupted two weeks ago. Payments, group licenses and reports all serve that one goal.
3 CASE STUDIES
Law / LegalTech
We design websites and custom software for law firms, in-house legal departments and LegalTech companies. We build calculators, qualifying forms, document workflow systems and solutions that make case handling more efficient, among other things. We automate repetitive processes and leave legal judgment to the lawyer.
2 CASE STUDIES
Automotive / Mobility
We work with parts manufacturers and distributors and automotive brands that sell online. We build stores and catalogs where customers get to the right part - by make, model and engine version, by OE number or by replacement. We make sure that expanding into new markets means configuring the existing platform, not building another store from scratch.
2 CASE STUDIES
Entertainment / GameTech
For game studios, streaming platforms and brands that build communities, we create social apps, loyalty systems and content platforms. We design them for scale, traffic spikes and user engagement - from the first version of the product to its further development.
