Work
Roblox worlds for ourselves — and programs or websites when the brief is sharp. Same bar. No leftover template.
Worlds
We take a brief and turn it into a place: space, lighting, UI, the rules underneath. Prototypes stay playable. If a mechanic does not feel right in the first ten seconds, we cut it. You get a world that can go live — not a folder of unfinished places.
Commissioned
Landing pages, tools, small systems, PHP where the host expects PHP. Same standard as the games: dark, considered, no leftover template. If we cannot do it well, we will say no rather than stretch.
Process
01
A useful brief is a paragraph, not a deck. What the thing is, who walks through it, what must be true on the day it ships. We push on scope before we open a file. If the idea is a catalogue of features with no feeling underneath, we will say so. This is the cheapest moment to be honest.
02
We make something you can stand in or click through. For a world that means a playable slice: one loop, one space, the camera already telling the truth. For a site that means real type, real rhythm, a page that is already the page. We do not hide behind wireframes once the feel is the question.
03
Production is the long stretch and we do not vanish inside it. You see builds. We cut what is not earning its place. Systems get simpler, lighting gets more expensive, copy gets shorter. The last ten percent is not polish for a screenshot — it is the difference between a place people bounce off and a place they stay in.
04
Launch is a Tuesday, not a ceremony. We watch the first sessions, patch what breaks, and leave the thing in a state you can actually run. If it is our world, we keep tuning. If it is yours, you leave with the files, the host, and a studio that will still answer mail.
Scope
We can start from a blank place or from something already live that needs a second life. You remain the owner of the experience unless we agree otherwise. After launch we stay for the first wave of fixes, then the world is yours to run — or we keep it in-studio if that is the deal.
Typical asks: a studio site, a tool behind a login, a contact pipeline that actually mails, a landing page that does not look like a template. We are host-aware. If your server is PHP, the form can be PHP. No framework for its own sake.
If the brief is “make this existing game, but ours”, we will pass. We build places, not clones.
We will not promise virality, influencer packages, or a player-count we cannot stand behind.
Open-ended retainers with no “done” are how work gets thin. We want a ship date, even a soft one.