01

Backend & APIs

We design and build services that survive the first release: explicit contracts, a data model that matches the domain, and deployment notes that another engineer can follow.

  • API design and versioning
  • Data modelling and migrations
  • Background jobs and queues
  • Tests, observability, and runbooks
GoPythonPostgreSQLSQLite
02

Data & Automation

Import, clean, index, and report. We build small pipelines that remove manual steps and leave a readable trail when something goes wrong.

  • Importers and one-off migrations
  • Search and indexing (SQLite FTS, Postgres)
  • Scheduled jobs and reports
  • Data quality checks
PythonSQLqueuescron
03

Internal Tools & Web Apps

Focused tools for the people who run the business. Server-rendered pages, simple forms, and no client-side framework unless the interaction truly needs one.

  • Admin panels and dashboards
  • Workflow and approval tools
  • Reporting interfaces
  • Small public-facing web apps
TypeScriptserver-renderedSQLitePostgres

How a project runs.

01

Frame

A short written brief: the problem, constraints, and what is explicitly out of scope. No discovery theatre.

02

Build

Small slices, working software early, decisions recorded next to the code. You see progress before the end.

03

Handover

A runbook, the source, and a walkthrough. The system should be operable without a permanent retainer.

Engagement formats.

Fixed-scope project. Best for a defined API, an importer, or an internal tool. The scope is written down before the work starts.

Monthly support. A small block of engineering time for maintenance, improvements, and the questions that appear after launch.

Technical audit. A focused review of an existing service: data model, deployment, failure modes, and the shortest list of fixes.

Write to hello@nmzz.online