Fintech · hospitality · data · AI agents

Systems that don't lose a payment, a booking or a record

Your product depends on providers that fail: banks, KYC and custody platforms, hotel PMS and POS systems, AI models. A small team of named engineers builds the system around them so nothing goes missing, and the guarantees are written into the contract.

Proof · client under NDA

Banking orchestration for a European payment platform, in production

One system of record across Sumsub onboarding, Fireblocks custody, a double-entry ledger and banking-as-a-service partners, so every customer, transfer and balance has one provable answer.

Read the case

Data at scale too: our own product Mycarro matches about 5.9 million live car adverts from 10 countries into about 3.1 million cars, each with a market price. Read the data case

Built on

  • Sumsub
  • Fireblocks
  • Double-entry ledgers
  • Reconciliation
  • Banking-as-a-service
  • Web data collection
  • Record matching
  • Valuation models

What we build

One senior team, four kinds of system

Different industries, the same hard part: outside providers that fail, and money, bookings and records that still have to add up.

All work
Fintech

Fintech systems where money and compliance meet

Ledgers and reconciliation, KYC/KYB, custody and banking-as-a-service, built to pass your partner bank's review.

Hospitality

Hospitality integrations and operations software

PMS and POS integrations and staff tools for hotel groups, restaurant groups and hospitality software companies, from a team that owns two hospitality products.

Data

Data platforms built on public web data

Collection at national scale, one record per real thing, valuations and indices on top. Our own Mycarro matches about 5.9 million adverts into about 3.1 million cars.

AI agents

AI agents inside the systems you run

Agents that triage, reconcile and reply inside fintech, hotel and sales systems, with permissions and audit trails.

Why a small team abroad is a safe choice

What goes wrong with agencies, and what our contract says instead

All contract and security terms
The seniors pitch, juniors build

The people you meet are the people who build

Your proposal names the engineers who will do the work, and you meet them before you sign. A key-person clause means nobody is swapped without your written consent.

The agency keeps the code

Your repository and accounts from the first commit

Code, cloud, app-store and domain accounts are in your name, and we work inside them from day one. The contract assigns the IP to you in the present tense ("hereby assigns"), so there is no later transfer to wait for. Portuguese law (Decree-Law 252/94) also treats commissioned software as the client's by default. lawyer to confirm DL 252/94

The agency disappears

Nothing depends on us staying

You pay per milestone, for work you have seen running. Everything lives in your accounts, and every milestone ends with a written handover: architecture notes and runbooks your next engineer can follow without us.

Code nobody can maintain

Reviewed work, under a 90-day warranty

A second engineer reviews every change before it merges, and code written with AI tools is read line by line (our AI-use policy). Paths that touch money and data have automated tests. A written 90-day warranty covers defects in our work.

How a project runs

From the first call to a system your team owns

  1. Week 0

    Call

    30 minutes with an engineer who would work on it, with a mutual NDA first if you want one. You get an honest yes or no.

  2. Weeks 1–2

    First step

    A fixed-price review or audit of what you have. You get the findings, a plan and a fixed quote for the build.

  3. Every week

    Build in the open

    The named team works in your repository and shows you working software every week, not status reports.

  4. Each milestone

    Handover

    Architecture notes, runbooks and an access review at every milestone. You pay per milestone, for work you have seen.

  5. 90 days

    Warranty

    We fix defects in our own work free of charge for 90 days after release. After that, monthly care is there if you want it.

Start small

A fixed-price first step, credited to the build

A short paid step shows you how we work and what the build will cost before you commit to it. If you go ahead, its fee comes off the build.

duration

Hospitality integration audit

How your PMS, POS and operations tools exchange data, where sync breaks and what it risks, from overbookings to wrong reports. You get a written report with every fix priced.

pricecredited to the build
duration

AI pilot review

For an AI pilot that works in a demo but not in production: what blocks it (data, permissions, evaluation, running cost), and a plan to ship it with its price.

pricecredited to the build

Also in the toolbox

CRM and automation work, as part of the systems above

CRM & automation

CRM integration

HubSpot, Salesforce and Pipedrive connected to your billing, product and operations systems, with automations that keep working after their builder leaves.

Questions

What buyers ask a team in Portugal

Why a team in Portugal?

We work on the same clock as London, under EU law and GDPR. Portuguese law (Decree-Law 252/94) treats commissioned software as the client's by default, and our contract assigns it to you as well. lawyer to confirm DL 252/94 You get experienced engineers priced close to a UK contractor, with no agency layer on top.

Who owns the code and the IP?

You do, from the first commit. We work in your repository and your accounts, and the contract assigns the IP to you in the present tense, not at some later date.

Who will actually work on our project?

The engineers named in the proposal, and you meet them before you sign. A key-person clause means nobody is swapped without your written consent.

How do time zones work for a UK or US team?

We work on Lisbon time, which is the same clock as London: Mon–Fri, 08:00–18:00 UK time. That leaves about four working hours a day in common with the US East Coast. You get a demo of working software every week and a short written update every working day.

What contracts do you sign?

A master services agreement with a statement of work for each project, or your own paper if you prefer. A mutual NDA before we see anything, and a GDPR data processing agreement. US clients get a W-8BEN-E from us. Which law governs the contract is answered on Contracts & security.

How do we pay?

The fixed-price first step is paid upfront. Builds are billed by milestone, after you have seen the work running. Monthly care, if you want it, is billed at the start of each month. We invoice in euros, pounds or dollars.

Free 30-minute call

Tell us what has to work, and by when

You talk to an engineer who would work on it, not a salesperson. You leave the call knowing what it would take and what the first step costs, or we tell you that you don't need us.

Or write to us
info@jobsdone.pro
Lisbon time: the same clock as London, 4–5 hours ahead of New York

We answer within one working day. We sign an NDA before seeing any code.

Thank you, it's with us

An engineer will reply within one working day with a few times for the call. If it's urgent, email info@jobsdone.pro.