Urverk

Work

How we deliver.

Fixed scope, verified builds, and outcomes you can reproduce — a method, not a promise.

The method

  1. We begin by fixing scope. What the work is, what "done" means, and the milestone dates that mark the way there — all written down and signed before a line of code is built. Fixed scope is what makes a fixed price and a real guarantee possible.

  2. We build AI-accelerated, which means fast, and verified, which means every change is checked before it moves forward. Speed without verification is how most AI software ships broken; here the check is part of the build, not a step anyone is allowed to skip.

  3. Delivery runs through Assay, the studio's proof layer. Evals, tests, and security and dependency scans run on your own project — not a demo, not a staging copy — and every number the report carries is one you can rerun yourself. The proof is a reproducible artifact you own, not a summary you take on faith.

  4. We close on outcomes you can measure. What shipped, whether it met the signed milestone, and how it has behaved since are numbers you can reproduce yourself. A result you cannot check is not a result the studio will claim.

Dogfooding

The studio runs its own operations through Assay.

Assay is infrastructure, and infrastructure earns trust by being used. The studio runs its own delivery — scoping, build, and verification — through the same proof layer that ships client projects. The evals, tests, and security scans that check your work check the studio's work first.

Assay measures rather than markets. The rule is simple: only measured, reproducible numbers get published — and the panel below is the studio running Assay against this very repository, real figures you can regenerate yourself. Client delivery metrics are held to the same rule: they appear once a shipped engagement produces numbers you can reproduce, and not before.

A view into Assay

What Assay shows you.

This is Assay's own proof run against this repository — the same report a client receives for their project, only here the subject is the studio itself. The numbers are real and reproducible: a committed snapshot, stamped with the date and commit it was generated from, regenerated on every ship.

Evals

  • 2 suites green
  • Studio operator evals (deterministic subset) — PASS
  • Studio intake evals (deterministic subset) — PASS

Tests

  • 8 suites green
  • Site quality gate (index) — PASS
  • Site quality gate (all pages) — PASS
  • Assay unit tests — PASS
  • Studio operator unit tests — PASS
  • Studio intake unit tests — PASS
  • Session-continuity restore tests — PASS
  • Snapshot-freshness comparator tests — PASS
  • Agency ops dashboard tests — PASS

Security & dependency scans

  • 0 findings across 294 tracked files
  • 0 third-party imports across 95 modules; no dependency manifest present

Milestones

  • 10 met
  • 0 in progress
Generated 2026-07-21 UTC at d076811 — full report

What the panel means for you

The same gate we run on ourselves runs on what we hand you.

The panel above grades the studio's own repository. The checks are green because the studio holds its own work to the bar before it asks to hold yours to it. When we build your system, that identical gate runs against your project — the evals, the tests, and the security and dependency scans point at the code you will own, not at a demo or a staging copy.

What you get is proof you can act on without taking anyone's word for it. Every claim in your handover report — what was built, what passes, what changed since the last milestone — is a command you can rerun on your own machine and watch return the same result. A number you cannot reproduce is not a number the studio publishes; the report exists so you never have to trust one on faith.

Delivery ledger

The record we keep in the open.

What every engagement will record. Rows appear only after delivery, with numbers you can reproduce — never as samples.
Engagement Scope Milestones met On-time % Defects post-ship
The ledger opens with the first client engagement. No rows are shown until real, reproducible numbers exist to fill them.

Founding clients

The first engagements get disproportionate attention.

Early clients work directly with the people building their system, and they get more of that attention than later ones will. The guarantee is in force from the first milestone — the automatic 10% credit applies to the first signed date as much as the hundredth.

Start with a Pilot