A recurring relationship.
A connected experience.
Bring subscriptions, customers, and your own portal together. Build the recurring service around the business relationships that matter.
A service that recurs.
A relationship that stays connected.
Keep the customer, subscription, portal, and partner relationships understandable as the recurring service moves through its lifecycle.
A subscription has a customer.
Keep the connection visible.
Represent the recurring service alongside the customer it belongs to. Let the portal show the relevant record and the supported operations rather than treating every renewal as an isolated purchase.
- Connect the recurring service to the customer
- Build the portal around meaningful subscription data
- Plan the actions your service supports
Northstar Studio
Customer contextRecords are presented for the selected customer.
Atlas Collective
Customer contextRecords are presented for the selected customer.
The person signs in.
The customer sets the context.
A customer portal may serve a person who belongs to several businesses. Resolve the selected membership and make switching explicit so subsequent requests refer to the intended business customer.
- Show the active customer before an operation
- Use membership-scoped access
- Keep customer-specific records in the right context
Northstar Studio
Customer contextRecords are presented for the selected customer.
Atlas Collective
Customer contextRecords are presented for the selected customer.
Reward an ongoing relationship.
Assign it deliberately.
Use affiliate plans for recurring commission arrangements. Assign existing subscription relationships explicitly when future eligible renewals should qualify; customer attribution alone does not retroactively make every subscription eligible.
- Configure recurring plans and overrides
- Assign existing subscriptions for eligible future work
- Follow commissions and payout administration
- Eligible renewalAccording to plan and assignment
- Commission recordTrack the generated business record
- Payout administrationPayment implementation remains separate
Give service changes
an understandable outcome.
Use rules and explicit actions around the supported changes of your recurring service. Inspect a rejection reason before retrying and use idempotency where the same intended operation must not duplicate its effect.
- Express the conditions for a service operation
- Follow why work proceeded or was rejected
- Connect repeats to the original intended effect
execution / example-042- 01RequestUpdate a product
Actor and customer context
- 02DecisionAllowed to proceed
Permissions and rules evaluated
- 03ChangeProduct updated
Recorded outcome
- 04OutboxExternal work queued
Delivery has a separate state
Inspect the action through its outcome.
Collect the information
the service actually needs.
Use a structured form in the customer journey for project-specific setup information. Field types and validation describe the questions, while your frontend controls how the portal asks them.
- Build a service-specific setup form
- Render the fields inside the portal experience
- Keep answers connected to your implementation
The field definition stays structured.
Your frontend controls the presentation.
Local rendering preview. No answers are submitted.
Explore the details.
The capabilities, examples, and integration choices behind this solution.
Build the recurring service.
Connect the relationships.
Choose the subscription model, portal experience, and business actions around your service.