A game studio site is not a SaaS site
SaaS advice assumes one reader with one question. A studio site has four audiences whose needs conflict, and the work itself is the argument rather than an illustration of it.
Most advice about product websites assumes one reader with one question: will this tool solve my problem, and what does it cost. A game studio site has neither the single reader nor the single question, and applying SaaS patterns to it produces a site that is tidy, legible and completely inert.
The difference is not aesthetic. It is that the two sites are doing different jobs for different people at different points in time.
Four audiences, one page
A SaaS marketing site has a buyer and, sometimes, the engineer who will have to live with the decision. A game studio site is read by at least four groups whose needs actively conflict:
- Players, who want to know what it feels like and when they can have it.
- Press and creators, who need assets, facts and a contact, quickly, usually against a deadline.
- Publishers and partners, who are assessing whether the studio can finish things.
- Prospective hires, who are reading the same pages as evidence of what working there is like.
A SaaS site resolves competing audiences by segmenting — "for engineering", "for finance". A studio site usually cannot, because it is small and the same few pages have to serve everyone. The resolution is ordering rather than segmentation: the work first, because it is the only thing all four groups came to see, and then the specific needs each group has after it.
The work is the pitch, not an illustration of it
On a SaaS site, the screenshot supports the sentence. On a game studio site the relationship inverts: the trailer, the art and the moving image are the argument, and the words exist to frame them.
This has a concrete consequence for layout. Copy-led patterns — headline, paragraph, feature grid — subordinate media to text and make a game look like a product. What works instead is giving the media room and letting the text be captions, labels and credits around it.
A SaaS site explains and then shows. A studio site shows and then explains, and the second half is shorter than anybody expects.
The tension nobody escapes
That argument runs straight into performance. The asset that sells the game is heavy, and the people arriving are often on a phone, from a link in a feed.
Both naive answers are wrong. Compressing everything until it loads instantly sells nothing, because the thing being sold is how it looks. Shipping the full trailer on page load means a large share of visitors leave before it decides anything.
The decisions that actually resolve it are ordinary engineering ones: a poster frame that carries the feeling on its own, video that loads on intent rather than on arrival, dimensions reserved so nothing moves when media lands, and the first meaningful thing on screen being something cheap. There is more on that class of decision in what production-ready actually means.
The conversion is not a signup
A SaaS site's goal is use the thing now: trial, demo, signup. A game frequently cannot be bought yet, which changes the whole shape of the page.
When the product is not purchasable, the only available action is a promise to come back — a wishlist, a follow, a mailing list. That is a weaker commitment and it has to be asked for differently: once the person has seen enough to want it, not in a banner before they know what the game is.
It also means the site's job is partly to be re-visitable. A SaaS site converts a visitor once; a studio site may be visited across months by someone waiting for a release, which puts a premium on the site being obviously current — a dated news entry does more for credibility than another paragraph of description.
Press needs, which SaaS does not have
A journalist or creator covering a game needs a small, specific set of things: logos that work on both backgrounds, screenshots at usable resolution, a factual description nobody has to paraphrase, a release status, and a human to contact. Not finding them in one place is often the end of the coverage, because there is always another game.
SaaS sites have no equivalent surface, which is why this is the single most commonly missing page on a studio site built from SaaS references.
Tone is a correctness question here
On a SaaS site, restraint reads as credibility and heavy styling reads as a risk. On a studio site the calculation inverts: a neutral, well-spaced, sans-serif marketing page tells a player the work has no point of view. The site is a sample of the studio's taste, and that is a thing the audience is explicitly evaluating.
That does not license illegibility. The practical line is that the atmosphere belongs to the media and the frame around it, while the things people must read — dates, platforms, prices, contact — stay plain. Expressive where it is being felt, boring where it is being used.
HYS Games is a client project of this kind: a website for a game studio, designed and built end to end.
If you are briefing one
- Name the four audiences and decide, explicitly, which one the first screen is for.
- Decide what the single strongest asset is, and build the page outward from it rather than fitting it into a template.
- Decide the action for someone convinced today when the game is not out — and put it after the work, not before it.
- Make the press surface real: logos, screenshots, a factual blurb, status, a contact.
- Check it on a phone over a poor connection, which is how a link from a feed actually arrives.
- Keep every date and platform plain, however atmospheric the rest is.
If you are building a site for work that has to be felt before it is understood, tell us what you are building.