01
Step one: name the two or three people and roles
Start with who is making the work and what each person does. Avoid vague collective language; give each member a first name, a role and one concrete responsibility. Example: a two-person team might say Mara designs the levels and puzzles while Eli builds the tools and sound. Readers, publishers and potential collaborators want to know who they would actually talk to. Keep each bio to two sentences, add a single line about why the pair works together, and leave out credentials that cannot be verified or shown on request.
02
Step two: describe the first project in plain terms
Next, explain the first project as a small, specific promise rather than a grand vision. State the genre, the number of players, the core action and the current stage, such as concept, prototype or playable demo. Example: a two-player cooperative game where one person scouts and the other builds shelter, currently in prototype with a short test build planned. Say what is finished and what is not. This honest framing builds trust and gives visitors something clear to follow, test or support, without implying release dates or audiences that do not yet exist.
03
Step three: give visitors one clear next action
Finish the page with a single action that matches the stage of the project. A prototype might invite readers to join a playtest list, a finished build might link to a store page, and a service might invite a project brief. Example: end with a short note saying the team shares a monthly development log and welcomes feedback from cooperative-game players. Keep contact details simple, name who replies, and review the page after each milestone so the team story, project status and call to action always match what is real.