Join the waitlist
Menu
Pay per signup

For products that sell themselves, pay per signup Dylan started.

Some buyers would rather try than talk. Dylan sends them to your signup page, and you pay for the work accounts that arrive from companies he wrote to.

Status: TestingWhat you pay for

A new account on your product, created by a person Dylan contacted, inside the attribution window in your plan.

Needs a connection from your signup system before launch.

Example: a timeline of two working weeks. Dylan emails Maya, VP Operations at Nordfeld Logistics, on Mon 19. The attribution window, whose length is set in your plan, runs from that day to Tue 27. Maya signs up on Thu 22 with the address Dylan wrote to, inside the window, so the signup counts.
You decide what counts

Pay for the signups Dylan started.

A signup is billed only when it meets every part of the matching rule. The list of what is never billed comes before the price.

The matching rule

  1. A new account

    A trial, a free plan or a demo request on your product, whichever your plan names.

  2. Started by Dylan

    Created by a person Dylan contacted, inside the attribution window your plan sets.

  3. A match

    The signup email is the address Dylan wrote to, or a work email at the contacted company's domain when your plan allows domain matching: one per company, unless your plan says per user.

  4. Inside your definition

    The person is inside your definition's company and title range.

A stricter event can be the default in your plan: an activated signup, counted at the first action you name.

Never billed

  • Free-mail addresses
  • People already in your CRM or user base at first contact
  • Companies Dylan did not contact in the window
  • Test and duplicate accounts
  • Accounts deleted within 72 hours
The price

Price set in your plan

  • Prepaid credit, 72-hour disputes, credit-only refunds.
  • Needs a connection from your signup system before launch.

The default offer is pay per held meeting, with its prices on the pricing page.

Status: Testing

We are testing this way to pay with a small group. The price is set in your plan. Join the waitlist and we will tell you when it opens.

How it works

From the first email to a signup on the ledger.

The plan, the approvals and Dylan's rules are the same as for held meetings. What changes is the event: an account on your product, not a call.

  1. The same plan and approvals

    You write the definition. A person at Belkins reviews the plan, and you approve the first emails before anything is sent.

  2. Connect your signup system

    Before launch: a webhook, a Stripe or HubSpot event, a Dylan short link in your form, or a weekly export during the test. You upload your current users, so they are never billed.

  3. Dylan writes and sends

    From his own mailboxes, as an AI agent working for you, pointing people who would rather try than talk to your signup page.

  4. The window runs

    Each person Dylan contacts opens an attribution window, as long as your plan says. A signup inside it counts, whatever the last click.

  5. You read the ledger

    Every match is on the ledger: the email sent, the signup, exact or domain. You have 72 hours to dispute each ledger.

The match ledger

Every signup on one ledger, with the reason.

A signup counts only inside the window, from the person or the company Dylan wrote to. Everything else stays on the ledger, marked not billed, so you can see why.

Example: Dylan emails Maya, VP Operations at Nordfeld Logistics, on Mon 19. The window runs to Tue 27. Her signup on Thu 22 from the address Dylan wrote to counts. Jon's signup on Thu 29 came after the window: not billed. A signup from a current customer: not billed.
Maya, VP OperationsNordfeld Logistics
Example

Drag the signup along the days, or focus it and use the arrow keys.

Counts

  • Passes: Dylan wrote to this person
  • Passes: Signed up inside the window
  • Passes: A work email that matches
  • Passes: Not already your customer

Match ledgerExample
  1. Maya, VP OperationsEmail Mon 19 · signup Thu 22 · same address
    Counts
  2. Jon, Head of DataEmail Mon 19 · signup Thu 29 · after the window
    Not billed
  3. Ops lead, Fenwick HaulageIn your user base at first contact
    Not billed: your customer
Checked and disputed

Matched against your data, written down in advance.

This way to pay needs data from your side, so your plan requires it before launch. Dylan matches each signup event against his send log.

The attribution rule is written in advance: contacted by Dylan inside the window counts, whatever the last click. Dylan publishes a match ledger, with the email sent, the signup and the kind of match, exact or domain.

Silence confirms. Disputes come back as credit.

Dispute any match that is
  • From a company Dylan did not contact
  • Outside the window
  • From a free-mail address
  • Already your customer
  • A test or duplicate account
  • Deleted within 72 hours

The same rules on every way to pay.

  1. Your definition comes first

    You write the meeting definition before launch: the titles, company sizes and regions that count.

  2. You approve before anything is sent

    Nothing is sent before you approve the plan and the first emails.

  3. What is never billed

    Free-mail addresses, people already in your CRM or user base, companies Dylan did not contact in the window, and test or duplicate accounts are never billed.

  4. 72 hours to dispute

    72 hours to dispute any billed event, with fixed reasons. Silence confirms. Disputes come back as credit.

  5. The stop rule

    If 1,000 contacts bring no positive reply, Dylan pauses, tells you what he heard and proposes a new angle.

  6. Your domain stays out of it

    Dylan says he is an AI agent in the first line of every first email. He sends from his own domains, or from a partner's, never from the domain of the company the meetings are for.

Questions

Questions about paying per signup.

Do I need to connect my signup system?

Yes, before launch. A webhook, a Stripe or HubSpot event, a Dylan short link in your form, or a weekly export during the test. Without one, this way to pay does not fit.

Do free-mail signups count?

No. A signup from a free-mail address is never billed, even from a person Dylan wrote to.

Do my existing users count?

No. The export of your CRM or user base that you upload before launch is the baseline, and anyone on it at first contact is never billed.

Does a link in the email track it?

A Dylan short link can carry the signup into your form, but matching does not depend on it. A signup counts when the address or the company matches, whatever the last click.

How long do I have to dispute?

72 hours from each ledger, with a fixed reason. Silence confirms. Disputes come back as credit.

Does Dylan say he is an AI?

Yes, in the first line of every first email. Dylan's. He writes as an AI agent working for you, from his own domains. Your domain never sends a cold email.

Do you promise a number of signups?

No. We are testing this way to pay, and we make no promise about signup volume.

Want to pay this way?

Pick Pay per signup on the waitlist. Picking a way to pay tells us what you prefer; it commits you to nothing.

Join the waitlist