Introducing dpkit Terminal and TypeScriptSee the announcement

What we build

Internal tools & back-office systems

The internal tool your industry actually needs — leads, deals, inventory, invoicing, permissions, an audit trail. Built around how you work rather than around a template.

starts fromdatist · pricing
€5,000
fixed price from
2 weeks
delivery from
Both agreed in writing before anyone starts

What it is

The internal system your business actually runs on, for when the off-the-shelf options are either too generic to fit or priced per seat for features you will never open. Leads and deals, inventory, invoicing, contracts, commissions, who is allowed to do what — and a record of who did it.

What you get

Software shaped around your process instead of a template you bend to fit. Roles and permissions that can be granted temporarily, with a record of who granted them, why, and when they expire. An audit trail you can query rather than a log file nobody reads. And reporting on your own numbers, not a vendor's idea of them.

How we build it

One Postgres database as the system of record, with the permission model enforced centrally rather than re-stated on every screen. We have built this twice over: a dealer platform covering inventory, leads, deals, customers, invoices and commissions — built and awaiting release — and the operations dashboard of a regulated financial services platform, where reviewers work cases under permissions the compiler checks.

Where we have built it

capturemycarro.app
The Mycarro car search engine as it runs today, searching across its live Portuguese listings.

Mycarrocar marketplace and dealer CRM

A used-car marketplace live in Portugal. Consumer search over listings gathered from across the market, a dealer back office for leads, inventory and invoicing, and a mobile app — built end to end.

we built

under NDA
Work we cannot show
ND

NDASwiss fintech platform MVP

Lead architect on a regulated financial services platform: a contract-first backend, an operations dashboard, and an iOS and Android app. MVP delivered.

client · NDA

What we build it on

  • One Postgres per product, with the schema and the queries deliberately owned by different tools.

  • Sign-in, organisations and permissions bought in rather than rebuilt badly.

  • One definition generating the server, the client and the docs, so drift is a build error.

  • Server-rendered React with typed routing and data loading in one project, not two.

Get in touch

Tell us what you need built.

We are a small team in Portugal, working London hours. A site, an app, an internal tool, or the platform behind them — start with a sentence about the problem and we will take it from there.

All services
Get a quote