Skip to content

About Bitnox

Bitnox Technology Solutions builds software and websites, advises on technology decisions, and teaches the skills behind both.

01 / 03The company

Four kinds of work, one company behind them.

Bitnox Technology Solutions is a Nigerian technology company with clients in Nigeria, the United Kingdom and further afield. The work divides into four: software development for businesses that have outgrown their spreadsheets, web development for companies whose website has to earn its keep, IT consulting for the decisions in between, and technology training for the people who will run all of it afterwards.

02 / 03How projects start

Most projects begin with one person holding everything together.

Most projects arrive the same way. Something works, but only because one person holds it together, and that has started to cost more than it saves. The first piece of work is usually not building anything. It is writing down what actually happens, which is rarely what the policy says happens, and deciding what the first version will deliberately leave out.

03 / 03The other two names

Three Bitnox names, and this site is the technology one.

The Bitnox name also covers two other things. Bitnox Education runs the course catalogue and enrolment, and Bitnox Cleaning covers laundry and cleaning on its own domain. They are separate operations with separate teams, and this site is the technology company.

How we work

What you can hold us to

Six commitments that can be checked against how an engagement actually runs, rather than six words about our values.

A written scope before a figure
Every quote comes with what is included, what is not, and the order the work happens in. Nothing starts on a verbal understanding, because the disagreements that end projects are almost always about something nobody wrote down.
We say when you do not need us
Off-the-shelf software is the right answer more often than a development company admits. If a package covers your situation, we will tell you which one and what it costs, and we would rather lose the project than build something you did not need.
One person who knows your account
You deal with somebody who has read the brief, not with whoever picks up. Questions during a build go to the same person, and so do questions two years later.
Handover includes the keys
Accounts, domains, hosting and repositories are yours, in your name, from the start. A client who cannot leave is not a client, and we have inherited enough systems locked to a previous supplier to know what it costs.
Support is an arrangement, not an invoice per email
Maintenance covers security updates, hosting, backups, monitoring and small changes under one agreement. Nobody should hesitate to report a problem because reporting it costs money.
Training is part of delivery
A system nobody was taught to use goes back to a spreadsheet within a month. Sessions for the people who will actually use it are in the plan, not an extra afterwards.
An illustrative scope sheet. Every quote arrives with what is included, what is not, and what is deliberately left to a later phase.

Getting started

What the first two weeks look like

Nothing is built until the scope is written down and agreed. That is not a formality: the disagreements that end projects are almost always about something nobody put in writing.

  1. You tell us what has to change

    The problem rather than the solution. What is slow, what gets typed twice, what nobody can answer at the counter. An email or a phone call is enough to start.

  2. We ask before we quote

    Usually two conversations. Who uses the thing, what the day looks like now, what happens at month end, and what the existing data is in. This is where a project either becomes clear or turns out to be two projects.

  3. You get a scope, a schedule and a figure

    In writing, with the parts we recommend leaving to a second phase named as such. If the answer is that you should buy something rather than build it, that is what the document says.

An illustrative order of work from a consulting engagement. Cheap fixes are scheduled first, so the long piece is not blocking them.

Where we are

Abeokuta, Nigeria

The office and the Event Space are in the same building on Lalubu Street, Oke-Ilewo, Abeokuta. Local work is done in person where that is useful. Remote projects run the same way as local ones: shared boards, scheduled calls and a written record of every decision, so nothing depends on who was in the room.

Office

24 Last Floor, Majek Kembo Plaza, beside Chicken Republic, Lalubu Street, Oke-Ilewo
Abeokuta, Ogun State
Nigeria

Event Space

The same building holds the Bitnox Event Space, which seats 60 and is booked for conferences, meetings, workshops and classes.

Tell us what has to change

Describe the problem rather than the solution. We will say which service it falls under, what it usually takes, and when the answer is that you should buy something instead of building it.