Everything Dueted does, in the order the product does it.

Sourcing, then outbound, then what comes back. This is the reference: every line below is running in production, and nothing on this page is a roadmap item.

Sourcing

Where the names come from. Nothing downstream is trustworthy if this part is guesswork.

The prospect model

A contact, under a company, under a domain you own. The domain is the root, because the domain is what you are selling.

Research that cites itself: An agent finds the companies whose exact match .com your domain is, scores each one, and keeps every source it used. The run stays linked to the leads it created, so a score can be traced back to the evidence behind it.
Run history: Every agent run is stored with its full timeline and results. Closing the tab does not lose the work, and a run can be reopened and imported later.
Contact verification: A researched address is not a lead until someone checks it. Contacts carry an MX check and a separate human verification, and unverified stays visibly unverified rather than being quietly promoted to fact.
Imports that append: Paste or upload a list and it merges. Existing leads keep their status, dates, notes and deal figures, so a re-import can never overwrite the work already done on a row.
Duplicate flagging: The same company prospected from two of your domains is flagged on both, so the same person does not get two cold emails in a week from the same sender.

Domains and for-sale pages

The portfolio itself: what each name costs you, what you want for it, and the public page that sells it.

Pricing and floor: Ask price, buy-now price and a walk-away floor per domain, with registrar and renewal dates alongside them.
Landers you edit as data: Headline, blurb, whether the price shows, and the buy-now link are fields on the domain row. Changing a for-sale page is a save, not a deploy.
A storefront: Every active domain appears on one public storefront, built from the same table, with hidden names excluded.
Inquiries land in the pipeline: A buyer who fills in the form on a for-sale page arrives as an inbound lead, and the visit-to-inquiry funnel for that page is recorded.

Outbound

How mail actually leaves, and what stops it leaving when it should not.

Campaigns

A sequence, an audience defined by a rule, and an approval that covers both. Membership is computed, never uploaded.

Multi-step sequences: Email steps and wait steps in any order. Waits count in calendar days or business days, and each step carries its own subject and body with merge variables.
An audience rule, not a list: Scope a campaign to one domain or the whole portfolio, cap it per company, require a verified contact, exclude anything on legal hold. While the campaign is active a daily sweep enrols new contacts that match, with no re-import.
Exclusions that survive a rebuild: Removing someone writes an exclusion rather than deleting a row, so rebuilding the list never quietly puts them back.
Approval covers the rule: Approving a campaign approves the sequence, the copy and the rule together. Change any of them and the approval goes stale; nothing enrols against a rule whose approval is no longer current.
Threaded follow-ups: A follow-up step can send as a reply inside the same conversation, resolved against the real message id at send time. It carries no subject, because a subject is what would make it a new thread instead of a reply.
Pause, resume, relaunch: Draft, approve, activate, pause and return to draft are all repeatable. Once a campaign has mailed someone, its content is frozen.
Stuck sends are visible: A send blocked by a terminal queue job is listed with the reason and can be requeued. One that may already have reached SMTP is listed too, with the refusal spelled out, because hiding it would make a missing email invisible.

Mailboxes

Sending infrastructure you watch, not a setting you filled in once. Rotation, warmup and health are monitored per mailbox.

Rotation: Add as many sending mailboxes as you like. Campaigns rotate across every enabled one, least recently used first, so volume spreads instead of concentrating on one address.
Per-mailbox daily caps: Each mailbox carries its own ceiling. Reaching it defers the remaining sends to tomorrow rather than failing them, and the screen says which is happening.
Warmup ramps: A new mailbox starts low and climbs to its full cap over a set number of days. The page states today’s effective ceiling and how long is left, so a cap of 200 sending 12 today does not read as a bug.
Bounce-rate health: Hard and soft bounces are counted over a rolling week. Below a minimum volume the product says there is not enough evidence to judge rather than calling the mailbox healthy.
Auto-pause is an incident: Crossing the bounce threshold pauses the mailbox and writes the reason. Sending never resumes on its own, because the cause is a list problem and it does not fix itself.
Encrypted per workspace: Credentials are encrypted at rest and readable only by the server. Mail leaves as you, on your own domain and reputation.

Sending by hand

For the deal you are working personally, rather than the campaign running in the background.

