Proof

Proof, with the attribution written down.

Everything on this page follows one rule: verified facts are labeled as verified, illustrations are labeled as illustrations, and nothing is published without permission.

Operator case study

Girls! Girls! Girls!?

Developed by Myosuki, our founder’s own studio. The operating system ContentCrepe sells was developed and tested marketing this title.

Deliverable examples

The formats an engagement produces.

These are the working documents of the standard client workspace. We walk qualified applicants through real samples on the fit call; we do not publish client artifacts here without written approval.

Comparable matrix
Where the game actually sits against category leaders, direct peers, and cautionary underperformers.
Decision memo
What should change, why it matters, at what confidence, owned by whom, and by when.
Store-page board
Copy, tags, screenshots, capsule, trailer, and declarations with approval status.
Capsule brief
Creative direction an artist can execute, judged at thumbnail size.
Screenshot plan
Which shots communicate the fantasy, in what order, and what must be captured.
Tag map
The tag neighborhood the game has to win, built from comparable evidence.
Campaign roadmap
Coming Soon through post-launch, with owners, dependencies, and decision gates.
Implementation board
Every approved action with an owner, a deadline, evidence, and status.
Risk register
Product, page, demo, launch, compliance, vendor, and schedule risks.
Measurement dashboard
Baseline, traffic, wishlists, demo behavior, and results, labeled honestly.

Client case studies

Approved external case studies and anonymized before/after examples will appear here as engagements complete and clients grant written permission. We keep internal before/after records on every engagement regardless, and no client is ever required to provide a testimonial.

Evidence and attribution limits

What this page will never claim.

Marketing proof is easy to inflate. These are the rules that keep ours flat and true.

  • Steamworks figures shown on this site are verified historical facts where documentation exists. Anything estimated or reconstructed is labeled as such.
  • Revenue outcomes emerge from years of product, pricing, and campaign decisions. We do not attribute them to a single page change or marketing action.
  • The operator case study reflects full control of budget, product, and timing. Client engagements involve constraints the case study did not have.
  • Client names, metrics, screenshots, and outcomes are published only with separate written approval. A quiet proof page is the cost of that rule.
  • Results labeled inconclusive stay labeled inconclusive. Thin traffic does not become a success story.

See the real thing

Sample deliverables come out on the fit call.

Apply with your game and, if the fit is plausible, we walk you through what the workspace would look like for your title.

Applications are reviewed for fit before any engagement is proposed.