Introducing dpkit Terminal and TypeScriptSee the announcement

Vertical CRM

Mycarro

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.

capturemycarro.app
The Mycarro car search engine as it runs today, searching across its live Portuguese listings.
Mycarrocar marketplace and dealer CRM

What it is

A used-car marketplace, live in Portugal. It aggregates listings from across the market, normalises them into one consistent shape, and lets buyers search the result as a single catalogue instead of a dozen incompatible ones — with a dealer back office behind it for the businesses on the other side.

Why it exists

Buying a used car means opening the same search on five sites and reconciling the answers yourself. The listings already exist; what does not is a single view over them trustworthy enough to decide from. The hard part is not the search box — it is that every source describes the same car differently, with different model names, different trim conventions and different ideas of what counts as mileage. A search engine is only as good as the normalisation underneath it.

Our part in it

We designed and built it end to end — the ingestion and normalisation layer, the data model, the search infrastructure, the web application, the mobile app, and the dealer platform for leads, inventory, invoicing and commissions. One team owned the whole stack, which is why the data layer and the interface agree about what a car is.

What we can build for you

Web application development

Data layer through to interface: search, integrations, background jobs, and the infrastructure to keep it running.

Full-stack web applications · Typed APIs · Durable workflows · Container orchestration

Multi-platform products

One product across a consumer site, an operator dashboard, a mobile app and partner microsites — sharing one data model, so they cannot drift apart.

Full-stack web applications · Mobile & desktop · Typed APIs · Identity & access

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.

Transactional databases · Identity & access · Typed APIs · Full-stack web applications

Mobile app development

iOS and Android from one codebase, sharing types with your backend so the two cannot drift apart. Through the stores, or over the air.

Mobile & desktop · Typed APIs · Identity & access

What we build it on

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

  • Columnar dataframes instead of ad-hoc scripts, so a million rows costs what a thousand does.

  • Polite, resumable crawls that fail loudly instead of quietly going empty.

  • Multi-step processes that resume exactly where they stopped after a crash or a deploy.

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

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

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

  • Tokens, primitives and accessible behaviour, so the tenth screen looks like the first.

  • Locale in the URL, copy in catalogs, and hreflang that only advertises pages that exist.

  • Native apps sharing the web product's types and rules instead of forking them.

  • Declared infrastructure on rented metal, for when a product outgrows a serverless bill.

  • Structured logs, real error reports, and analytics that need no cookie banner.

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 projects
Get a quote