Question 1

Do I need to know how to code?

Accepted Answer

No. The whole workspace is built around natural-language editing. You describe what you want changed; we patch the build. There's a JSON view for power users who want to peek under the hood, but you'll never need it.

Question 2

How does the variant engine actually work?

Accepted Answer

You pick the dimensions (hook, character pose, palette, CTA copy, etc.) and the values you want to test on each. We render every combination (the math is just the cartesian product) and serve them as a creative set. Engagement data per variant flows back in.

Question 3

Which DSPs and ad networks do you support?

Accepted Answer

Direct push to AppLovin, IronSource, and Mintegral. Universal MRAID 2.0 ZIP export works with any other DSP that accepts playable ads (Meta, Unity, Liftoff, etc.).

Question 4

What about my existing assets and brand kit?

Accepted Answer

Drop your characters, logos, screenshots, and UI kit into the reference pack. We auto-tag everything and use it as the source of truth. Every template skin and every variant is forced to stay on-brand. You set authenticity to "true-to-game" and it stays there.

Question 5

Can I generate assets if I'm missing them?

Accepted Answer

Yes. Character poses, FX, audio stings, and missing UI states can all be generated inline. Each generation has a fixed cost charged against your session budget cap, and you approve before it spends.

Question 6

How fast is "minutes, not weeks"?

Accepted Answer

The target workflow is a first playable preview in one session, then a multi-variant creative set after the first few edits. The exact time depends on asset readiness, brand constraints, and how many variants you want to test.

Question 7

What happens if my brand team needs to approve creative?

Accepted Answer

Every session has a shareable read-only preview link with comments. Brand can review variants, leave notes per-frame, and approve before anything is pushed live. Approval state is tracked per variant.

Question 8

How is 7play.ai different from template-based playable engines?

Accepted Answer

Honest answer: most current engines are template-based. You bring assets, pick a mechanic from a fixed gallery, swap in characters and copy, export. That ships reskins of known mechanics fast. 7play.ai is simpler at the surface: hand us a gameplay video, the agents reason about how your game plays (mechanic, controls, visual language, UI), figure out which assets matter, and generate sprites in place if you do not have isolated ones. Template builders scale creative. 7play.ai is creative discovery grounded in your real game.

Question 9

What does it cost?

Accepted Answer

We're in design partner mode right now, working closely with a small number of studios on their launches and creative scaling. Pricing follows the conversation, not the other way around. Drop us a line and we'll figure out what makes sense for you.

Design-partner pricing.