Aura Forge · proof first for game studio founders

You make the game.We prove the next move.

You keep building the game. We find and fix one problem outside the build that is costing time or growth.

Inspect the format
Public evidence first · yours to keep

We know it's not the game keeping you up.

It's late. The build is waiting — but the store page needs copy, Discord's on fire, three creators are chasing assets, and a publisher wants an update by morning. You didn't start a studio to run all of this. But here you are.

Marketing · youCommunity · youCreators & UGC · youPlayer support · youHiring · youPublisher outreach · youAnalytics · youRetention · youInvestor updates · you

A whole second company runs inside yours — and you're the only one staffing it. One evidenced fix can give the build room again.

The promise

Start with one problem we can actually show.

No platform pitch before proof. We inspect public studio surfaces, separate what the evidence shows from what we infer, and recommend one first fix around a founder outcome that matters:

01 — Time

Recover build time

Find one recurring operating task whose public symptoms are visible and make the first repair concrete.

↳ A fix with a named owner and boundary

02 — Focus

Reduce decision load

Rank the visible problems instead of handing you another undifferentiated backlog.

↳ One top priority, not twenty ideas

03 — Growth

Support the next signal

Tie the recommended fix to a success signal the studio can observe without inventing a result.

↳ A proposed measure with unknowns shown

The commitment is deliberately narrow: useful evidence first, optional implementation second.

Evidence before trust

Inspect the diagnosis before you buy the implementation.

The free Studio Evidence Pack starts from public material and makes the reasoning inspectable. You see what we observed, what we inferred, how confident we are, and what remains unknown.

Public sources reviewed

Store page, website, public community surfaces, trailers, posts, and other links you choose to share.

Three evidence-backed findings

Each finding separates Evidence from Inference instead of presenting a polished guess as fact.

Decision-ready next move

One top priority, one first fix, one proposed success signal, plus Confidence / unknowns.

Studio Evidence PackInspectable
Inputs public onlyFindings 03
A diagnosis you can challenge before any implementation begins.
IncludesEvidence · Inference · Confidence / unknowns
Ends withTop priority · First fix · Success signal

If the pack is not useful, the paid path has not earned the next step. The findings are yours to keep.

Illustrative format · not a client result

See the shape of what comes back.

This fictional example demonstrates the format only. It is not a claim about a real studio, client result, or promised outcome.

Finding 01 / 03Priority candidate
Source Public store pageConfidence Medium
The page leads with a feature list before it gives a new player a clear reason to care.
EvidenceThe first visible copy names systems and modes; the player promise appears later.
InferenceFirst-time visitors may have to work too hard to understand the game's distinct appeal.
Confidence / unknownsMedium. Private conversion and wishlist data are unknown.
Findings 02–03Evidence labelled
02 · EvidenceA public community link resolves to an expired invite. InferenceA preventable trust break may interrupt intent.
03 · EvidenceRecent public updates use different calls to action. InferenceThe next audience step may be unclear.
Top priorityClarify the first promise on the public store page.
First fixRewrite the opening block and align its proof beat with one audience action.
Success signalCompare the studio's existing public-page intent signal before and after, if it is already measured.

Every real pack is grounded in the studio's own public material. Unknowns stay visible instead of being filled with confident-sounding guesses.

The journey

Public evidence to one optional implementation.

The sequence is visible before you submit anything. No hidden discovery gate and no need to expose private systems to learn whether the diagnosis is useful.

01Public links

Share the store, site, community, or public posts you want reviewed.

02Three findings

Receive three evidence-backed findings with inference clearly separated.

03Top priority

See which visible problem deserves attention first and why.

04First fix

Get one bounded repair instead of a broad transformation pitch.

05Success signal

Name what would indicate progress and what remains unknown.

06Optional 10-working-day implementation

Discuss the paid Sprint only if the diagnosis has earned trust.

No login, installation, private analytics, payment, or obligation. The findings are yours to keep.

Earn the implementation

Useful diagnosis first. Paid work only after.

The Studio Evidence Pack stands on its own. If one finding is credible and worth fixing, the Founding Case Study Sprint is the single paid bridge.

Free entryStudio Evidence Pack

Three findings, top priority, first fix, success signal, and the limits of the public evidence.

Owner decisionChallenge the finding

Question the evidence, inference, priority, or proposed measure before choosing any next step.

Optional paid bridgeOne focused Sprint

One agreed problem, implemented over 10 working days with a defined success measure.

