Services
Custom software development services
Twelve services, each with its own page: what we actually deliver, who it suits and how long it takes. If you are not sure which fits, read how to choose below.
How to choose where to start
We work on business applications — the ones that run a company's operations, not the ones that present it. That means rules of your own, roles, approval flows and integrations with the systems you already use.
We can start a project from scratch, step into one already under way, or take over one abandoned by someone else. In every case the first step is a conversation about what needs solving, not a quote sent blind.
You have an idea but nothing built
Start with a web application or a mobile app, depending on where your users work. If you sit in the area one of our solutions covers, that can shorten the road.
You already have an application and it gets in your way
If it works and only the versions are old, you need modernisation. If you do not know what you have, start with a code audit — you receive a written document you can take to any team.
Your programs do not talk to each other
That is where API integrations and automation come in. The clear sign is someone copying data from one program into another every day.
You run the company out of spreadsheets
Internal management systems and a custom CRM solve exactly the moment when the number of copies of the same file became a problem.
All 12 services
Each has its own page, with what we deliver and how long it takes.
Web applications
Web applications for processes an ordinary website, a CMS or an off-the-shelf product cannot cover.
Details → 4-10 weeksMobile apps
iOS and Android apps connected to the data and the operations you already have, not isolated from them.
Details → 6-14 weeksAPI integrations
We connect the systems currently held together by copy-paste: suppliers, couriers, invoicing, ERP, marketplaces.
Details → 1-4 weeksCustom CRM
A CRM that follows the way you sell, instead of forcing you to sell the way a software vendor decided.
Details → 5-10 weeksERP and internal systems
Internal applications that bring together in one place the operations currently held in dozens of spreadsheets.
Details → 8-16 weeksB2B portals
A place where your partners place their own orders, with their contract prices and real stock in front of them.
Details → 6-12 weeksProject rescue
We audit, stabilise and take over existing PHP/Symfony applications, with a written assessment and a clear plan for what to keep, fix or rebuild.
Details → 1-2 weeks for the auditLegacy modernisation
We bring applications stranded on old versions back to a state where they can be maintained and extended again.
Details → 4-12 weeksCode audit
A written assessment of your application: what risks exist, what remediation takes, and where it is worth starting.
Details → 1-3 weeksAutomation
We move into code the repetitive work someone currently does by hand every morning.
Details → 1-5 weeksMaintenance and support
Daily care for an application already in production: updates, monitoring, verified backups and a person who answers.
Details → Monthly contractAngular interfaces
Interfaces for data-heavy applications, the kind people spend whole hours inside every day.
Details → 4-10 weeksSolutions
Or start from a solution already designed for your industry
If your industry is on the list, you start from a proven product rather than a blank page.
From practice
What this looks like on a real project
The list above says what we deliver. The case studies say where it started, what we decided along the way and how the work looks now.
Leave taken out of the spreadsheet and out of the inbox
The record of leave lived in a file kept by one person, and approvals travelled by email. It worked, until two managers approved the same day in parallel.
Read the case study → Property managementA payment notice the owner understands unaided
The manager spent more time explaining the calculation than doing it. The application did not shorten the calculation — it removed the need for the explanation.
Read the case study → FinanceThe receipt photographed on the spot, the claim closed without the pile
Receipts collected in a wallet and reached accounting once a month, creased and without context. Half the time spent on claims went into reconstructing who spent what, where and why.
Read the case study →Not finding what you are after?
The list above covers what we do most often, not everything. If you have something else to build, write to us — we will tell you straight whether it is something we do well or whether you are better off looking elsewhere.