This mother-template preview demonstrates the reusable pricing structure only. Replace every offer statement with approved project facts before release.
Replace before launch.
Get started with your first SaaS startup.
Charged $89 every month
Includes
Ship Fast with your SaaS Startups.
Charged $169 every month
Everything in Starter, plus
Ship Any AI SaaS Startups.
Charged $249 every month
Everything in Standard, plus
The table follows the billing option selected above and uses the same plan data as checkout.
| Plan detail | Starter | Standard | Premium |
|---|---|---|---|
| Best for | Get started with your first SaaS startup. | Ship Fast with your SaaS Startups. | Ship Any AI SaaS Startups. |
| Checkout charge | Charged $89 every month | Charged $169 every month | Charged $249 every month |
| Credits | 100 credits included | 200 credits included | 300 credits included |
| Validity | Valid for 30 days | Valid for 30 days | Valid for 30 days |
| Included capabilities |
|
|
|
Pricing should explain account state and billing facts without inventing a universal task cost.
After sign-in, the header reads the authoritative account balance and refreshes after credit-changing actions, page focus and checkout returns.
The included credit amount and validity shown above come directly from the selected plan configuration.
The mother template does not assume every action costs 10 credits. A project must supply its own server-side quote before showing estimated usage.
These answers describe the current template behavior and avoid promises the project has not configured.
Use the checkout-charge line shown on each plan. Annual plans can display a monthly equivalent while the checkout charge states the full yearly amount.
Each plan shows its configured validity beside the included credits. A new project should replace those values before enabling payment.
After sign-in, the header keeps Credits, Upgrade and the account menu visible. This page also shows a compact account summary when a user is authenticated.
Checkout only offers providers enabled by the project configuration. The pricing page does not claim support for a provider that is turned off.
The mother template does not invent a universal cancellation promise. A project must define the provider flow, effective date and customer support path before publishing this answer.
No refund window is assumed by the template. Add the confirmed legal and payment policy to the Project Brief before enabling checkout.
Return to the plans, select a cadence and review the checkout charge before continuing.