Studio

A small number of projects,
run by the partners throughout.

The people making the architectural decisions are the people in the room with you, from the first meeting to delivery. There is no account-management layer, and no handoff to another team once the contract is signed.

D2Cust Daniel & David · Custom User Systems & Technology
DA
Daniel
Partner · Architecture and discovery

Leads discovery and the data model. Owns the scope boundaries and the architectural decisions that are settled before development starts.

  • Discovery
  • Data model
  • Architecture
DV
David
Partner · Infrastructure and integrations

Owns infrastructure, integrations and data migration from the systems already in place. Leads go-live and keeps the system stable after it.

  • Integrations
  • Data migration
  • Infrastructure

Working principles

Four rules that do not change between projects.

01

Scope before price

The proposal derives from an agreed discovery document. A scope change is documented and priced, not argued about mid-project.

02

Full ownership of what we build

The code, the databases and the infrastructure are in your name from day one. No vendor lock-in.

03

A working environment early

A version you can run exists from the first iteration, not only at delivery.

04

Documentation is part of delivery

Runbook, data schema and operational documentation ship with the system, not after it.


Contact

Two ways to start.