TPSolutions is new. The engineer who would deliver your project is not. This is the record in the form you can check: what was built, what it had to hold up against, and the two public profiles that corroborate it.
None of the work below is TPSolutions client work. All of it was delivered under previous employment, before this firm existed, and none of it is offered as a portfolio. The firm publishes a case study only when a client has read it, approved it, and put their name on it, which is why there is still nothing of that kind on this site. That promise is on the about page and it has not changed.
What has changed is that the other half of the question was going unanswered. Before anyone sends work to a firm this new, they want to know who writes the code and whether that person has done this before. This page answers that, and it stops where the evidence stops.
Clients, employers, and countries are not named here. Those engagements belong to the organisations that held them, so publishing their names is not ours to do. The employment history is not reproduced on this page either, for a better reason than discretion: it is only worth anything where a stranger can check it, and that is the LinkedIn profile at the foot of this page, not a list retyped onto a website that has every reason to flatter itself.
Seven systems that were harder than they looked, each given by the problem it had to solve and the stack it was solved in. No performance percentages, because a number nobody outside a project can check is not evidence, it is a claim wearing a decimal point.
A mobile application built from nothing, plus the custom back-office modules behind it, so field staff could record the health, nutrition, and education conditions that release payments to poor households. Node.js, Vue, TypeScript, Capacitor, and Odoo.
A synchronisation library for both client and server, built on event sourcing, so household and beneficiary records could be created and changed with no connectivity at all and reconcile later with the audit trail intact. Node.js and TypeScript.
A live application refactored onto a replacement backend without a rewrite, against legacy code and a fixed date, while the people who depended on it carried on using it. Vue, TypeScript, and Capacitor.
Acting team lead, from the first architectural decisions on both sides of the stack through search and into delivery. React, Redux, Socket.IO, Fastify, MongoDB, Elasticsearch, and AWS.
Features in a bank's lending platform, where a conflict between two requirements is a compliance question, not a preference, and the requirement has to be resolved with the product owner before a line of it is worth writing. Plus the internal tool that let engineers jump straight to any application state, which took most of the manual clicking out of regression testing.
Map rendering stabilised under a live feed of real-time points, then front-end code refactored across the two different frameworks that were sharing one codebase. The first legacy rescue, and the reason that service exists here at all. OpenLayers, React, and Angular.
Four applications taken up to current framework versions, including the breaking changes in the native Android and iOS libraries that upgrades like that always uncover, and crashes traced down into the native bridge. The unglamorous work that decides whether software is still alive in three years.
Experience is only worth reading if it maps onto the thing you want to buy. Here is where it does. The fifth service, product discovery, is left out on purpose: the experience behind it is real but thinner than these four.
Verify it
The firm publishes its tax registration so you can confirm the entity in one click. The same principle applies to the person. Neither profile below is under this website's control, which is what makes them worth reading.
Founder and delivery owner, TPSolutions.
A practical first conversation
Thirty minutes by video with Tai. The person described on this page is the person on the call and the person who does the work.
Bring the part of the project you are least sure about. That is the useful half of the conversation.
Message us
We reply Monday to Friday, 09:00 to 18:00 GMT+7.
Every message goes straight to Tai. No bot, no queue, no ticket number.