Email’s New P&L: From Cost-Per-Send to a Revenue, Data, Outcome and Media Surface (Part 2)

Email Earns from Actions

The click-through was never a step. It was the leak.

Consider what happens when an email works.

A customer opens it. Something in the message is relevant enough that they decide to act. At that instant — and it is an instant, not a state — intent is at the highest point it will reach in the entire life of that message. Then the email asks them to leave.

They tap. A browser opens. A page loads, or partly loads. There may be a login. There may be a basket that has forgotten what was in it. There may be an address form, a card form, a one-time password arriving in a different application. Somewhere in that sequence, most of them stop.

The industry has a name for the gap between the click and the conversion and treats it as a fact of nature. It is not. It is a design decision made when email could not do anything except link out, and it has survived long past the constraint that produced it.

Pay-in-Email removes the leaving. Its principle is one line: the transaction should end where the attention begins. The customer completes inside the message — paying by UPI or a stored card, confirming a renewal, booking a slot, accepting a quote, finishing a verification step, making a donation, taking an upgrade. For most repeat relationships the brand already knows the customer, the product, the address and the payment method; the action does not need another journey, it needs a confirmation. Intent is captured at its peak rather than at the end of a sequence designed to lose it.

What completes in an inbox

The list is longer than most people expect, because a great deal of commercial activity is not discovery at all. It is completion of something already decided.

  1. payment of a bill, an instalment or an invoice
  2. renewal of a subscription, a policy or a plan
  3. repeat purchase of a known item at a known price
  4. booking or rescheduling against live availability
  5. completion of an application already begun
  6. a document, consent or verification step
  7. an upgrade, an add-on or a top-up
  8. a donation or a pledge

None of these needs a shop. All of them currently require one.

There is a second saving hidden inside the first, and it is larger than it looks. A customer who completes in the inbox has just proved they are reachable for free. They should leave the paid retargeting pool the same minute. The brand saves the transaction leakage and the reacquisition spend in a single action. That is Never Pay Twice, operating at the level of one customer on one Tuesday.

The second output: declared data

The same surface that takes a payment can take an answer.

Tell-in-Email captures declared data at the moment the customer is already engaged: a preference, a size, a renewal date, an interest, a consent, a piece of feedback, a choice between two service options. One tap, inside the message, with no form and no landing page.

Declared data is a different substance from inferred data, and the difference compounds. Inferred data is probabilistic, decays quickly, and grows more expensive to obtain every year as the identity layer of the open web degrades further. Declared data is exact, durable, consented — and, the part that matters commercially, it is the input the entire personalisation side of the architecture runs on. In the TWIN framework it is the I: individual data, given rather than guessed.

Key points: Pay-in-Email earns revenue now. Tell-in-Email earns the data that makes the next decision smarter. They are two outputs of one action surface, which is why they sit on the same rung and belong in the same section of the statement.

This is the literal content of the phrase Email for Revenue & Data. It is not a slogan about email mattering. It is a description of what a single Living Email produces on every open: a transaction and a signal.

The law that keeps the rung honest

There is a trap here and it should be closed before it opens.

The same Living Email can be sold two ways. Sold as a capability: the brand operates it, the vendor supplies the surface, and the vendor is paid for what the email can do. Or operated as an outcome: Progency runs it against a concurrent holdout and is paid on the lift it can prove. Both are legitimate. Both appear in the equation. They are different rungs of the same ladder — Act and Run.

What is not legitimate is charging for both on the same work.

Key points: On the same audience and the same intervention, charge for the capability or participate in the outcome. Never both. If the vendor is paid for the surface and paid again for the result the surface produced, it has invoiced twice for one email. Never Pay Twice is a rule we hold ourselves to, not only a charge we lay against adtech.

The law also disciplines the sale. A commercial team forced to choose has to be clear about what it is selling — tooling or accountability — and the customer is able to tell which one they bought. Ambiguity here is where outcome pricing usually dies quietly: an operator paid a fee regardless has no exposure, and an operator with no exposure is an agency with a dashboard.

Figure 4 — One Living Email, two commercial models, and the wall between them.

The technical condition

None of this works on a static email.

A payment needs a live balance, a current price and an authorisation window. A booking needs live availability. A renewal needs a real date. A declared preference needs somewhere it will be written back and later read. All of that is state at the moment of opening, not state at the moment of sending.

That is the composed-at-open inflection, and it is why it is the highest de-risking priority in the venture. A static email is a prediction made at send. A Living Email is a decision made at open. Everything in this section depends on which of those two things the email is.

One honest constraint, stated plainly because it is a condition of the bet rather than an objection to it. Interactive rendering is not universally supported: it is Gmail, Yahoo Mail and Mail.ru, behind sender registration and a DMARC policy most brands have not yet set. Fallback-first design is therefore not a courtesy. For a large share of any real list the fallback is the primary experience. An email programme that only works in its interactive form is a demonstration, not a product.

Key points: (a) The click-through was never a step in the journey. It was the leak. (b) Capability revenue is not new demand. It is demand the brand already created and then handed to whoever owned the next page.

Published by

Rajesh Jain

An Entrepreneur based in Mumbai, India.

Leave a Reply