Contact

One email. One business day.

The terms are the same before and after you talk to us — so there is nothing to negotiate before you write.

How to reach us

Email the studio.

hello@urverk.com

Tell us three things: what the work is, what "done" looks like, and your timeline. Enough for a real answer instead of a request for a call.

You get a reply within one business day.

Prefer to talk? Say so in one sentence and you'll get times within a business day — we bring the metric we'd measure, not a pitch.

Rather fill in the blanks?

The same three things, structured.

This composes the email in your own mail app and opens it there. Nothing is sent to a server — you read it and press send yourself.

No mail app? Write to hello@urverk.com directly.

No trackers, no analytics, no cookies — nothing here watches you. Every page is hand-written and served as a plain static file. Open View Source and read every line.

Your data

Where your data lives.

Before: this page. It collects nothing — you can read every line in View Source.

Inside an engagement, the same by design. You run on your own API keys and accounts (BYOK), so your data moves through your provider under your terms. You own all code and IP, no lock-in. The studio keeps none of your business data after handover, and regulated data — PHI, HIPAA — is out of scope pre-launch.

Before you ask

Questions worth answering up front.

Who owns the code?
You do — all code and IP, from day one, in writing. Not something the studio holds back to negotiate at the end.
How does pricing work?
Scope and price are agreed together in the first conversation — scope first, number second — and written down before anything is built. Once we agree it, it holds.
Can we run on our own API keys?
Yes — bring your own keys to run on your own accounts and budget.
Can you build a persona-fronted assistant?
Yes — a named, branded assistant your staff or customers talk to, the persona owned by you. The system underneath is measured like any other build, and always discloses that it is automated.
What is the proof run?
Every project ships with a proof run — the tests, evals, and security checks that prove the work, running where you can watch them and rerun them yourself. It is infrastructure, not a person: no avatar, no face. Like turning a watch over to its open caseback, the mechanism is there to see.
Where is the studio?
California, remote-first. The terms read the same wherever you are.