What we have learned running this software for real firms
Tax, stock, payroll and the parts of a working week software is supposed to make easier. Written by the people who build it and answer the phone about it, using figures already published on this site.
The 2025 VAT Act, and what it costs to get it wrong
One invoice, worked twice. The gap between the two totals is money your customer paid and you could not recover.
Why software sold in Ghana has to work without a network
The connection drops at the third stop, in the warehouse and on most afternoons in Kwabenya. A system that stops there is a system people stop using.
Six questions to ask any supplier before you sign
Ask all six of every supplier on your list, including us, and compare the answers rather than the demonstrations.
What moving a year of books actually involves
The part every supplier calls straightforward, written out properly: what has to be decided, by whom, and in what order.
Not written yet
SSNIT tiers and PAYE bands, worked through one payslip
A single month for a single employee, with every deduction shown rather than summarised, so you can check it against the number you already know is right.
Not written yet
Counting stock so the book and the rack agree
Why a variance is a question and not an adjustment, and what changes when the count is taken where the stock is.
Not written yet
What we write about
Narrow on purpose. There is no shortage of writing about running a business in general and very little about running one here, under these rules, on this infrastructure.
VAT, NHIL and the GETFund levy under the 2025 Act, PAYE, SSNIT and the returns that go with them. We hold these as editable rates inside the software, which means keeping up with them is our job either way.
Power that goes, networks that drop, a shop floor where nobody is going to type. Most business software is designed somewhere these are edge cases, and here they are Tuesday.
What to ask a supplier, what a switch costs, when a spreadsheet is still the right answer. We publish these knowing some readers will conclude they should stay where they are.
Print, manufacture, supply, services, schools. Written from sitting in them rather than from a survey, which is both the strength of it and the limit of it.
Written by the people who build it, and corrected in the open
Four rules, which exist mostly to stop this page turning into the kind of content marketing it was written to avoid.
The person who wrote the VAT rates into the software writes the piece about the VAT rates. It is slower than commissioning it and it is the only reason any of it is worth reading.
There is no schedule and no quota. A monthly cadence is how a blog ends up with twelve pieces a year that nobody needed to write.
No guest posts, no sponsored pieces and no exchanges. Everything here is ours, which is a limitation worth knowing when you weigh how much to trust it.
Where a piece argues for something rather than describing it, it says so. The arguments are the useful half, but a reader is owed the distinction.
A correction is made on the piece itself with the date on it, rather than by quietly editing the sentence. Where something turns out to have been wrong enough to matter, the note says what it used to say.
Where to start, depending on why you are here
The list above is in the order things were written, which is rarely the order anybody wants to read them in. Pick whichever of these three describes your week.
- You are working out what the 2025 Act means for your invoices
Start with the piece on the Act. The levies sit inside the VAT base now and the arithmetic changed, which is the part that catches people out on their first return rather than on the day it was gazetted.
- Your network drops and the work stops with it
Start with the piece on working without a network. It is about what has to be true of software before a shop floor can keep running through an outage, and it is the one we are asked about most after a bad week.
- You are about to sign something
Start with the piece on the questions to ask before you sign. It is written to be used against us as much as against anybody else, and the comparison page carries the same six questions in a shorter form.
Why half this list is still a title
Three of the six pieces above are a heading and a subject and no words yet. They are listed anyway, with the dates absent, because a page that showed only the finished three would be telling you this was a complete body of writing.
Each of the three is something we have done repeatedly and taken notes on. None is a topic picked because it would rank well, which is why none of them has been written quickly.
That is how to read the list: where there is no date and no reading time, there are no words. Nothing on this page is hidden behind a form or an email address.
Several of the pieces that exist were written because somebody asked the question twice. If one of the three is what you actually need, say so and it gets written next rather than eventually.
It is the same habit as naming the unbuilt modules on the pricing page and the penetration test we have yet to commission on the security page. A supplier's unfinished list is worth more to a buyer than their finished one.
Bring the question your current supplier talked around
Forty minutes on your own figures. If the answer is that you should keep what you have, you will hear that, which is what the comparison page is for.
No account needed to ask · We reply within one working day