Services
Services
Five ways to work together, from a one-off review to a long-term contract. Each one builds a different part of the same column. End to end, from the data model to the interface, one owner. No price list: every engagement starts with a call.
Architecture review
Part I · Fundamentum: the foundation and the measured plan
For teams whose backend has outgrown its first design. A review of services, data flows and boundaries, ending in a written plan: what to keep, what to change, and in what order.
You get
- A map of services, data flows and boundaries as they are today
- Risks ranked by what they cost you, not by how they look
- A written plan: keep, change, and in which order
Backend & data engineering
Part II · Scapus: the load-bearing drums
Node.js and TypeScript services (NestJS, Express, tRPC, GraphQL), PostgreSQL, and serverless on AWS: Lambda, SQS, DynamoDB, Athena. Proven on hundreds of terabytes in S3 and Parquet.
You get
- Services and APIs that the next team can read
- Data models and jobs that survive the next order of magnitude
- Query cost and run time measured, before and after
AI & LLM pipelines
Part III · Capitulum: the capital, with the core inside
From prototype to production: transcripts in, structured output out. Prompt design, multi-modal processing and caching, plus no-code tools so non-engineers can define what the pipelines produce. Since 2024 in UK financial advice.
You get
- A pipeline running on real, messy input
- Evals, so every prompt or model change is measured
- A person signs off before output becomes a decision
Product & UI/UX design
Part IV · Ornamenta: what people see and touch
For products where the interface and the system behind it should come from one hand: user flows, UI and a design system, designed together with the data model, so the screens match what the backend can actually do.
You get
- User flows and screens, tested on the real data model
- A design system in code, not only in a design file
- Screens that never promise what the backend can’t do
Senior engineer on contract
Part V · Machina: the crane, the one who builds it
A senior full-stack engineer embedded in your team, long-term or for a fixed scope. React on the front end when the product needs it. Invoiced by PaxCode, an EU VAT-registered company.
You get
- A senior engineer in your stand-ups and your repo
- Decisions written down as they are made
- B2B invoicing from an EU VAT-registered company
How an engagement starts
Three steps, no surprises.
-
01
A call
30 minutes about your system: what you’re building and where it hurts.
-
02
A written scope
What gets done, in what order, and in which form: review, fixed scope or contract.
-
03
The work
Decisions written down as they are made. Invoiced by PaxCode.
Contact
Not sure which fits?