The prices, in the open.

What the Pilot includes

One workflow, fixed at the edges.

The Pilot is a single back-office workflow, inbound intake and lead triage, built against the channels and tools your firm already uses. What counts as in scope is fixed in writing before work begins. Anything outside it is a separate engagement, not an expansion of this one.

In the 30-day build

• Baseline measurement of your current intake, taken up front so the result is checked against your own numbers.
• The intake and triage build itself: capture, qualify, route, and first-respond across your existing web form, email, and phone-to-text.
• Integration with your existing CRM, inbox, and calendar, within the agreed scope.
• A milestone Assay report at each checkpoint, attesting what was built and that its checks pass.
• One round of tuning against the measured baseline, inside the 30-day window.
• A working session with your staff at handover — a walkthrough of operating the system, so the team adopts it, not just receives it.

Outside the Pilot

• A second workflow, such as proposal or quote generation. One at a time.
• Ongoing monitoring, optimization, and expansion, which is the Care tier.
• Model and API usage costs. You bring your own keys, so you hold your own budget.
• PHI or HIPAA-covered intake. Regulated-data handling is out of scope pre-launch.
• Human staffing, content, or marketing work.

Yours after launch

• The full source code, with IP assigned to you from day one.
• The runbook and architecture write-up needed to operate or hand off the system.
• Your own API keys and deployment, with no proprietary runtime you cannot self-host.
• Freedom to run, modify, or hand the system to another vendor. No lock-in.

Proof

Every milestone ships with an Assay report.

Each checkpoint hands you an Assay report, the studio's proof layer, generated against your delivered system. It attests what was built and that the delivered checks pass, measured against the baseline taken at the start.

What is real today is narrower, and stated plainly. Assay v0 runs its deterministic checks against the studio's own repository, the same exit-0 pass, exit-1 fail contract this site's quality gate uses. Its evals panel grades the studio's own operator and intake systems, the two eval suites shipping today; evals for your system join your report as the engagement ships them. There is no always-on client dashboard today, only a proof report handed over at each milestone. The current proof run is Assay checking this very repository.

Not for you if

When this is the wrong studio.

1. The target work has no measurable, repeating cycle. Without a high-volume, rule-driven workflow there is no baseline to measure and nothing for the guarantee to sit on.

2. You want an assistant that hides being automated, or one that impersonates a real person. Urverk builds persona-fronted assistants — but the persona is yours outright, the system under it is measured, and it always discloses what it is to the people it talks to.

3. The back office handles PHI or is HIPAA-covered. Regulated-data intake carries a liability surface that is out of scope for a solo studio pre-launch.

4. You will not grant measurement access. Proof requires measuring the baseline and the outcome inside your own systems, and without that there is only an unverifiable claim, which the studio does not make.

5. You are shopping for the lowest hourly bid. The model is a fixed base fee plus an automatic guarantee, priced on the outcome, never on billable hours.