Case Studies

CASE STUDY · AI-ORCHESTRATED PRODUCT BUILD

An AI game prototype—20 years in mind, playable in 3 days.

A persistent city builder escaped the backlog when AI and QUIQQER collapsed the distance between idea and implementation.

Hen had carried the idea for Hell's Contractor for roughly twenty years but never found the time to build it. With a structured concept, continuous human direction and AI implementation on QUIQQER, it became a playable browser prototype in three days. The website followed later as a separate, editable product home.

Visit Hell's Contractor See the implementation
3 days
From concept work to playable prototype
~20 years
The idea waited for a viable way to build it
0 lines
Personally programmed by the human director

THE PROJECT

Keep the full ambition. Remove the implementation bottleneck.

The breakthrough was not a smaller game idea. It was a workflow able to carry a large one.

Hell's Contractor began as a long-held vision for a calm, persistent city simulator set in Hell: one city across many sessions, systems to shape and no victory screen forcing an ending. There had never been enough time to turn that vision into a real product.

The first focused concept session gave the AI a structured foundation covering vision, systems, MVP, balance, map, interface, technology, data, assets and roadmap. Human intent, taste, testing and correction stayed in the loop while the implementation moved at machine speed.

THE CHALLENGE

Turn a long-held world into a working system without sanding off its character.

Externalize the vision

The game had lived in one person's head for roughly twenty years. The first task was to turn taste, pace, systems and boundaries into context an AI workflow could act on.

Design before implementation

The initial concept session produced a structured foundation for vision, MVP, balance, map, interface, technology, data, assets and roadmap.

Keep human direction

AI handled the implementation; Hen supplied intent, testing, corrections, priorities and the judgment to reject technically valid work that did not fit the game.

Add the front door later

Once the playable city existed, a separate QUIQQER website made its systems understandable and gave development, help and future product flows a coherent home.

AI-ORCHESTRATED PRODUCTION

Context, direction and iteration turned AI output into a playable product.

The workflow was not a one-line request to “make a game.” It was a guided production loop: explain the world, define constraints, inspect the result, correct misunderstandings and keep moving toward a clear experience.

  • Structured product context before implementation
  • Human taste and priorities kept in the loop
  • AI responsible for the implementation
  • Playable browser prototype after three days
Playable Hell's Contractor prototype showing the city interface and its first-run onboarding dialog.
The current browser prototype exposes a real simulation interface and onboarding flow—not a static concept mock-up.

THE IMPLEMENTATION

One clear idea, translated through five connected steps.

01

Define the experience

A calm, persistent infernal city builder: one city across many sessions, deep systems, no FOMO and no final screen.

02

Build the context

The first focused hour established the design foundation the AI needed to reason consistently across systems and assets.

03

Implement the prototype

AI and QUIQQER turned the structured concept into a playable browser prototype over three days.

04

Direct and refine

Hen tested the work, corrected misunderstandings, changed priorities and protected the intended pace and atmosphere.

05

Create the product home

As a later step, Codex worked through QUIQQER's real pages, media, navigation, settings and reusable components to build the live website.

ONE SYSTEM, TWO STAGES

The prototype came first. The website followed later.

The three-day claim belongs to the playable game prototype. The public website was a separate next step: a native QUIQQER product layer for game guides, system data, Chronicle posts, help, social previews and search visibility. Because it uses real CMS structures rather than a one-off generator, people and agents can continue working on the same product.

THE RESULT

The idea did not get smaller. The path to it did.

Hell's Contractor became a playable, explainable and extendable product without separating human direction from AI implementation.

Playable in three days

A long-held concept became a functioning browser prototype in a verified three-day implementation window.

Human-directed

Intent, taste, testing, corrections and priorities remained human responsibilities throughout the build.

Built for the long game

The result is a persistent systemic city builder designed for one city across many sessions—not a disposable demo round.

Made understandable

The later website explains systems, buildings, residents, progression and development before asking visitors to enter the game.

Native and editable

Pages, media, navigation, settings, reusable components and publishing states remain real QUIQQER structures.

Ready to extend

The same product home can grow toward purchase, account and download flows as the game moves forward.

AI & MCP

Ready to connect your AI agent?

Connect AI clients to public QUIQQER skills, installation guidance and the capability catalog; machine-readable setup instructions are available in llms.txt.

https://www.quiqqer.com/mcp