How it works

1. 1

   Apply

   Launch minus 12 weeks

   Apply once for your company in the partner portal: the company questions, all commitments and declarations.

   Outcome: Completed application

2. 2

   Assessment

   Within 10 working days

   We review your company, your commitments and any exceptions. A complete application results in a decision.

   Outcome: Approved, approved with conditions, or declined

3. 3

   Partner Agreement

   After approval

   Review the Partner Agreement in the portal and accept it; we countersign. It covers every app you build with us, and sets the commercial terms. At this stage we work together to find opportunities in a non-exclusive partnership.

   Outcome: Agreement signed by both sides

4. 4

   App and Engagement Order

   For each app

   When an opportunity goes live, you submit each app in the portal: what it is, the route, the customer, the technical approach and the dates. We approve it with an Engagement Order setting out the scope, dates, funded term and fees; you accept it and we countersign.

   Outcome: Engagement Order signed

5. 5

   Access

   3 working days after the Engagement Order

   Receive accounts for Studio Dev (Monterosa's control centre for live content), credentials for the Interaction SDK, the CLI and a shared Slack channel.

   Outcome: Accounts and a named Monterosa contact

6. 6

   Build

   Halfway checkpoint

   Build on a development instance. Review the working app with us throughout until code freeze.

   Outcome: Working app and checkpoint review

7. 7

   Evidence

   Launch minus 4 weeks

   At code freeze, supply security scans, load tests, hosting and cookie declarations, and your runbook.

   Outcome: Evidence reviewed by Monterosa

8. 8

   UAT

   Launch minus 3 to 2 weeks

   We test first, then the customer signs off against the agreed scope. Defects are recorded and the must-fix list agreed.

   Outcome: Written sign-off and defect list

9. 9

   Production set-up

   Launch minus 10 working days

   We create the production Project. Deploy the approved version and smoke test by five working days before launch.

   Outcome: Approved production app

10. 10

    Launch

    Launch day

    Go live after approval. Your team stays on standby through the first live event periods and ready to respond.

    Outcome: Live fan experience

11. 11

    Fast follow

    Launch to 4 weeks after

    Fix P1 issues immediately. Batch other P2+ fixes weekly with written approval. Review at two weeks; steady state at four.

    Outcome: Stable app and normal support

Prizes, currency, leaderboards or material votes need certification. Plan it at least three weeks before launch and confirm the date with us.