End-to-end responsibility
A solo game project forces the full chain: scope, systems, UX, validation, release posture, documentation, and public communication.
Recruiter-facing profile · independent studio chapter
I'm a solo developer following a lifelong dream of building games for Steam.
I'm Brendan Davies: a systems-led builder with SaaS, workflow, AI operations, and product execution experience. I'm also realizing a lifelong passion by building an independent game studio from the ground up.
The game itself stays private for now. The public signal is the journey, the operating discipline, and the proof of ownership.
The honest story
A solo developer chapter, not a disappearing act.
Building a game studio is not separate from my professional story. It is the clearest expression of how I work: reduce ambiguity, build systems, test the loop, control scope, and keep moving when the work crosses product, design, engineering, and operations.
For recruiters and hiring teams, this matters because the same discipline shows up in serious work: ownership, judgment, written clarity, AI-assisted execution, risk control, and the ability to turn messy intent into a working path.
Proof signals
What the studio journey demonstrates.
Readable complexity
My strongest work is turning complicated state into something humans can understand, trust, and improve.
AI as leverage, not theatre
I use AI to accelerate research, validation, refactoring, documentation, and critique while keeping human review and decision authority intact.
Home lab + local Gitea
Built and maintain a personal home lab with self-hosted Gitea repositories: sovereign, offline-first workflows under my control, with the same reliability principles I bring to product and technical roles.
Role fit
Where I add the most value.
I fit best where systems thinking, customer reality, technical judgment, and product execution need to meet in one person.
Systems architecture
Operating models, workflows, internal tools, validation loops, and migration shapes that stay readable under pressure.
AI workflow reliability
Practical AI-assisted execution with boundaries, review gates, context hygiene, and measurable outputs.
Product-minded delivery
Reducing ambiguity, sequencing work, testing assumptions, and keeping the user or customer outcome visible.
Commercial empathy
Experience across customer-facing, operational, and technical surfaces where handoff quality changes outcomes.
Hubsays Studio
The studio is the public creative container.
Hubsays is where the independent studio story lives. It is intentionally separate from this site so recruiters get a clear professional signal here, while the studio has room to become its own thing.
The first Steam title is private until the work is ready. That restraint is part of the operating model: build the foundation first, then earn the reveal.
Open Hubsays StudioFor recruiters and hiring managers
The studio journey is a proof surface for ownership, not a reason to ignore the professional one.
The useful question is not "is Brendan building a game?" It is "what does this reveal about how he thinks, ships, learns, tests, communicates, and handles ambiguity?"