URVERK

Your business, like clockwork.

Urverk builds the AI and automation that runs the work you do by hand — on time, every time, without you pushing the buttons.

Som ett urverk. Urverk is the Swedish word for clockwork — the word inside "runs like clockwork." We build the mechanism; you read the time.

See how it runs

What the work runs on

Rigor

Most software built with AI ships unverified. Ours ships with proof. Every change runs the same checks — evals, tests, security and dependency scanning — before it reaches you.

Transparency

You watch the work as it happens, not a summary after the fact. Prices are published, scope is fixed in writing, and the proof layer runs where you can see it. Nothing about how we work sits behind a call.

Guaranteed outcomes

We commit to milestone dates and put money behind them. Miss one for reasons attributable to us, and the credit is automatic — no claim to file. The incentive to deliver on time sits with us, where it belongs.

What we build

From named assistants to full systems.

Persona-fronted assistants your customers talk to, intake and lead triage, back-office automation, chat and voice agents, multi-step AI workflows, and custom systems — every one owned by you from day one, measured against your own baseline, and delivered under the guarantee.

See what we build

The proof layer

Every project ships through Assay — our proof layer.

Assay is the infrastructure that checks the work. It runs on your project, and hands you a report whose every number you can rerun yourself — the same checks we run on our own work, reproducible on your machine, not a summary you take on faith. Assay has no avatar, no pronouns, no persona; it is a record of what was checked and when.

  • Evals Behavior measured against the intent we agreed on, not just against whether it runs.
  • Tests Tests written to exercise each change and pin the behavior that matters.
  • Security and dependency scanning The stack and its dependencies checked for known vulnerabilities on every build.
  • Delivery observability A clear record of what shipped, when it shipped, and how it has behaved since.

Latest run: PASS · generated 2026-07-21 UTC at 4ef723f · read the full report

The difference in practice

How an engagement compares

What differs A typical engagement With Urverk
Pricing Prices arrive after a discovery call, and can move once the scope is understood. Every price is published, and it holds the same before and after you make contact.
Delivery proof You are asked to trust that the work was reviewed and tested. You watch Assay run the checks on your own project, as they happen.
A missed date A slipped milestone opens a conversation about who is at fault. A slipped milestone applies an automatic 10% credit — nothing to file.
Who owns the code Ownership of the code and IP is negotiated as the engagement ends. You own all of the code and IP from day one, in writing.

Pricing

Published, because a guarantee you can read beats a call you have to book.

Fixed scope, fixed starting prices, and terms that do not change once you talk to us.

Pilot

Inbound intake and lead triage — one workflow, fixed scope, 30 days.

from $6,000
Build

A production system, scoped and delivered end to end.

from $8,000
Care

Monitoring, optimization, expansion — scope fixed in writing before it is sold.

from $1,500/month

A founding-client price applies while the studio's casebook is empty: the first two engagements book the Pilot at $4,500, labeled as such in the statement of work. Same scope, same proof, same guarantee — the discount is the price of being first, not a lighter build.

The guarantee

Miss a signed milestone date for reasons attributable to us and you receive an automatic 10% credit of that milestone's fee. No dispute process.

A description, not the contract: the operative terms live in the engagement agreement you sign.

Read the full terms

Start here

Start with a Pilot.

Tell us what the work is and what "done" looks like. We reply within one business day.

Start with a Pilot