Skip to main content

AI Billing Agent — Dynamic Pricing Rules & Multi-Phase Plan Lifecycle

🔍 Problem Statement
As a subscription ops manager, I experience no native way to schedule pricing changes or chain plan transitions, which forces manual intervention at renewals and reliance on Stripe workarounds — causing billing errors and subscriber churn.


💡 User Stories

  1. As an ops manager, I want to write rules like "increase price 3% annually, capped at 15% lifetime" so I can automate inflation-linked pricing without code.

  2. As a finance controller, I want an audit log of every pricing decision — rule, inputs, output — so I can reconcile revenue and resolve disputes.


🎯 Definition of Done

  • ✔ Given an active billing rule, when a renewal runs, then the rule evaluates against the subscription context and the resulting price is applied before charging.

  • ✔ Given a two-phase plan, when Plan A expires, then Plan B activates automatically with a configurable subscriber notification.

  • ✔ Given a natural language prompt is compiled, then a versioned JSON policy is created — admins must explicitly activate it before it affects any live subscription.

  • ✔ Given a rule fails, then the subscription falls back to its previous price, an alert fires, and no charge is submitted.

What would you like to be able to do? (One idea per form):
I'd like to be able to set a plan such that when it expires it activates a 2nd plan (phase).

How would that help you?:
It would keep me from having to run segments and campaigns each time to step up everyone on plan 1 to plan 2.

How important is this to you?:
Critical

Email address:
c.cleaveland@theday.com

———————————————
This task was submitted through Suggest an idea - Product Roadmap
https://form.asana.com/?k=qsv6hMm2wL8SXD_R-h-N9Q&d=742417627358732

Status: Available2 comments

Log in to comment and vote

Comments2

  • Michael Ghattas

    Team•

    Apr 14

    We’ve released the AI Billing agent that is capable of doing all types of complex dynamic prices and multi-phase renewals. Check out the documentation here:

    https://docs.pelcro.com/docs/ai-billing-agent

  • An Anonymous User

    •

    Apr 2

    •

    Merged request

    •

    4 votes

    Price change complications

    🔍 Problem Statement

    Changing subscription prices in Pelcro is complex and error-prone. Past incidents include automation bugs where scheduled billing phases were not respected after a price update, and the Core API's batch update limitations have forced teams to fall back on direct Stripe API calls — bypassing Pelcro's control layer and creating reconciliation risk.


    💡 User Story

    As a Pelcro admin, I want a reliable, first-class way to change subscription prices through Pelcro, so that pricing updates are applied correctly on the next billing cycle, scheduled phases are honoured, and no direct Stripe API intervention is ever needed.


    🎯 Definition of Done (DoD)

    A feature is done when:

    ✔️ Given an active subscription with an existing price, when an admin applies a price change through the Pelcro admin interface or API, then the updated price takes effect on the correct billing cycle, all scheduled phases continue to be respected, and the change is fully completed without requiring any direct Stripe API calls or manual workarounds.