Sample work

See what the work looks like.

This public preview uses a fictional game to show the clarity and detail a team can expect. The deeper evidence work and client workflow stay inside the engagement.

Real operator record

Start with the source records.

The Myosuki record covers one game we operated. It does not claim that another game will follow the same sequence or reach the same result.

Evidence: Six dated Steamworks and Steam placement records
Work context: Commercial Steam strategy operated through the documented recovery period
What stays visible: Reporting windows, discounts, Daily Deal placement, source images, and the limits on causal inference
What it does not claim: No isolated tactic is credited for the result, and no outcome is promised for another title

Open the dated operator record

Curated public preview

Three artifact types, shown through selected excerpts.

These excerpts show the standard of the work. They do not give away the connected procedure used to build a paid deliverable for another game.

Selected diagnosis excerpt

Commercial diagnosis

Decision at risk: Should this fictional team buy more festival traffic, or fix the Steam page before the next campaign?
Illustrative finding: The playable footage makes tense crew decisions easy to see. The page leads with inventory systems and setting instead, so page communication is the strongest-supported constraint.
Important uncertainty: The available record does not settle how much audience demand exists. The page finding is not a forecast of wishlists.
Private working record: [defined only when included in scope]

The excerpt shows how clearly the conclusion is stated. The evidence tests and internal decision logic are not included.

Selected direction excerpt

Steam-page direction

Fictional player promiseCommand a damaged salvage crew. Decide who gets home.

Positioning: Lead with the pressure of protecting the crew, not the ship's inventory screen or unexplained world lore.
Page direction: Opening copy and creative direction should make that playable choice clear without adding a feature the current build cannot support.
Truth boundary: Do not imply crew relationships, branching outcomes, or survival consequences that are not present in the game.
Private specifications: [defined only when included in scope]

This excerpt shows the level of direction a team receives. It is not a reusable page formula or asset recipe.

Selected handoff excerpt

Implementation plan

Generic implementation-plan structure
Work item	Owner	Dependency	Approval	Review point	Publication check	Measurement check	Status
Prepare the approved Steam-page revision	Studio page lead	Approved positioning	Game director	Pre-publication review	Desktop and mobile QA	Starting measure recorded before publication	In progress
[defined only when included in scope]	[defined only when included in scope]	[defined only when included in scope]	[defined only when included in scope]	[defined only when included in scope]	[defined only when included in scope]	[defined only when included in scope]	[defined only when included in scope]
[defined only when included in scope]	[defined only when included in scope]	[defined only when included in scope]	[defined only when included in scope]	[defined only when included in scope]	[defined only when included in scope]	[defined only when included in scope]	[defined only when included in scope]

The visible columns show how the handoff is organized. Client evidence, task order, dates, and decision logic are completed only inside the signed engagement.

How the public preview fits

See the public method at the right level.

The Method page explains the four broad areas, the evidence-first philosophy, and the three high-level stages behind a commercial recommendation.

Discuss the complete work

Bring us the game and the stuck decision.

Share the Steam page, tell us what is not moving, and include the next demo, festival, campaign, or launch decision your team must make.

Send us your Steam page