Every service below is backed by something already running in production, named underneath it. Nothing here is a capability I am hoping to acquire on your project.
Move a financial institution through a reclassification without losing its books.
Bank of Ghana transition closes 31 December 2026
Ordered by how quickly an engagement can start, not by what I would rather be doing. If none of these is quite it, describe the problem and I will tell you honestly whether I am the right person for it.
Chart-of-accounts mapping, migration off whatever runs today, the reporting pack the new category requires, provisioning basis, dual-control and AML configuration, and an audit trail an examiner can follow. Fixed scope, fixed fee, finished before the deadline rather than after it.
Best fit: a community bank, credit union or microfinance institution with a supervisory deadline and no engineer.
Provisioning, deploys, TLS renewal, backups with restores that are actually tested, uptime checks and an upgrade path. The work that decides whether a product survives its second year, done by the person who wrote it.
Best fit: a business running something important on infrastructure nobody owns.
Delivery, templates, campaigns and a prepaid balance where every movement is written to a ledger, so "where did our units go" has an answer. Sending is designed never to break the thing it reports on — a failed message must not fail a deposit.
Best fit: anyone sending receipts, balances or reminders who does not want a second vendor relationship.
USSD session flows for feature phones and metered data, and mobile money collection that treats payment as asynchronous: the order is pending, the webhook is signature-verified, the amount is checked, and stock or balance moves only then. Retries are idempotent, because the provider will retry.
Best fit: a business whose customers are on feature phones, or who pays for a card checkout most people abandon.
Extraction, reconciliation, validation and a batch import that can be rolled back. The output is the same data with its history intact and a report saying exactly what did not survive and why, rather than a silent best effort.
Best fit: a vendor stopped answering, or the business has outgrown the spreadsheet it was built on.
Trial balance, income and expenditure, portfolio and arrears, cash book, teller activity and dormancy — drawn from the postings themselves, exported in the shape the supervisor asks for, on the cadence they ask for it.
Best fit: a regulated institution whose reporting is currently one person and a spreadsheet.
Catalogue with real variants and per-variant stock, mobile money as the primary way to pay, delivery zones priced before checkout instead of as a surprise, order tracking without an account, and an admin the owner actually operates. Built data-light, because the customer is on mobile data.
Best fit: a retailer selling on WhatsApp who is losing orders in the thread.
Local storage as the source of truth, client-generated identifiers, append-only writes, replay queues and deterministic conflict rules. The difference between a till that survives a dropped connection and one that loses a day of trading.
Best fit: point of sale, field operations, or anything used where connectivity is not a given.
Colour contrast measured on every text node in both themes rather than sampled, every page rendered under its own content-security policy, every outbound link and product surface loaded in a real browser, structured data validated, and the interaction layer exercised. Findings, severity, and what to do about each one.
Best fit: a team that suspects its site has problems it cannot name.
A help messenger that embeds in your product, answers from your own published material before it reaches for a model, streams its replies, and hands to a human when it is not confident. WhatsApp joins the same conversation instead of living in a separate phone.
Best fit: a business running support out of a WhatsApp inbox with no record of what was promised.
There is no price list here because there is no honest one. A migration for an institution with eleven years of history is not the same job as one with two, and quoting either from a table would mean padding one and underselling the other.
Describe what you have and what has to be true by when. You get a fixed scope and a fixed number back, or a straight answer that this is not work I should take.