Home / Software

The systems a company runs on

We carry other people's traffic for a living, so we know what happens when a system goes down at the wrong hour. We build software the same way: for the day it is under load, not the day it is demonstrated.

Tell us what you need See the CRM

What we build

Four kinds of work. The first three are projects; the fourth is a product we already own and adapt, which is why it costs a fraction of building one.

E-commerce

Stores that hold up on campaign day. Payment, stock, shipping and accounting connected to each other rather than reconciled by hand every evening.

  • Local and international payment providers
  • Stock and order sync with the ERP or accounting system
  • Marketplace integrations where the volume justifies them
  • Page speed treated as a requirement, not a report

ERP

Purchasing, stock, production, invoicing and reporting in one place. Built around how the company already works instead of forcing the company to work around the software.

  • Role-based access, so approval limits are real
  • Migration from spreadsheets without losing history
  • Reporting that finance can reconcile, not just read
  • Runs on your infrastructure if that is what compliance needs

Web platforms, from nothing

Corporate sites, portals, booking and membership systems. Written from scratch when a template would cost more to fight than to replace.

  • Design and build in the same team, not handed over
  • Multi-language and multi-currency where the market needs it
  • Content editable by the people who own it
  • Accessibility and search treated as build requirements

CRM

Our own customer management system, already built and running. Licensed and adapted to your process rather than written again from the first line.

  • Pipeline, offers, contracts and after-sales in one record
  • Adapted to your fields and stages, not a fixed template
  • Weeks to launch instead of months
  • Source code available under a separate agreement
Read about the CRM
OUR OWN PRODUCT

A CRM that already exists

We built it because we needed it: tracking interconnect requests, offers, contracts and the after-sales conversation in one place. It has been in daily use inside the group before it was ever sold to anyone else.

That is the whole argument. Buying it means buying something that has already survived real use, adapted to your fields and your stages — which takes weeks, not the months a new build would take.

Weeks
to launch, not months
Yours
fields, stages, permissions
Optional
source code handover
Ask for a demo

Already running a CRM you cannot leave? We integrate with it instead of replacing it — the work is usually smaller and the risk is lower.

How a project actually runs

Four stages. The one that decides whether the project succeeds is the first, and it is the one most people want to skip.

What we will not do

  • Quote a fixed price for a scope nobody has written down yet.
  • Hand over a system with no documentation and no access to the code.
  • Take a project where the deadline only works if nothing goes wrong.

Understand the work

We sit with the people who will use the system and write down what they actually do today, including the parts handled in a spreadsheet nobody admits to. This is what the estimate is built on.

Agree the scope and the price

A written scope with what is in, what is out, and what each phase costs. Changes are priced when they come up, not absorbed silently and billed at the end.

Build in visible pieces

You see working software every two weeks, not a progress percentage. Something wrong in week three costs a conversation; the same thing found at delivery costs a rebuild.

Hand over properly

Documentation, accounts, environments and the code. Support continues under a separate agreement, but the system is yours to take elsewhere if you ever want to.

Questions clients ask first

Why would a telecom carrier build software?
Because we run our own. The routing, reporting and settlement systems behind the messaging business were written in house, and the team that wrote them does this work for other companies too. It is the same discipline applied to a different domain, not a side business bolted on.
Do we own what you build?
For project work, yes — code, documentation and accounts are handed over at the end. The CRM is different: it is our product, licensed to you, with the source code available under a separate agreement if you need it.
How is the price set?
Per phase, against a written scope. We do not give a number before the first stage is done, because a price quoted over a scope nobody has written is a guess that someone pays for later — usually you.
What happens after launch?
Support and maintenance run under a separate agreement with a defined response time. If you would rather take it in house, the handover includes everything needed to do that; we are not interested in keeping a system hostage through documentation nobody wrote.

Describe the problem, not the solution.

What is slow, what breaks, what is being held together by a spreadsheet. That is enough to tell you whether we are the right people for it.

Start the conversation