Skip to content
akafal
All work
Prototype2026

DAPIOS: fixed-operations diagnostics for dealerships

A dealership enters its monthly statement, and DAPIOS turns it into KPIs, diagnostic findings and actions ranked by their value.

Year
2026
Role
Product build, with a partner from the dealership world
Approach
Next.js · React · TypeScript · Tailwind · next-intl · Drizzle ORM · Better Auth · Supabase · Vercel

The problem

The service and parts side of a car dealership produces a monthly financial statement full of numbers and very little interpretation: what the figures mean, where the department stands and what to do first.

The constraint

A dealership's figures are private, so each organisation is isolated in the database itself and access is by invitation only. Statements also arrive in different formats depending on the manufacturer.

What I did

DAPIOS is a dealership fixed-operations product I'm building with a partner from the dealership world. It covers the service and parts side of a dealership, and it is for the fixed-ops manager and the consultant who reviews the numbers with them.

A dealership enters its monthly financial statement in a structured form. The form saves drafts and partial work, marks a month as submitted, and has field maps for several manufacturers' statement layouts.

From that entry, three engines run:

  • a KPI engine that computes the department's key indicators;
  • a diagnostic engine that raises findings from them;
  • data-quality checks that flag figures which do not hold together.

The result is a cockpit: benchmarks, findings, reconciliation and a print view, with actions ranked by their value.

Underneath, it is multi-tenant. An organisation owns its rooftops (its individual dealerships) and can create, retire and switch between them. Postgres row-level security keeps each organisation's data apart, and tests prove the isolation. Sign-up is closed, so access is by invitation only, and the interface runs in English and French.

It is in testing. No dealership uses it and none pays for it. The public page at dapios.com is a coming-soon page.

The outcome

DAPIOS is a prototype. The entry form, the engines and the cockpit are built and in testing, and no dealership uses it or pays for it. The public page at dapios.com is a coming-soon page.

Have a problem worth solving, or an idea worth building?

Book thirty minutes. We pressure-test it together and you leave knowing whether it is worth doing, roughly what it takes, and whether I am the right person to do it. If I am not, I will tell you who is.