How it works

The shared plan from application to your first live Event. These are default intervals, agreed at approval.

  1. 1

    Apply

    Launch minus 12 weeks

    Complete the application, including the company questions and all 65 commitments. Propose UAT, launch and fast-follow dates.

    Outcome: Completed application

  2. 2

    Assessment

    Within 10 working days

    We review the scope, backend, monetisation, security, dates and capacity. A complete application gets a decision.

    Outcome: Approved, approved with conditions, or declined

  3. 3

    Partner Agreement

    Before access

    Sign the Partner Agreement. It sets the commercial terms.

    Outcome: Agreement signed

  4. 4

    Access

    3 working days after approval

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

    Outcome: Accounts and a named Monterosa contact

  5. 5

    Build

    Halfway checkpoint

    Build on a development instance or Playground (Monterosa's sandbox instance). Review the working app with us halfway between access and code freeze.

    Outcome: Working app and checkpoint review

  6. 6

    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

  7. 7

    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

  8. 8

    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

  9. 9

    Launch

    Launch day

    Go live after approval. Your team stays on standby through the first live Event.

    Outcome: Live fan experience

  10. 10

    Fast follow

    Launch to 4 weeks after

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

    Outcome: Stable app and normal support

Launch planner

Work back from your proposed launch date.

MilestoneDate
ApplyChoose a launch date
Code freeze and evidenceChoose a launch date
Request certificationChoose a launch date
UAT sign-offChoose a launch date
Post-launch reviewChoose a launch date
Fast follow endsChoose a launch date

Planning dates only. Approval takes up to 10 working days after a complete application. Production dates are agreed in working days.

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

Standards →