- The personal free edition already supports self-service local script-slot expansion, and the fixed packages and prices are defined.
- The team monthly and annual upgrade path already exists and routes users to the standard shared-SaaS formal tenant registration page.
- The
publicsuper-admin order lifecycle already runs a minimal real loop. Payment, activation, renewal reminders, and expiry recovery are not only demo pages.
Sales Sheet
Membership and Pricing
Pricing NarrativeThis page is for sales explanation, free-path guidance, and first pricing conversations. The core goal is not to explain every feature. It is to explain clearly which closed loop the customer should enter now.
The most stable commercial path today is: individual users start from the free path, people who keep using it personally but have not entered formal collaboration expand local script slots, formal teams move into the monthly or annual team-tenant path, and enterprise or private deployment is evaluated separately by scenario.
If you are deciding how to introduce ExecGov right now, do not start by listing a pile of module names. First judge whether the other side currently belongs to individual exploration, personal expansion, formal team collaboration, or enterprise project / private deployment.
Personal free experienceLocal script-slot expansionTeam monthly subscriptionTeam annual subscriptionEnterprise / private deployment
- Do not describe the personal free path as a complete general-purpose billing center.
- Do not say that every payment line is already fully connected to mature third-party payment gateways.
- Do not hardcode team monthly or annual pricing on the materials page because the final price, payment page, and service term should be read from the actual formal-tenant registration page.
Path 01
Free path experience
- Best for individuals, friends, or light evaluators touching ExecGov for the first time.
- Start by experiencing the public entry, personal skill library, upload flow, execution history, announcements, and community basics.
- The main goal is to feel whether this is a platform that can truly bring scripts and automation into one governed entry.
Path 02
Continued personal use / script-slot expansion
- Best for users who keep onboarding scripts in their personal space but have not moved into multi-user collaboration yet.
- The current fixed packages are
+1 19.90 CNY,+3 49.90 CNY, and+5 79.90 CNY. - After payment succeeds, the local script-slot quota is written back directly. The default recommended option is currently
+3.
Path 03
Formal team / monthly or annual subscription
- Best for teams that have already entered multi-user collaboration and need a formal tenant with a more stable usage cycle.
- They should not keep staying inside the hidden personal free tenant. They move into the standard shared-SaaS formal tenant registration path instead.
- The monthly option is better for validating one cycle first, while the annual option is better for teams that already know they will use ExecGov long term.
Path 04
Enterprise project / private deployment
- Best for customers with intranet, local Agent, approval, compliance, or formal-delivery requirements.
- These projects usually do not order directly through the standard membership page. They start by discussing boundaries, deployment style, and delivery style.
- They are better handled through scenario framing, delivery scope, and phase-based goals.
Monthly
How to frame the team monthly subscription
- Best for teams that are just preparing to enter formal collaboration but still want to validate one full cycle first.
- The advantage is a lower decision barrier and a practical way to test real members, real flows, and a real formal tenant.
- The right sales framing is: use one cycle first to verify whether the platform deserves to become part of the long-term team workflow.
- The price, payment page, and service term should be read from the actual target tenant registration page.
Annual
How to frame the team annual subscription
- Best for teams that already know they will use ExecGov for the long term.
- The advantage is a more stable service cycle and fewer repeated monthly renewal actions.
- The right sales framing is: for long-term usage, it reduces management friction and makes it easier to bring governance capability into the normal operating rhythm.
- The materials page still should not hardcode a fixed price. The authoritative source is the target registration page.
Price Authority
How pricing should be explained: what can be fixed and what should not be
| Path | Current pricing authority | Payment method / entry | More accurate sales framing |
|---|---|---|---|
| Personal free experience | 0 | Enter the free experience path and personal console directly | Let people confirm at very low cost whether the product deserves deeper attention |
| Local script-slot expansion | +1 19.90 / +3 49.90 / +5 79.90 | Personal free edition "billing and script slots" page | This is a fixed-price lightweight one-time expansion and the slot quota is written back directly after payment |
| Team monthly / annual subscription | Do not hardcode on the materials page | Route from the upgrade page into the standard shared-SaaS formal tenant registration page | The final price, payment page, and service term should be read from the target registration page |
| Enterprise / private deployment | Scenario-based evaluation | Discuss requirements, deployment, and delivery boundary directly | This should not be forced into the standard membership-page narrative. It should be quoted by project boundary. |
Benefit Matrix
Membership benefits and usage boundary matrix
| Path | Best for | What users get now | Current boundary |
|---|---|---|---|
| Personal free experience | Free-path trial, individual exploration, first-time visitors | First contact with the product position, entry structure, personal console, and platform value | Default script slots are limited and it is not meant to be the formal team collaboration space |
| Local script-slot expansion | People who already keep onboarding scripts in their personal space | Immediate expansion of local script slots after payment | This is lightweight expansion, not the formal team-edition membership |
| Team monthly subscription | Teams that want to validate formal collaboration first | Formal tenant registration path and a better multi-user workflow | Price and payment authority come from the registration page |
| Team annual subscription | Teams already committed to long-term use | A more stable service cycle with less monthly renewal friction | It is still not the default path for private deployment or deeper delivery boundaries |
| Enterprise / private deployment | Customers with intranet, compliance, approval, or formal-delivery requirements | A path based on project boundary, deployment mode, and governance requirements | This does not use the standard membership narrative and needs separate evaluation |
Demo Narrative
The smoothest explanation order for customer guidance and free-path demos
01. Let them try the free path first
On first contact, do not rush into pricing. Let them feel the public entry and the value of the personal console first.
02. If it is still only personal use, guide them to script-slot expansion
At this stage the key is to explain the fixed packages and the direct write-back of quota after payment, not to turn it into a complicated membership mall story.
03. If multi-user collaboration is about to start, move into the team monthly or annual path
The core here is not "buying one more package." It is switching from the hidden personal tenant into the standard shared-SaaS formal tenant path.
04. If intranet, approval, or private deployment enters the picture, move into enterprise-project discussion
These cases need delivery, deployment, and governance-boundary discussion and should not keep using the standard membership-page framing.
FAQ 01
Why does the team monthly or annual subscription not show a fixed price here
Because the current product truth is that the team upgrade path routes into the standard shared-SaaS formal tenant registration page, and the final price, payment page, and service term should be read from that live entry. Hardcoding it on the materials page would be more likely to drift from reality.
FAQ 02
Does local script-slot expansion count as a formal membership
No. It is a lightweight add-on inside the personal free edition that solves a personal script-slot capacity problem. If the user is entering formal team collaboration, the correct path is still the team monthly or annual formal tenant registration flow.
Next Step
Judge which category the customer belongs to first, then lead them through the matching closed loop
The most common sales mistake is not saying too little. It is mixing personal expansion, team membership, and enterprise delivery into one vague story. Explaining the path clearly matters more than piling on terms.