01 Build
Custom software & SaaS
Internal platforms, client portals and multi-tenant SaaS products, designed around the workflow and data you actually have.
Outcome: One system of record instead of scattered tools.
Custom software here means a web application built around one organisation’s workflow and records: an internal platform, a client portal, or a SaaS product used by several companies, each seeing only its own data. The data model, interface and deployment are built as one system.
It fits when core work runs through spreadsheets, email and tools never meant to work together, or when a product idea needs a first version real users can work in. It is less useful when a mature off-the-shelf product already covers the workflow with small adjustments.
Typical needs
- Core work runs through spreadsheets, email and tools that don’t fit
- Off-the-shelf software forces workarounds the team has to remember
- A SaaS idea that needs a production-ready first version
What you receive
- A production web application built around your workflow
- A documented data model and architecture your team can extend
- Deployment, handover and continued development
Approach
How the work runs.
- 01
Records before screens
The records the work depends on — clients, orders, cases, invoices — are listed with who creates each one and where it lives today. The spreadsheets and inboxes become the inventory for the data model.
- 02
Tenants and roles from day one
Who may see and change what is decided early: which company, office or team owns each record, and which roles exist inside it. Isolation is modelled in the database, not added after launch.
- 03
A first release that replaces real work
The first version takes over one complete part of the current process, so people use it daily and the next slice is shaped by what they actually do.
- 04
Run it, document it, extend it
The system is deployed with automated checks on every change, the data model and architecture are written down, and development continues in the same codebase instead of a rewrite.
Technologies
- TypeScript
- React
- Next.js
- PostgreSQL
- Supabase
The engineer who does this work is the founder, Filip Volf — you work with him directly.
Questions
About this service.
Can you build the first version of a SaaS product?
Yes. The first version includes what is hard to add later: separate data for each customer organisation, roles and permissions, and billing rules where they apply. Pametni Advokat works this way — each law office has its own case numbering, lawyer and secretary roles, and data no other office can see.
What happens to the spreadsheets we use today?
They are the starting point. Their columns, workarounds and duplicates show what the data model has to hold. Existing records can be imported, and the move can run in stages, one part of the work at a time, while the old tools stay available.
How is this different from software modernisation & maintenance?
This service builds a new system or a new product, from the data model up. Modernisation starts from software you already run and upgrades or migrates it step by step while it stays in use. If an existing system already does most of the job, modernising it is usually the better place to start.
Related services
- 02
Product & UX/UI design
Outcome: A product shaped around the real work — agreed before the build begins.
- 05
APIs, backend architecture & PostgreSQL
Outcome: Business rules enforced once, where the data lives.
- 11
Software modernisation & maintenance
Outcome: The software you already rely on, safe to change again.
Next step
Let’s talk about what you’re building.
Describe what you need built or fixed, how the work runs today and the constraints. You get clarifying questions or a first outline of the approach — by email, in English or Serbian.