00 / Arrival
Community architectAuthorSystem builder

JOEY

I build, grow, and manage online communities people actually want to be part of.

Community architect & author. I take a new or dying community and make it alive — then run the onboarding, governance, teams, events, and the growth & outreach that keep it that way.

DisciplineCommunity architecture
Experience7 years · 6 communities
StatusOpen for work
Anyone can open a server. I build the machinery that makes people stay.
Experience
7 years founding, running & directing communities
Scale
6 communities built & staffed · up to ~1,400 members
Craft
Cambridge C2, Grade A · novelist · every word written by me
Experience
7 yrs
Founding, running & directing communities
Built & staffed
6
Communities across RP, milsim & multi-game networks
Network scale
~1.4k
Peak members in Crimson Network
Launch velocity
2,508
Messages/day reached on Aurora by day 14
Onboarding target
24h
First real interaction in the Handler System
03DisciplineNine capabilities · one person
01

Community launch

Structure, channels, first events and the opening momentum most servers never get. Zero to active.

Launch
02

Onboarding systems

Turn sign-ups into regulars. New members reach a real first interaction within a day — not never.

Retention
03

Governance

Clear rules, fair enforcement tiers, mod-log discipline, and standards that hold under pressure.

Order
04

Leading teams

Recruit, train and structure a staff team with department heads — one that runs the place without you in the room.

Leadership
05

Growth & outreach

Grow through targeted outreach, partnerships and relationship-building — identifying relevant communities and decision-makers, personalised outreach and follow-ups, collaboration planning and long-term partnership development.

Growth
06

Events & engagement

Recurring events and campaigns that give people an actual reason to come back tomorrow.

Engagement
07

Writing & lore

Announcements, rules, guides and original worldbuilding that people actually read. I write every word.

Voice
08

Marketing & social media

Content planning, scheduling and multi-platform clip campaigns that pull new members from outside your server.

Reach
09

Setup & security

Full server setup, verification, anti-nuke and anti-raid protection, and the infrastructure that keeps it safe.

Infra
04SystemConceptual · not a data set

A community is a system, or it is a room that empties.

Fig. 04 — Community architecture Hover a hub · click to lock
Selected
subsystem

Acquisition & outreach

05Selected workTwo chapters
Project Aurora — arctic observation post under the aurora Case A2025 —

PROJECT
AURORA

Cold launch → a living world.
9 → 2,508messages/day by day 14
End to endonboarding to identity
 Open case study Crimson Shield International brand banner Case B2024 – 25

CRIMSON
NETWORK

Scale → a team that runs itself.
~1,400peak members
Handed offstructure outlived me
 Open case study Site-202 internal department structure Case C2023 – 24

SITE-202 "NEW WORLD"

Campaign first → launch second.
4,000+messages on day one
100members in the first week
17public dev logs
 Open case study
06Operating doctrine

Analyze. Structure. Activate. Sustain.

01 / Analyze→

Find the real friction

Map member behaviour, dead ends, staff load, onboarding gaps and the reasons people stop showing up. Fix the actual system, not the symptoms.

02 / Structure→

Build the machinery

Channels, roles, governance, progression, security, staff ownership and operating docs — designed as one connected system.

03 / Activate→

Create a reason to return

Launch momentum, first interactions, events, feedback loops and outreach that turn a server from technically open into socially alive.

04 / Sustain↻

Make it survive you

Train the team, distribute ownership, measure retention and keep improving until the community can run without one person holding it together.

07EngagementsThree problems I own end-to-end
01 / Launch→

Launch a community

Turn an empty server into a place with a structure, identity and opening rhythm people can actually enter. Server architecture & roles, launch plan & opening events, onboarding & first-contact flow, rules, moderation & security, initial staff structure.

02 / Repair→

Fix a dying community

Find where people drop out, rebuild around real behaviour and create reasons for members to return consistently. Community audit & diagnosis, retention & channel restructure, feedback and reactivation loops, events & engagement systems, growth & partnership plan.

03 / Scale→

Build a team that runs it

Replace founder-dependence with clear ownership, trained staff and documented systems that survive handoff. Staff roles & departments, recruitment & application flows, training & operating standards, escalation & accountability, clean handoff & continuity.

Full capability scope, track record and references live in the archive →

08The through-line
I'm a writer first.

Author of a completed science-fiction novel of approximately 90,000 words, a national-level writing award, and Cambridge C2 Grade A (Writing 200/200). Every announcement, rule and lore document in this portfolio is written by me — the tone of a community is the community.

≈90,000 words · completed SF novel Cambridge C2 · Grade A National writing award
Atmospheric world art — a window over a city at dusk
Worldbuilding — original art & text
LIVEFollow my workContent · profiles · services

Follow the work.
See the thinking.

Community breakdowns, practical systems, short-form ideas and the places where you can work with me.

09Open a line
Have a problem worth solving?
Start a conversation Book a call Browse the archive
Email
joeyinsync@gmail.com
Discord
joeyinsync
Upwork
Upwork profile
Fiverr
Fiverr profile
LinkedIn
LinkedIn profile
Status
Open for work