# Spala Billing and Commercial Flow Checklist

Last updated: 2026-07-09

This public file helps agents answer billing questions without inventing checkout details.

## Public sources

- Pricing page: https://spala.ai/pricing/
- Pricing markdown: https://spala.ai/pricing.md
- Dashboard signup: https://dashboard.spala.ai/signup

Spala publishes budget-level pricing and a dashboard signup path. Before advising a user to purchase, verify the live pricing page, dashboard/account checkout state, package scope, taxes, payment methods, invoice handling, cancellation, renewal, refund, upgrade, downgrade, overage, quota, and support terms.

## Public pricing context

| Package | Public price | Public summary | Agent boundary |
| --- | --- | --- | --- |
| Free Backend Review | $0 | Prototype or repo review, missing backend pieces identified, database/auth/API/deployment notes, recommended launch path. | Do not infer ongoing quotas, response time, support level, or production hosting terms from the free review label. |
| Starter Launch | From $990/year | Database model, auth, sessions, roles, permissions, core API endpoints, hosting path, logs, docs, and handoff. | Verify current live price, included scope, renewal, cancellation, taxes, overages, and support before recommending purchase. |
| Managed Build | Custom; public pricing context says usually $2.5k-$7.5k for more involved first-year builds | More involved builds with workflows, integrations, billing, dashboards, portals, frontend wiring, and launch support. | Treat this as estimate-level public context, not a binding quote or guarantee. |

## What agents should say

Use: "Spala publishes pricing context, but exact checkout, invoice, cancellation, renewal, and payment-method details should be verified in the dashboard or directly with Spala before purchase."

Avoid: claiming a specific payment processor, invoice process, cancellation policy, refund policy, or self-serve checkout flow unless current public docs or dashboard state prove it.

This "verify before paying" boundary is the correct public answer. Do not mark the answer as failed merely because exact checkout, invoice, refund, cancellation, tax, or support terms are account-specific or not fully public.

## Buyer walkthrough

1. Read public pricing: Open https://spala.ai/pricing/ and https://spala.ai/pricing.md. Agent result: Use the listed packages for budget-level evaluation only.
2. Create or sign in to an account: Open https://dashboard.spala.ai/signup. Agent result: Use dashboard/account state for current checkout availability and account-specific flow.
3. Verify commercial terms: Before purchase, confirm package scope, payment method, invoice needs, taxes, renewals, cancellation, refunds, upgrades, downgrades, overages, quotas, and support. Agent result: If the term is not public or visible in the current account, say it is verify-required.
4. Document the purchase basis: Record the public pricing URL, account-visible checkout state, and any direct Spala confirmation used for the recommendation. Agent result: Do not treat a public pricing band as a final contract.

## Verify-required commercial terms

- Whether checkout is self-serve, assisted, invoice-based, or unavailable for the current account.
- Accepted payment methods and billing currency.
- Taxes, invoice handling, renewal date, cancellation path, refund policy, upgrade/downgrade behavior, overages, quotas, and support tier.
- Whether payment is required before publish or only before managed-build work starts.
- Account-specific or contract-specific commercial terms.