Close the loopReview and handoff

Review the work, record the result honestly, and leave with a next-step recommendation.

The evidence pack is not a disguised sales call. The optional Sprint begins only after both sides agree on the concrete bottleneck.

Method, disclosed

The method stays inspectable too.

Software-assisted analysis plus human review. The evidence, assumptions, and limitations remain inspectable, and a person is accountable for what the pack recommends.

Sources visibleInference labelledUnknowns preserved

Implementation details are available when relevant, but technology is not substituted for acquisition proof.

evidence · assumptions · limitations

Clear boundaries

Keep control of the risk and the story.

The free entry artifact uses only public studio surfaces you provide. It is designed to be useful before credentials, private data, or a commercial decision enter the room.

Before any paid workPublic surfaces only

No login, installation, private analytics, payment, or obligation. Share only the links you want inspected.

After the pack arrivesYou keep the findings

Use them, challenge them, or walk away. Public use of your identity, quote, result, screenshot, metric, or confidential detail always requires separate approval.

No case study is implied by the illustrative format above. Every real result stays private unless the studio approves a specific public use.

The current paid path

Founding Case Study Sprint. One problem, fully bounded.

$1,500 upfront for month one and one focused 10-working-day implementation. The scope includes one review, handoff, a success measure, and a next-step recommendation.

One priorityAgreedThe evidence pack identifies the candidate; the Sprint starts only after the scope is mutually clear.
10 working daysFocusedOne implementation boundary, not an open-ended transformation or platform migration.
One reviewIncludedA deliberate point to inspect the work against the agreed problem and success measure.
HandoffIncludedThe studio receives the implemented work and the practical context needed to own it.
Success measureNamedThe signal is agreed without turning an unknown future result into a guarantee.
Next-step recommendationFinalContinue, adjust, or stop based on what the implementation actually showed.

No scarcity or outcome guarantee is added to the offer. The price and month-one scope above are the current terms.

After month one

Keep shaping the product without another access fee.

Months two through twelve of Alpha access are free for substantive feedback and case-study participation. That access does not grant automatic permission to publish anything about the studio.

Substantive feedback. Say where the product is useful, incomplete, or wrong in real operating conditions.
Case-study participation. Help document what was attempted and what the evidence did or did not show.
Separate approval every time. Identity, quote, result, screenshot, metric, and confidential detail each require specific permission before public use.
Honest withdrawal. Declining publication does not rewrite what happened or turn an unknown into a result.

Access and publication permission are separate decisions. Participation never makes private material public by default.

The offer, without hidden mechanics

One paid month. One focused implementation.

The Founding Case Study Sprint begins only after the free Studio Evidence Pack has identified a credible fit.

Month one includes
  • 01
    One agreed bottleneckThe implementation stays tied to the priority and evidence that justified it.
  • 02
    One focused 10-working-day implementationA bounded piece of work rather than an open-ended operating-system promise.
  • 03
    One reviewInspect the implemented work against the agreed boundary and success measure.
  • 04
    HandoffReceive the work, its operating context, and any limits discovered during implementation.
  • 05
    Success measureDefine the signal without guaranteeing an outcome that has not happened.
  • 06
    Next-step recommendationContinue, adjust, or stop based on the evidence after implementation.
Month-one price
$1,500upfront

One price for the defined first-month Sprint scope. No invented scarcity and no guaranteed result.

After month one Months two through twelve of Alpha access are free for substantive feedback and case-study participation.

EntryEvidence pack first

No payment or private access is needed to judge the initial diagnosis.

ScopeOne implementation

The 10-working-day boundary stays focused on the agreed first fix.

MeasureNo outcome guarantee

Success is measured honestly; unknowns and external factors remain visible.

PublicationPermission stays separate

Every public use of studio material requires separate approval.

The free evidence artifact and the paid Sprint are separate decisions. The implementation is optional.

ForgeOS maps discovery to purchase and shows exactly where attention, trust, and install intent need support.

DiscoverAudience fit and first promise.
TrustProof, social signal, store confidence.
ConvertWishlist, demo, purchase, follow-up.

Studio Evidence Pack

Start with evidence you can inspect and keep.

Share the public surfaces you want reviewed, or discuss one concrete bottleneck. We'll return to the evidence before suggesting implementation.

Public links onlyThree evidence-backed findingsNo obligation

Aura Forge is the studio and the vision. ForgeOS is the operating system it builds for game studios.

Studio Evidence PackPublic surfaces · yours to keep