DDueted

Six situations. Find the one that sounds like yours.

Each one starts with what actually goes wrong, because that is the part you already recognise. What Dueted does about it comes second.

One person, a whole portfolio

You own dozens of names and each has its own set of likely buyers. Worked from a file, you lose track of who was emailed, when the follow-up is due, and which reply belongs to which name. The bookkeeping grows faster than the portfolio does.

What happens instead

  • One pipeline across every domain, with a daily list of exactly who to contact and who is overdue.
  • A campaign whose audience is a rule rather than an import, so newly researched contacts join it on their own while it is active.
  • Follow-ups that reply inside the existing thread, scheduled for you, with the next due message highlighted.
  • Replies matched back to the lead they belong to, so nothing arrives without context.

A team on one pipeline, without stepping on each other

More than one person works the leads. You need control over who can send, who can only research, and who just watches. And you cannot risk two people emailing the same buyer in the same week.

What happens instead

  • Four roles enforced in the database, not hidden in the interface: a researcher works leads but cannot send, a viewer cannot change anything, and the rules hold through the API too.
  • Assign a lead to a teammate, comment internally, and read a workspace activity trail of who did what.
  • The same company prospected from two of your domains is flagged on both, so nobody sends twice.
  • A campaign cannot start sending until someone approves the copy and the audience together.

Inquiries from your for-sale pages, tracked

Your parked pages generate interest, but it arrives as scattered mail with no context and no follow-up. A buyer who was ready on Tuesday goes cold while you dig for the thread.

What happens instead

  • Every inquiry from a for-sale page lands in the pipeline as an inbound lead, ready to answer.
  • The daily attention list puts waiting inbound buyers first, before they cool off.
  • A visit-to-form-to-inquiry funnel per page, so a page with traffic and no submissions is visible rather than assumed fine.
  • The page itself is data: headline, blurb, whether the price shows, and the buy-now link are fields you edit and save.

Handing research to someone without handing over the keys

You want help building lead lists. You do not want an assistant sending mail as you, or editing your prices, or deciding that a domain on legal hold looks like a fine prospect.

What happens instead

  • The researcher role adds and works leads but can never send or touch a domain.
  • Unverified research stays visibly unverified, and an audience rule can require a verified contact before anyone is enrolled.
  • A lead on legal hold refuses to be emailed, and taking it off hold is owner-only. Both are enforced by the database.
  • Every change is on the activity trail, so you can see what happened without watching it happen.

Keeping a live deal moving to a number

Once a buyer replies, the conversation drifts across your mail client and you lose sight of the ask, the last offer, and the number you will not go below.

What happens instead

  • Ask price, latest offer and a walk-away floor on every lead, with portfolio totals across them.
  • A suggested range from the lead score, offered as a starting point rather than dressed up as a valuation.
  • Deals idle for ten days or more are called out on the pipeline health read, with the next step named.
  • The whole thread stays beside the deal, so the history and the numbers are on one screen.

Wiring the pipeline into what you already run

You have other systems, and you do not want a CRM that is an island you copy and paste out of.

What happens instead

  • A REST API with scoped keys over leads, domains, conversations and messages.
  • Webhooks on all six events: replies, mentions, assignments, inquiries, offers and a domain selling. HMAC-signed so the receiver can verify them, retried with backoff.
  • Slack and Discord notifications formatted natively for each, so the team sees activity where they already are.
  • Export to CSV or JSON on demand, and imports that append rather than overwrite what is already there.

Whichever one is you.

Import your domains and connect a mailbox. Everything above is on from the first day.

Start freeFree while in beta · no card required