Early access

It isn't available yet. This list hears first.

There is nothing to buy or book here yet. What exists is the deployment behind this site, a resident agent you can talk to on the home page, and one inbox at Duval Software. Leave an address and you hear when that changes — before it goes anywhere public, and from a person rather than a sequence.

The list

Email is the only required field. The rest helps us reply with something useful instead of a form letter.

Your address goes to one inbox at Duval Software. That's it.
Plain terms

What this list is, and isn't.

A waitlist is a promise in both directions. Here is ours, in full.

What you get

First word, from a person.

When there is something to hand you — a deployment to try, a walkthrough, an update worth reading — you hear before it goes anywhere public. If you wrote something worth replying to, you get a reply. That is the whole promise.

Why the use-case line matters

The system is built around one memory and one approval rail. Knowing whether you'd point it at a pile of recordings, a shared inbox, or a fleet of background workers tells us which part to show you first.

What you don't

No drip. No call. No sharing.

No marketing sequence. No sales call. Your address is not handed to a tool, a list, or a partner. It sits in one inbox at Duval Software, and a note to that same inbox removes it.

What the dollar figures on this site mean

They describe what the system costs to run — the default fifty-cent daily worker budget, the five-dollar Deep Think, the ten-to-twenty-dollar Shipwright build, the twenty-five-dollar money line — not what anyone is charged.

Who this is for

Three kinds of people.

Teams drowning in recordings and threads nobody reads. Operators who want agents that ask before they act. Engineers who want to see the architecture before they believe a word of this — start there.

What "ask before they act" means

Agents can search, summarize, draft and propose. Anything with a real-world effect — an email, a calendar move, a merged pull request, a new agent, a paid build — lands on an approval tray as a card with the exact payload that will run. Nothing executes until a person resolves it, and what is in the fields at approval is what runs.

Not sure yet?

Ask Jeffery on the home page — he remembers the whole overview and will say plainly when he doesn't know something. Jeffery is this deployment's resident agent; every deployment names its own.

Talk to Jeffery → Read the architecture →