The Honest Position
The speculative phase of Web3 gaming is over, and most of the studios that existed to serve it have gone with it.
What’s left is smaller and more serious: token projects that need genuine utility rather than a whitepaper, platforms building actual on-chain games, communities that want verifiable ownership of things they’ve earned, and brands who need a shared virtual space that isn’t a marketing render.
Those buyers have a specific problem, and it’s the same one that killed most of the previous generation of projects: the game was an afterthought. Enormous care went into the tokenomics and almost none into whether anyone wanted to play. Players arrived for the earnings, the earnings fell, and the game had nothing else to hold them.
We build the game first. The chain is a layer on top of something that works without it.
What We Build
On-chain assets and ownership. ERC-721 and equivalent standards for items, characters and squads, with trading and upgrade paths. In our football management sim, squad members are on-chain assets in a game where the league table, the season structure and the economy would still work if they weren’t which is exactly the test a project should pass.
Token economies. In-game currencies with modelled sources and sinks. An economy where every inflow is inflation and nothing removes currency will break within weeks of launch, and no amount of chain architecture prevents it. This is game economy design, and it’s separate from smart contract work.
Wallet integration and onboarding. Connection flows for players who already have a wallet, and a path into the game for the much larger number who don’t.
Play-to-earn and reward distribution. Earning mechanics with withdrawal, as in our social mobile title built for a token launch, where the game was the utility layer for the client’s currency.
Airdrop and campaign mechanics. Distributing tokens through something people actually play rather than a claim page. We built a set of instant-win and table game formats as the distribution layer for exactly this, on a backend designed to assume everyone was trying to farm it.
DAO and community governance. Team and asset ownership through shared wallets, with the in-game consequences of a governance decision actually implemented rather than symbolic.
Metaverse and shared virtual spaces. Multiplayer environments where headset and desktop users occupy the same room, with avatars, voice and things to do see the case study for what that involves technically. More on the delivery side in VR and XR development.
The Rule We Work By
The wallet never blocks the front door.
Gating the first session behind a wallet connection loses most of your potential audience before they’ve seen anything. Players who want on-chain ownership get it, on their terms, at the point where it means something. Everyone else plays a game and can opt in later, or never.
This costs you nothing except the satisfaction of a purist architecture, and it’s the difference between a product with an audience and a product with a community of holders.
Store Policy Is Not Negotiable After the Fact
Apple and Google both have specific policies covering cryptocurrency functionality in apps, and they’re enforced at review rather than discussed afterwards.
What happens inside the app, what happens outside it, and what the app is permitted to say about either, those are architecture decisions made before development starts. We’ve shipped mobile titles through this, and the cost of designing for it upfront is a fraction of the cost of a rejection two weeks before a token launch.
Browser delivery avoids the problem entirely, which is one reason a good share of Web3 games belong in WebGL rather than an app store; no review, no install, and it opens inside the in-app browsers where a lot of this audience already lives.
Chains and Tooling
We’ve shipped on BNB Chain and Polygon, and worked with Polkadot, whose logo sits among our clients. Contract integration through thirdweb, avatars via Ready Player Me, and AI-driven NPCs with Convai where a project calls for them.
Chain selection is a project decision, not a preference. Fees, finality, wallet penetration among your actual audience, and where your community already is matter more than the technical merits.
Common Questions
Yes, most of our Web3 work integrates with what a client already has deployed rather than starting from zero.
Depends on your audience, your fee tolerance and where your community already holds assets. It’s a conversation worth having before the architecture rather than after.
It should. That’s our design rule, and it’s also your insurance policy: if the token layer changes, gets delayed, or a store objects, you still have a product.
Start a Project
Tell us what exists already; a token, contracts, a community, a game and what’s missing. If you’re early enough that the economy isn’t modelled yet, say so; that’s a useful conversation to have before anyone writes code.
Scope, team composition and a fixed quote come back within two business days. We also work as co-development or team extension where you have a team and need the game or backend layer specifically.