One at a time or a queue: Send a single message, or work the whole due queue with human-length gaps between sends and a daily cap counted from the real sends log.
A follow-up cadence: A first email and two follow-ups, each stamping the next follow-up date when you mark it sent, with the message that is due next highlighted.
House voice by default: Short, no hard sell, no em dashes, one soft ask. The drafts are editable and the angle is the exact match .com, not a pitch deck.
Legal holds refuse to send: A lead on hold cannot be emailed. The refusal is enforced in the database, so it holds through the API too, and taking a lead off hold is owner-only.

Pipeline

What comes back, and the numbers that decide what to do next.

Inbox

Replies come back into the product, threaded and attributed to the lead they belong to.

Threaded and matched: An incoming reply is matched to the right lead and threaded into its conversation, so the answer sits beside the deal instead of in a separate mail client.
Reply, reply all, forward: Answer from the same screen with templates, merge variables, an appended signature and attachments.
Snooze and follow-up: Snooze a conversation out of the way until a date, or set the follow-up date that puts it back on the list. Snoozed threads are filterable rather than hidden.
Which domain it is about: The conversation list names the domain each thread belongs to, because someone running six domains needs that before the name of the company.
A failed read says so: If conversations cannot be loaded the inbox says the load failed. It never renders an empty state that looks like having no mail.

Deals

A broker without money in the model has a contact list. The deal fields are first-class.

Ask, offer, floor: The price you want, the offer received, and the number you walk away below, on every lead, with portfolio totals across them.
A suggested range: A price range derived from the lead score, offered as a starting point rather than presented as a valuation.
Lead identity done properly: A lead is unique per domain, company and site, so the same company can legitimately be a prospect for two different names in your portfolio.
Comments and assignment: Internal notes on a lead, and an owner from your team. You can only post as yourself; that is enforced in the database.

Analytics

Aggregations over your own sends log. No projections, no benchmarks against other people’s numbers.

Reply rate per template: Reply rate by template and variant, which is the only thing that answers whether the rewrite was better.
Conversion funnel: Contacted to replied to won, with the open ask carried alongside it.
Pipeline health: A single read on how well the pipeline is being worked, with the highest-leverage next step named rather than implied.
Lander funnel: Visit to form to inquiry for every for-sale page, so a page that gets traffic and no submissions is visible.
Sent against your cap: How much went out today against the ceiling, and volume over the last two weeks.

Underneath

The parts that are infrastructure rather than screens.

AI, managed

It runs server-side on a managed model chain with fallbacks. There is no key to bring, and there is no key to pay for.

Draft a reply: A reply in the house voice, grounded in the actual thread and the actual lead.
Brief a lead: A short summary of where a lead stands and a suggested next step.
Suggest a price: A range for a domain, offered with the score it came from.
Ask your pipeline: A question answered from your own leads, from the command palette.
It never sends: AI drafts and suggests. It does not send mail, it will not invent a contact, and it refuses leads on legal hold.

The platform

Wire it into whatever you already run.

REST API v1: Leads, domains, messages and conversations, with scoped keys stored only as a hash.
Signed webhooks: Every delivery carries an HMAC signature so the receiver can verify it, with retries and backoff.
Slack and Discord: Notifications formatted natively for each: Block Kit for Slack, embeds for Discord.
Zapier and Make, via the API: Through the REST API and a generic signed webhook, rather than a dedicated app in either directory.
Export: Leads and domains to CSV or JSON whenever you want them.
Real mobile: A collapsible nav and card lists instead of a table cropped to a phone.

Guarantees that are enforced

The promises worth making are the ones the database keeps whether the interface cooperates or not.

Workspace isolation: Row-level security scopes every query to your workspace. It is not an application filter that a bug can bypass.
Roles checked fail-closed: Owner, broker, researcher and viewer are enforced in the database and through the API. A viewer cannot send; a researcher cannot touch domains.
Nothing sends twice: Once the mail server accepts a message, no path retries it. An ambiguous outcome is flagged for a human rather than re-sent, because the message may already be on the wire.
No browser data stores: The database is the only store. If it cannot be reached the app says so in red rather than pretending to save.

That is the whole surface.

No feature gates, no per-seat locks and nothing on this page waiting on a roadmap. If something here matters to you, it is running today.

Start free Why it works this wayFree while in beta · no card required