Software development
Custom CRM and business systems.
Systems that replace spreadsheets, paper and manual re-entry. Cut to the process that actually exists in your company, not to someone else's template.
When an off-the-shelf CRM is not enough
Most companies start with a ready-made tool and end up bending their work to fit it. That is fine until the part that makes you money is the part the tool does not model, and then it becomes a spreadsheet next to the CRM, and then three spreadsheets.
A custom system is worth it when your process is the thing you compete on, when the data lives in several places that never agree, or when people spend hours copying between systems that could talk to each other.
What a custom system covers
Scope differs by company, but the pieces recur.
- Clients, contacts and their locations, with the history attached.
- Your pipeline, with the stages you actually use.
- Documents and invoices where the work happens, not in a separate folder.
- Reports built from live data instead of assembled by hand each month.
- Roles and permissions, so people see what they should and nothing else.
From practice
We built a CRM for a consultancy working with restaurants and food brands: it tracks clients and their venues, consolidates data coming in from delivery platforms and produces the reports the team used to assemble by hand.
For a clinic group we built booking, patient records and messaging automation into one system. For restaurants we built Patrono, where the owner sees revenue, costs, food cost per dish and shift schedules in one place.
Integrating with what you already have
A new system that ignores your existing tools creates a second island. We connect to accounting, e-invoicing, point of sale, email and whatever else already holds your data, through APIs where they exist and through file exchange where they do not.
Your data stays yours
The database is yours, the code is yours, the export is available at any time. Hosting can sit in your cloud account or in ours. If the relationship ends, you leave with everything, which is the only arrangement that makes the decision reversible.
From the portfolio
Business systems we have built.
Restaurant Management Platform
VisitPatrono
Operations platform for a restaurant, in the browser and on the phone. The owner sees where the place stands every day: revenue, costs and supplier invoices in one place, food cost per dish with margins, shift schedules staff open on their phones, and HACCP records ready for an inspection.
Read the case study
Business system
Agency CRM
CRM for a consultancy working with restaurants and food brands. Tracks clients and their venues, consolidates data from delivery platforms, and produces reports, a planner and analytics.
SaaS platform
VisitKlinika Hub
Clinic management platform with online booking, patient records and WhatsApp automation.
Questions
FAQ
How long does a custom system take?+
A first usable version typically takes two to four months, and it is deliberately narrow: the part that hurts most, in production, being used. Everything after that is built on something people already rely on.
Can it connect to the tools we already use?+
Usually yes. Where a tool has an API we integrate directly, and where it does not we exchange files on a schedule. We check this before quoting, because an integration that turns out to be impossible changes the whole plan.
Our process is not written down anywhere. Is that a problem?+
No, that is the normal starting point. Part of the work is sitting with the people who do the job and writing down what actually happens, which is often the first time anyone has.
What happens to our data if we stop working together?+
You keep it. The code and the database are yours, exports are available throughout, and handover documentation is part of delivery rather than something you have to ask for.
Contact
Have an idea? Let's talk.
Tell us about the project. For smaller ones we send an analysis and a quote within a few days. For larger and more complex work we agree the scope of that analysis with you first.