Process
How a project actually runs
Nine steps, from first inquiry to final invoice — no surprises in between.
Typical timeline: 3 weeks for a micro project, up to 9 weeks for a medium one.
Inquiry
You reach out with your project idea — through the contact form, however rough the idea still is.
Discovery call
I talk through goals, wishes, materials, and budget directly — no forms, just a conversation.
Design brief & quote
A written brief scoping what's in and out, with a quote structured as MVP plus optional extras, so you can scale the project to your budget.
Deposit (50%)
Due on accepting the offer — production begins as soon as the deposit lands.
Concept phase
First visual drafts of UI and gameplay, with a feedback round before moving forward.
Gameplay construction
A playable but non-final build, with a feedback round focused on mechanics.
Final polish
Feedback on a finished but not-yet-tested build — bugs may still show up at this stage, and that's expected.
QA & delivery
Testing on the devices and platforms agreed with you, then final delivery.
Final invoice (remaining 50%)
Due on delivery.
I know my boundaries — and I've already got a plan for the edge cases.
QA, stated openly
Standard QA covers phone, tablet, and desktop across Chrome, Firefox, Edge, and Safari via BrowserStack — that covers the large majority of real-world bugs. QA isn't the studio's core specialty, and I say so upfront: if a project needs broader device or OS coverage, that's arranged through an external QA partner and scoped into the budget at the brief stage, not discovered as a surprise later.
AI-assisted workflow
Modern AI-assisted tools are used selectively across concepting, art, and development — it's part of how a single-person studio delivers studio-level production without studio-level overhead or timelines. This is a deliberate production choice backed by 20+ years of non-AI craft, not a shortcut: the work can be delivered fully without these tools, and using them selectively is what keeps fixed pricing realistic while a human designer makes every real decision.
Yes, AI tools are an optional part of the toolkit — and yes, a human is still doing the designing.
Tools
- Godot
- Figma
- Affinity
- Blender
- Claude Code
- ComfyUI
Communication adapts to your own stack — MS Teams, Slack, email, whatever your team already uses — rather than imposing a fixed tool on you.
After delivery
Engagement normally ends at delivery. Game-breaking bugs found within 3 months post-launch are covered under the original contract at no extra cost, excluding issues caused by platform updates or external circumstances outside the studio's control. Hosting and ongoing live-ops support aren't standard, but can be scoped and added — worth raising at the discovery call so it's planned for, not left implicit.