Core business systems development
From the discovery that defines it to the platform beneath it — mobile apps, web apps and customer portals, built to be changed.
The challenge
The gap between idea and impact
Between the idea and the first paying customer sits everything that can go wrong: scope, architecture, the deadline — and the handovers between agency, designers, developers and ops, where accountability dissolves. And launch is the easy part. The decade of releases, incidents and integrations after it is where products are actually won or lost.
Our approach
One team, and we stay
We discover, design, architect, build and launch as one team — web platforms, portals, mobile apps and the APIs partners build on — with architecture decisions made for the decade, not the demo. And we stay: monitoring, releases, incidents and feature work handled by the people who built it.
Results
Startup speed, bank accountability
One partner, and no gaps between agency, designers, developers and ops — because they are the same people. And because the same company runs a data and AI practice, your product is born instrumented: analytics, scoring and reporting from the first release, with no re-platforming when the board asks for numbers.
What we do
The decisions taken before the first line of code, written down where they can be argued with. We research the users, map the journeys, wireframe and prototype the experience and test it while changing your mind is still cheap — then hand over a scope you can fund, an architecture the build can stand on, and a design system engineers work from directly.
- Discovery workshops that land an agreed problem and an MVP scope
- User research — interviews, observation and personas from what people actually do
- User journeys, task flows and information architecture, mapped before any screen
- Wireframes and prototypes tested with real users, while changing course is still cheap
- UI design and a design system engineers build from, every state included
- System architecture and a prioritised backlog with acceptance criteria
The systems your customers and your own staff use every day: mobile apps, web applications, customer and partner portals, marketplaces and booking platforms, and the back-office tools where most of the working day actually happens.
- Mobile apps, web applications, customer and partner portals
- Marketplaces, booking and self-service platforms, with the admin tooling behind them
- Built by a small senior team that stays on the system after launch
Most of the systems are already there — the ERP, the CRM, the payment provider, the warehouse. The work is making them talk to each other reliably, so a change in one shows up in the others without anyone re-keying it.
- REST and event-driven interfaces between the systems you already run — ERP, CRM, payments, logistics
- Partner and third-party integrations, versioned so a change on either side doesn't break the other
- Retries, idempotency and reconciliation, so a failed message is recoverable rather than silently lost
For most consumer-facing products in the EU accessibility is now a legal requirement rather than a nice-to-have. We design and build to the standards and test against them, instead of auditing at the end and hoping.
- The European Accessibility Act, in force since June 2025 — e-commerce, banking, transport, e-books and more
- WCAG 2.2 Level AA as the working standard, and EN 301 549 where public-sector procurement applies
- Keyboard paths, screen-reader flows and contrast tested as part of delivery, not bolted on before launch
Faster pages and leaner infrastructure are the same piece of work: less data transferred, less compute burned, less energy used. We profile first and fix what the numbers point at, rather than what feels slow.
- Core Web Vitals measured on real traffic, not only in the lab
- Payload, image and query budgets, so a regression shows up before release rather than after
- Right-sized infrastructure and efficient queries — the same change lowers both the bill and the carbon
Proven in production
Web & Mobile
Netgíró — Iceland's national payment method
Iceland's leading buy now, pay later platform — built and scaled over more than a decade of partnership.
Web
Straumur — A payment facilitator built from an empty repository
Onboarding, processing, settlement, portals and APIs written from an empty repository — kick-off to live money in about seven months, and 50M+ transactions in the first eighteen.
Web
Gaveia — One backend, four booking platforms
Four holiday booking platforms across Croatia and Slovenia, all standing on one core business system — the properties, the prices, the internal tools, and now the AI that answers travellers.