Bemente N.

I design and build custom systems for businesses whose problem doesn't fit off-the-shelf software. Most of my work starts the same way: someone has a process held together by spreadsheets, three tools that don't talk to each other, and a person whose full-time job is copying data between them. I work out what the system actually needs to do, design it, build it, and hand it over running. I've done this across banking, CRM, mobile, internal ops tooling, and AI. The domain changes; the work doesn't understand the problem properly, choose boring reliable technology, and get the data model right the first time, because that's the part you can't cheaply undo. What I build: ✅ Custom platforms end to end. Database schema through API, frontend, deploy, and handover. Django/DRF, FastAPI, PostgreSQL, Celery, Docker, on AWS, Azure, or GCP. I've spent a lot of time on a multi-currency banking platform as one of three backend engineers multi-currency accounts, card issuing, crypto custody, FX, payroll and payments is a good school for building things that have to be right. ✅ Integrations between systems that weren't built to talk. Seven external financial providers integrated end to end, plus CRM and internal tool syncs. Webhook signature verification, idempotency, retry and backoff, reconciliation jobs that catch what the other side gets wrong. This is the unglamorous middle layer where most custom projects actually fail. ✅ AI, applied carefully. A natural-language reporting tool over a production database where the model never sees a customer row it gets a schema, emits a validated query plan, and every generated query passes a field whitelist and PII guardrails before it runs. Plus MCP servers giving AI assistants controlled access to internal tools, and n8n workflows automating processes that used to be manual. ✅ Internal tooling people will actually use. Reconciliation dashboards, reporting, approval workflows. The measure of a good internal tool is whether the ops team stops emailing you mine do. ✅ Mobile. complete apps built solo for IOS and Android in React Native/Expo. Flutter/Dart as well. How I work: I ask questions before I write code. If your requirements are going to cause a problem six months out, I'll tell you before you pay me to build it that conversation is the most valuable thing I offer, and it's free. I'm comfortable being the only technical person on a project and translating between what a business needs and what a system has to do. If you already know exactly what you want built, I'll build it. If you know the problem but not the solution, that's the work I prefer.