normic
Use cases

The moments normic is built for

Every game and app studio lives through the same moments every week, and each one ends with the same question: did it work, and what now? normic is built to answer it.

A price test

A starter pack costs a little less. More players buy it, but each one pays less. Did the studio make more money, or less?

With normic, your team knows, and decides whether to keep the new price, go back, or try another one.

A new ad setup

Players now see more rewarded ads a day, and ad revenue is up. Are new players leaving because of it?

With normic, your team knows whether the extra ads pay for themselves, and where to draw the line.

A live-ops event

Events now run more often, and players spend more. Are they still coming back a week later?

With normic, your team knows whether to keep the new rhythm or step back.

A new paywall

Trials are up after a paywall change, but paid subscriptions take longer to show. Is it too early to call?

With normic, your team knows when a result is ready to call, and does not call it before then.

A budget shift

UA budget moved to a new country and installs got cheaper. Will those players be worth what they cost?

With normic, your team knows whether to scale up, and how fast.

A dip nobody can explain

Revenue dipped on Tuesday. Twelve replies in the channel, and still no answer.

With normic, your team knows which change it followed, and what to do about it.

Who lives these moments

Growth, monetisation, live-ops, ads, UA and product teams at game and app studios.