Bring your own customer agreement. We would love to show you how it can find a home in Alunta.
Recalculate your own price
Bring a real pricing model: fixed price, seats, usage or a combination. Ask to see the same customer on monthly and annual billing, including any discounts and included units. Establish who supplies usage data and when the billing period becomes locked.
Checkpoint: You can explain every line and reproduce the calculation yourself.
Change an agreement mid-period
Upgrade, downgrade and cancel a sample subscription. Ask what happens immediately, what waits, and how an adjustment or credit appears. In Alunta, a seat reduction follows the plan setting: a lower current quantity does not necessarily change the amount billed for the current period.
Checkpoint: The demonstration shows both the agreement change and its billing consequences.
Follow the invoice into accounting
Ask to see the difference between billing data, a draft, an issued invoice and an accounting entry. Establish what your team approves and where errors appear. An integration logo alone does not explain which data is transferred or who handles a rejection.
Checkpoint: The responsible person can find the error, correct the source and follow its status.
Try a payment that fails
An expired card should ideally become a small task for the customer and a small part of your day. See how the system helps with retries, customer messages and an easy payment-method update. Little things make a big difference as your customer base grows.
Checkpoint: You know what the customer sees and who follows up.
Check access and integrations
Try customer self-service and see the working day from the bookkeeper’s chair. Good connections mean less duplicate work: your product, CRM, accounting and AI should be able to join in. At Alunta, we believe in open connections through the API, webhooks and MCP, so you can build on your own ideas.
Checkpoint: You understand the responsibilities of your product, Alunta, the payment provider and accounting system.
Plan migration and ongoing operations
List the agreements, prices, start dates and history you need to transfer. Check separately whether payment agreements can be reused; this depends on the provider and setup. Request a limited trial import and comparable pricing that includes required extras. Assign someone to monitor the first renewals.
Checkpoint: You have a concrete transition plan and know which steps require your team.
Put it into practice
A small evaluation scorecard
Use the same assessment for every system. Leave unanswered questions open.
- Demonstrated
- You have seen the journey with your own example data
- Needs configuration
- There is a specific setting and an owner
- Needs development
- There is a defined integration and an estimate
- Unresolved
- Documentation or a concrete trial is still missing
Do not give every feature equal weight. Reliable accounting transfer may matter more to your team than one additional payment method.
Two common questions
How should I compare two subscription systems?
Use the same customer data and journey in both: creation, price change, invoicing, payment, accounting and cancellation. Record what was demonstrated, needs configuration, requires development or remains unresolved.
Can I transfer every payment agreement?
Check this specifically. It depends on the payment provider, agreement type and both the old and new setup. Run a trial before relying on it for the whole transition.
Product references
The Alunta-specific descriptions use these public product guides. Consult them for exact behaviour and configuration details.
