Back to all services

Custom business systems for teams that have outgrown spreadsheets

For teams whose work still runs through spreadsheets, email threads and disconnected tools. We build internal systems around your process, so information moves to the right place and people do not have to do the same work twice.
  • From 15000€
  • Live in 8-16 weeks
  • Built on infrastructure that scales
  • You own the code, the data and the hosting
Discuss a project

When a company outgrows off-the-shelf tools, part of the work often stays trapped in spreadsheets, email threads and separate systems. That is where decisions slow down, information gets lost and small errors become real cost.

We build internal systems that bring the workflow into one clearer place. Role-based access, permissions, audit trails, reporting and integrations are part of the solution, not extras added later. The system should follow how your team actually works, not force the team to adapt to someone else’s software.

If the project involves real-time data, regulated workflows or hardware-related logic, we scope that from the start. The same team that thinks through the solution also builds it to completion.

01 Who this is for

Who we build custom systems for

  • Your team's work still runs through spreadsheets that break when more than two people edit them.
  • Your processes live in email threads, shared folders and tools that do not talk to each other.
  • You are paying for SaaS that almost fits, with workarounds nobody documents.
  • You need real user roles, permissions and an audit trail of who changed what.
  • You want one system that connects to your accounting, CRM or ERP, not a fifth dashboard.
  • You expect the system to grow with the company — more users, more locations, more data — without a rebuild.

02 Process

How we work

  1. 01

    Scoping (weeks 1-3)

    We map how the work actually happens today: who does what, where delays appear, which tools stay in place and what the new system has to connect to. By the end of the stage, you have a written scope, role list, integration map and fixed quote.

  2. 02

    Build (weeks 4-12)

    We build in stages, with working software you can test from week four onwards. Roles, permissions, audit trails and reports are part of the first release, not the second one. We connect to your accounting, CRM or ERP as we go, instead of leaving integrations until the end.

  3. 03

    Launch and rollout (weeks 13-16)

    We do not just "go live". We migrate your real data, train each role group on the parts of the system they use, run the new system alongside the old one for a week or two, and stay on for thirty days of post-launch tuning while the team gets used to it.

03 Relevant work

A recent project in this space

MeterNova — AMR and energy-management data from meters to billing.

Meternova needed one reliable operator system to replace manual meter-reading routines across buildings — readings, diagnostics, alerts and billing all coming from different sources, with operators stitching it together by hand.

We built the operator application and the integration layer that brings meter readings from different industrial protocols into one normalized data model. The same data then powers the dashboards operators use day to day, the reports finance needs, and the billing workflow tenants get invoiced from.

  • Operators see readings, diagnostics and alerts in one tool instead of switching between exports and spreadsheets.
  • Billing runs from the same data operators trust — no manual re-typing between systems.
  • The platform scales across more buildings and meter types without rebuilding the integration layer each time.

The important change is trust in the readings. Operators can see where the data came from, which protocol delivered it and what needs attention before billing starts.

Andres Vaher, CEO at Meternova
View case study
MeterNova — AMR and energy-management data from meters to billing.

04 Price and timeline

Typical scope

Most first releases land between 15000€ and 40000€ and go live in 8-16 weeks. The final price depends on roles, integrations, data volume and whether the project touches hardware or regulated data. We give a fixed quote after scoping.

From 15000€ Live in 8-16 weeks

Typical range 15000€–40000€ depending on roles, integrations, data volume and technical complexity.

Base scope usually includes

  • Scoping, written scope and fixed quote
  • Custom application built around your workflow
  • User roles, permissions and audit trail
  • Reports and dashboards for the roles that need them
  • Integration with one or two existing systems (accounting, CRM, ERP or similar)
  • Data migration from your current spreadsheets or tools
  • Production hosting on infrastructure that scales with usage
  • Role-based training and thirty days of post-launch support
  • Full ownership of code, data and hosting
Discuss a project

Usually separate or optional

  • Hardware integrations or real-time data from physical equipment
  • Additional integrations beyond the first one or two
  • Complex regulated-data handling (medical, financial, GDPR-sensitive workflows)
  • Mobile apps for field workers (separate from the core web system)
  • Ongoing development after the first release
  • Migration from a complex legacy system rather than spreadsheets

05 FAQ

Common questions before we start

Will the new system replace our existing tools or sit on top of them?
Both, depending on the tool. We typically replace the spreadsheets, the email-thread coordination and the SaaS that almost-fits. We keep and connect to the tools your business genuinely runs on — accounting, ERP, CRM, payment processors. The aim is one fewer system, not one more.
Can you integrate with our accounting or ERP?
Yes. We have integrated systems with Merit, SmartAccounts, Microsoft Dynamics, SAP Business One, HubSpot, Pipedrive, Stripe and payment gateways. For industry-specific tools, we check during scoping which APIs are available and where a workaround is needed.
Who owns the code, the data and the hosting?
Yes. We deploy on infrastructure where a single machine failure does not take the system offline, and capacity can be added when usage grows. If the project involves regulated data, hardware integrations or real-time work, we plan the deployment around those constraints during scoping.
What about hosting and uptime — is this a serious production system?
Yes, in most cases. We migrate data from spreadsheets, old SaaS exports, CSV files and, when needed, local databases. During scoping we agree what moves into the new system, what gets cleaned up and what stays in the old system as read-only history.
Can we add features after the first release?
Yes — and most clients do. The first release is intentionally scoped to the work that matters most. Ongoing development happens at a transparent monthly rate, or as discrete projects when the next feature is well-defined. You are not locked into a retainer.
We have a lot of legacy data — can it move into the new system?
Yes, in most cases. We migrate data from spreadsheets, old SaaS exports, CSV files and, when needed, local databases. During scoping we agree what moves into the new system, what gets cleaned up and what stays in the old system as read-only history.

Start with the business goal

Tell us how your team works today

Send a short note about your company, how the work moves through your team today and where it slows down. We reply with next steps, an initial budget range and the questions we need to plan the scoping stage.