Implementation and operation

Aura runs everything underneath.

Network connections, data delivery, reconciliation and reporting. Your team provides access to the data that shows qualifying behaviour, and the approvals your processes need.

How a programme runs

From qualifying activity to data on a customer’s line.

Your systems keep doing what they do. Aura handles the qualification, the telecom side and the reconciliation.

  1. You

    Your systems

    The customer activity you already record, such as salary, balances and transactions.

  2. Agreed in planning

    Agreed data

    Only what is needed to check the rule, shared by a method your technology team agrees.

  3. Aura

    Qualify and unlock

    Checks each customer against your rule and triggers the unlock.

  4. Aura

    Network delivery

    Delivers the data on the mobile network the customer already uses.

  5. Your customer

    Your plan

    The customer sees your data plan, in your brand and your channels.

Back to your team: reports on qualification, delivery, reconciliation and the results against the control group.

Conceptual. The integration method, the data shared and the report format are agreed with your teams during planning.

Operational ownership

Where your team and Aura meet.

You keep the customer relationship and the decisions. Aura carries the build and the day-to-day running.

Your team

  • Access to the data that shows qualifying behaviour
  • The rules: who qualifies, what they do, how much data and how often
  • Your brand, your channels and your customer relationship
  • Approvals your processes need, including risk and information security
  • Review of results with your analytics or finance team

Aura

  • Integration work, using a method agreed with your technology team
  • Telecom operations, including the network connections
  • Automation that turns qualifying activity into delivery
  • Data delivery on the networks your customers already use
  • Reconciliation of what was earned, delivered and charged
  • Reporting, measurement and ongoing improvement

The implementation path

What happens, and what your team does.

The sequence is fixed. How long each step takes depends on your systems and approvals, and is planned with you.

  1. Design

    Find the opportunity

    A target behaviour, the customer group to start with, and what a change in that behaviour is worth.

    Your team

    • Your growth goal
    • Access to the relevant customer data
    • Your own economics, such as the value of deposits
  2. Design

    Design the programme

    A programme design and an experiment plan, with measures and scaling criteria agreed before launch.

    Your team

    • The rules: who qualifies, what they do, how much data and how often
    • Approvals from your teams
  3. Run

    Launch and integrate

    A live programme under your brand, without your team building or operating a telecom stack.

    Your team

    • Technical access to the data that shows qualifying behaviour
    • Your channels to tell customers about the plan
  4. Run

    Deliver and reconcile

    Reliable delivery and a reconciled record you can check.

    Your team

    • A route for customer questions in your existing service channels, agreed in planning
  5. Prove

    Measure what changed

    A clear answer on whether the programme pays, and what to do next.

    Your team

    • Agreement on the measures and success criteria up front
    • Your analytics or finance team to check the results
  6. Prove

    Improve and scale

    A growing programme, with each stage earned by proof from the one before.

    Your team

    • Decisions on which groups and behaviours come next
    • Approvals for each new stage

For technology, operations and risk teams

Agreed with your teams before anything goes live.

Data protection, security and compliance requirements are agreed with your risk and information security teams before any customer data is shared. Tell us what your review needs and we will work through it with you.

Settled during planning

  • The integration method and the data each side shares
  • Which networks are covered in your market
  • Who sends customer messages, and through which of your channels
  • How customer questions about data delivery are handled
  • Report format and frequency
  • Data protection, security and contractual terms
  • Commercial terms for the programme and for scaling

Evaluation questions

From technology, operations, risk and procurement.

All questions

What does our team need to build?

Aura handles the integration work, telecom operations, data delivery and reconciliation. Your team provides access to the data that shows qualifying behaviour, and the approvals your processes need.

The integration method is agreed with your technology team during planning, based on what your systems already support.

What data does Aura need?

Only what is needed to assess the qualifying behaviour, deliver the data and measure the results. The exact data, how it is shared and how often are agreed with your teams before anything is shared.

How are results reported?

Aura reports on qualification, delivery, reconciliation and the outcome measures against the control group. The format and frequency are agreed during planning, and your analytics or finance team can check the results.

How is customer data protected?

Data protection, security and compliance requirements are agreed with your risk and information security teams before any customer data is shared. Tell us what your review needs and we will work through it with you.

What do we commit to at the start?

One experiment: one group of customers, one valuable behaviour, one clear test of the economics, a matched control group and criteria for scaling that we agree up front. Any further spend is decided by the results.

Bring your technology and risk teams in early.

Tell us what your review process needs. We will plan the integration and the approvals with your teams.