About

Small, on purpose.

Connect-One Technologies builds and operates software products from South Africa. The people who design a system are the people who write it, deploy it, and fix it.

We work end to end. That means taking responsibility for the parts that are easy to forget - the payment integration, the hosting, the backups, the app store release, the support call at half past four on a Friday. A product that works in a demo and falls over in a school office has not been built.

It also rules some things out. There is no handover to a support desk that has never seen the system, and no third party to blame when something breaks. If one of our products is down, the person who can fix it is the person who wrote it, and they already know.

Each product runs as its own brand, with its own database, its own hosting and its own release pipeline. That separation is deliberate and it costs us something to maintain. It buys the thing worth having: a problem in one product cannot become a problem in another, and a customer's data lives where it belongs rather than in a shared pool.

How we decide what to build

Most of what we run started as something somebody described to us over coffee - a school administrator explaining what the last week of term actually looks like, a venue owner describing the queue at the till. Not a feature request. A description of a bad afternoon.

So the first conversation is not a demo. It is us asking enough questions to work out whether software is the right answer at all, and saying so when it is not. We would rather talk someone out of a project than build something that quietly becomes another system nobody opens.

When we do build, we start narrow and put it in front of real users early, because the thing everyone assumed was essential usually is not, and the thing nobody mentioned usually is.

  • We build for the people doing the work, not for the person signing the invoice.
  • We would rather ship a small thing that gets used than a large thing that gets demonstrated.
  • If we are the wrong fit, we say so early, when it costs nothing.

Want the technical version?

How we actually build and release - AI in the loop, scheduled releases that check themselves, and what happens when one does not answer correctly.

How we build