Work with me

Fixed scope. Priced per deliverable.

I take a product from the first version to production: backend, front-end, infrastructure, and AI where it helps. You see a written plan before you pay for a build, and every deliverable comes with its own acceptance test.

Three ways to start

from €1,000Scoping sessionA paid session on your problem. It ends with a written plan and a quote, and both are yours to keep, whoever builds it. If I do the build, the session is credited against it.
from €5,000Fixed-scope buildThe architecture, the first working version and the handover. Priced per deliverable, so the risk of the work running long is mine.
from €2,500ReviewA look at a system you already run: architecture, data correctness, where the AI is allowed to decide. You get a written report with what to fix first.

How a build runs

01 · ScopeDecisions before codeEvery open question gets an answer, or gets marked out of scope, before anything is built. Each deliverable gets a price and an acceptance test we agree on up front.
02 · BuildThe first working versionThe model does judgment, deterministic code does correctness. Anywhere money or records are involved, the numbers are computed and checked, never generated.
03 · HandoverYours to runDocumentation good enough for another engineer to take over, and the code and accounts in your name. Ownership moves to you on payment.

What I bring

12 yearsSoftware that holds up in productionAnyone can generate an app now. Making it survive real users, real data and the next engineer is where experience shows: clear boundaries, tests that check what matters, and code someone else can take over.
DesignCareful design before the first lineData models, failure modes and what happens when a dependency goes down, worked out up front. Decisions are written down so they can be checked later.
Full stackBackend, front-end, infrastructure and teamsFrom the database to the screen to the server it runs on. Lead engineer for five years, so also how a team ships it.
Finance dataBank-data and accounting pipelinesOpen banking feeds, statement extraction, reconciliation, and getting the result into the spreadsheet or system people already use.
AI productsLLM-backed products and agent memoryEvals as release gates, the model kept out of the arithmetic, a clear line on what it is allowed to decide, and memory that says when it has gone stale.

What I've built: Qaravel

QocoaReads bank statements, refuses when they don't add upOpening balance plus every movement must equal the closing balance, or the result is marked partial. No model in the extraction path. QorianderSyncs client banks into the accountant's own sheetEach account on a schedule, from exactly where it stopped, tied to the bank balance. In closed beta with a practice in Portugal. QashewA plan tried before it's livedScenarios drawn over real accounts. The assistant can argue with the plan, but only a person can save it. WritingThree exchanges died this year. The mess lands on accountantsWhy an exchange export can't be tied out the way a bank statement can.

Let's scope it.

Thirty minutes, no charge, to see whether it's a fit and which of the three shapes makes sense. Remote across EU timezones, based in Lisbon.

Book a call