

Escrow for social commerce on Mobile Money — the buyer's payment is held until delivery is confirmed.

A full-stack engineer in Ghana building web and mobile products for African markets — from the database schema to the last pixel.

A quick look at the work so far — and how much of it is covered by tests.
In-depth looks at what I built, the decisions behind it, and what changed for the people using it.


Escrow for social commerce on Mobile Money — the buyer's payment is held until delivery is confirmed.

Workflow automation on a visual canvas, run by a durable execution engine. My final-year thesis.
Farmer-to-buyer marketplace with price negotiation, dispatch and Mobile Money wallets. Built for the GDSS-PSInno AgriTech Challenge.
NCLEX exam-prep platform for a physician-led tutoring practice: bookings, tuition payments and student portals.


Escrow for social commerce on Mobile Money — the buyer's payment is held until delivery is confirmed.
10 projects across fintech, agritech, commerce, education and automation.
See all 10 projectsWhere I'm most useful on a team — and the tools I reach for in each.
Decision records from my builds — what I chose, what it cost, and why.
From people I've shipped with — clients, teammates, leads. Written by them, read by me before anything goes up.
Nobody's written one yet. The first one gets this whole stage to itself.
1 square = 1 review
A few honest lines about what it was like to work together. Clients, teammates, leads and mentors — all welcome.
Yours would be Nº 01
Quick answers to what people usually ask before we work together.
Full-time software engineering roles and freelance builds — remote, or on-site in Ghana. I'm happiest owning a product end to end: data model, API, web and mobile.
TypeScript end to end: React and Next.js on the web, React Native with Expo on mobile, and Node.js (Express or NestJS) with PostgreSQL and Redis behind them. I also work in Java with Spring Boot and in Python when a project calls for it.
Architecture first: I design the data model, system boundaries and API contracts before writing features, then ship in small, tested steps. I use AI tools to move fast — and review and test everything they produce. Nothing ships on blind trust.
Yes. I start by reading, running and testing what's there, and I write decisions down before changing them — AutoFlow alone has 25 architecture decision records.
Email amoahjerry835@gmail.com, or send a message through the contact page. LinkedIn works too.
Have a role, a project or just an idea? My inbox is open.