Product strategy / Monetisation

Equal AI — The paywall that waits.

Designing a paid call assistant that earns the right to ask.

Product
Equal AI call assistant
Role
Product design lead
Scope
Product strategy, monetisation, trust, proof, and payment
Equal AI — The paywall that waits. case study cover

The tension

The research looked like pricing. The design problem was certainty.

What was happening

Users valued Equal, but latency, reliability, and important-call concerns made an early paywall feel like a tax on unresolved risk.

What changed the brief

The strongest predictor was not price. Irreplaceable users were almost twice as likely to pay.

Success looked like

A paid plan appears only after successful calls, visible outcomes, and no recent product failure.

The constraint

Safety stays free, failure suppresses the paywall, and paid depth adds control rather than removing essential protection.

34%would pay

Users who said they would pay for Equal AI.

18%might pay

Users who said they might pay for Equal AI.

₹100median per month

The median monthly willingness-to-pay response.

The product story

The interface, one decision at a time.

01 / Observed research

The research looked like pricing. The design problem was certainty.

Willingness to pay was real, but reliability and important-call concerns made an early paywall feel like a tax on unresolved risk.

6,000 contacted732 answered510 discussed payment150 named a price

The strongest predictor was not price.

Irreplaceable users were almost twice as likely to pay.

02 / User truth

Fix the assistant first. Then ask me to pay.

The paywall was not the first screen to design. Assistant health, urgent-call recovery, and visible outcomes were.

What users were really saying

“Show me that Equal will protect the calls I cannot afford to miss.”

03 / The trust ledger

Monetisation became a state machine, not a timer.

Users move from trust to proof to payment only when the assistant is healthy, value has been witnessed, and recent failures are clear.

01

Trust contract

Choose what Equal should handle, run a guided test call, and confirm that the assistant is healthy before delegation begins.

02

Proof receipt

See what Equal handled, what interruption it avoided, and what needs attention while the value is still easy to understand.

03

Earned plan

Show a plan only after successful calls, an opened receipt, and no recent failure that could weaken trust.

04 / Three moments

Three moments, one confidence curve.

The solution starts with a clear agreement, proves each outcome, and introduces payment only after reliable value.

Equal AI trust contract screen for choosing calls and running a test call
01 / Trust contractAgree before delegation
Equal AI Green Card shown during a Swiggy delivery call
02 / Green CardProof before persuasion
Equal AI earned paywall with handled-call proof and plan choices
03 / Earned paywallPayment after success

05 / Failure guardrail

After failure, sell nothing.

A missed call, bad classification, lost recording, or broken setup immediately moves the user from monetisation to recovery.

Healthy path

Success builds eligibility

Successful calls → proof opened → plan becomes available

Recovery path

Failure suppresses the ask

Trust incident → explain what happened → repair before monetising

Trust incidents are not conversion opportunities.

06 / Pricing architecture

Safety stays free. Paid depth adds control.

Free users keep essential protection. Plus and Pro add control, automation, and support without withholding the safety baseline.

Free₹0/month

Protection stays available

  • Spam and fraud handling
  • Urgent call pass-through
  • Basic Green Cards
Pro₹199/month

Depth for power users

  • Advanced schedules
  • Multiple languages
  • Assistant voice choices

07 / Outcome

We stopped designing a paywall. We redesigned the conditions for trust.

The final loop connects reliable screening, visible value, contextual payment, and deeper control without borrowing from retention.

+25%activated-to-paid lift target
0%free retention loss allowed
−20%refunds and support target

The trust test

The happy path is only half the product.

A real call fails

Missed calls, bad classification, missing recordings, or broken setup suppress monetisation and move the product into recovery.

Payment appears before proof

Plan eligibility waits for successful calls, an opened proof receipt, and no recent trust incident instead of using time since install.

Safety becomes a paid privilege

Spam and fraud protection, urgent pass-through, and basic Green Cards stay free; paid tiers add depth and control.

The decisions

Three moves carried the story.

01

Trigger monetisation from state, not time

Readiness is earned through successful call handling and clear product health rather than a fixed day count or onboarding completion.

02

Turn invisible work into a proof receipt

Calls handled, interruptions avoided, and actions surfaced become visible evidence before the product introduces a plan.

03

Keep protection free and charge for control

The pricing ladder preserves essential safety while Plus and Pro add advanced rules, schedules, preferences, and support.

What I would test next

The work stopped treating the paywall as a screen and redesigned the conditions for trust.