Accountable for the whole system, start to handover.
Plinth Technologies & Consult is run by Samuel Biliksuun, a software engineer based in Accra. You talk to the person writing the code, from the first scoping call to handover.
Background
Before consulting, I spent three years on payment infrastructure: the systems that move money between banks, telcos and merchants, where a failed retry is not a bug report but a missing GHS 40,000.
That work teaches a specific discipline: assume the network fails, assume the third party times out, make every operation safe to repeat, and log enough that you can prove what happened three months later. Most business software never gets built that way. It should be.
For a client, the practical effect is boring in the best way: the invoice run does not double-charge, the booking does not disappear, the integration does not silently stop at 2am, and when something does break there is a trail that explains it.
The same discipline goes into my own products: Pulse, Habor and AcademicTracker. That is where you can see the decisions rather than take my word for them. Read the three case studies.
Plinth Technologies & Consult
Accra, Ghana · GM-045-6434
FOCUS
LANGUAGES
SHIPPED
ENTITY
How we work
01
Scope before code
A short written document: what is being built, what is not, milestones, price. You approve it before anything starts.
02
Two-week increments
Working software on a staging URL every fortnight. You see progress you can click, not a status report.
03
Your infrastructure
Code lives in your repository, deployed to accounts in your name. No lock-in to me as a supplier.
04
Handover that holds
Architecture notes, runbook, and a walkthrough session. Another engineer can pick it up without calling me.