All articles

Practical guide · Getting started

Build the first agreement. Test the whole journey.

A subscription business starts with something your customer needs repeatedly. Your systems then need to repeat the agreement without rebuilding it for every invoice. Begin with one manageable model and follow it from purchase to cancellation.

Alunta · Updated

A good idea deserves a good start. Here is the path to your first subscription agreement.

Define what the customer receives

Write down the recurring deliverable: software access, ongoing advice or a regular service. Define what is included and what costs extra. An internal pricing idea is not enough; sales, support and the invoice should describe the same agreement.

Checkpoint: Can a colleague explain the service and its boundaries without asking you?

Choose a price you can verify

A fixed price is a simple starting point. Seat pricing needs a clear quantity rule; usage pricing needs reliable measurement. Choose the currency and renewal interval too. In Alunta, the plan is the price catalogue and the subscription is the individual agreement. Changing the catalogue does not automatically rewrite existing agreements.

Checkpoint: Can you calculate the next period price for three realistic customers by hand?

Agree the dates and change rules

Decide the start date, first period and future renewal. Consider trials, upgrades, downgrades and cancellation before they become support questions. In Alunta, a pause or trial belongs to the subscription timeline rather than adding a new subscription status. Price adjustments depend on the model and configuration.

Checkpoint: Write down what should happen when someone starts mid-month and changes their agreement.

Connect purchase, invoice and payment

Decide whether customers buy through checkout or your team creates the agreement. Connect the relevant payment provider and accounting integration. Check the invoice recipient and how payments are recorded. An active subscription, an issued invoice and a completed payment are three different facts.

Checkpoint: Can you trace one customer from purchase through invoice, payment status and accounting?

Run a small trial journey

Use a limited setup and your payment provider’s test facilities where available. Try a failed payment, an agreement change and a cancellation as well. Check customer emails and self-service access. Decide in advance how any real trial invoices and payments will be handled.

Checkpoint: Have both a successful purchase and an exception completed the journey?

Follow the first renewal

Start with a small customer group and follow their next period. Name the person responsible for declined payments, incorrect billing data and questions. Reconcile agreements, invoices and receipts. MRR helps track normalised subscription value; it does not tell you how much cash is in the bank.

Checkpoint: Does everyone know who takes the next step when something needs attention?

Put it into practice

One simple starting point

Illustrative service agreement, not an Alunta pricing offer.

Service
A clearly scoped monthly service
Price
DKK 500 per month excluding VAT
10 active agreements
DKK 5,000 normalised MRR before discounts or changes
Control
Check invoicing and actual payment separately

This example assumes identical active monthly agreements without discounts. Taxes, expenses and payment timing are outside the MRR calculation.

Two common questions

Should I start with lots of plans?

Start with the models your real customer agreements require. Every additional plan, currency and interval adds scenarios to verify. Expand the catalogue once the core journey works.

Does an active subscription mean a payment succeeded?

No. Subscription status describes the agreement. Billing and payment have their own processes, and an active agreement may have a pending or declined payment.

Product references

The Alunta-specific descriptions use these public product guides. Consult them for exact behaviour and configuration details.

Next step

Give your idea a home in Alunta

You have the idea. We have the engine for subscriptions, invoicing and payments. Try your model in Alunta, and talk to us if you would like an experienced pair of eyes on the first agreement.