Define the Build Cycle company
A software-company simulation prompt should distinguish build progress, operating costs and revenue timing. Build Cycle is a fictional four-month studio with one Developer and one Sales employee. The company starts with 30 cash, no product and no subscribers. Payroll is five cash at the start of each month.
Each month processes in this order: pay payroll; bill existing subscribers at four cash each; pay one cash support cost per existing subscriber; choose one focus action. Build increases project progress by one, and progress two launches the product. Sell adds one subscriber after billing, so that new account starts paying the following month.
The win condition at the end of month four is a launched product, at least two subscribers and cash of 13 or more. The company loses if cash reaches zero or below before the deadline, or if the target is not met by month four. There are no loans, taxes, churn, feature requests or variable salaries.

Separate launch, billing and support timing
The billing order protects the meaning of recurring revenue. A subscriber acquired in month three does not bill until month four. A subscriber sold in month four begins billing in month five, outside this scenario. Support cost applies only when an existing subscriber is billed.
The focus action follows payroll and billing. Build is legal until launch; Sell is legal only after launch. If a focus action is illegal, the turn is wasted but monthly payroll and existing subscriber billing have already occurred. Restart returns cash, employees, progress, subscribers and month number to their initial values.
The sequence lets a reader see a tradeoff: two early Build actions launch the product, leaving only two months to sell. Revenue arrives after customer acquisition, so end-of-run cash depends on the billing delay.

Trace the example
Month one: payroll leaves 25 cash; Build raises progress to one. Month two: payroll leaves 20; Build reaches progress two and launches. No subscribers exist yet. Month three: payroll leaves 15; no subscription billing occurs; Sell adds the first subscriber, which begins billing next month.
Month four: payroll leaves cash at 10. The existing subscriber pays four and incurs one support cost, so cash rises net three to 13. Sell adds the second subscriber after billing. At the deadline the product is launched, there are two subscribers and cash is 13, meeting the stated goal.
This is fictional cash-flow arithmetic, not a forecast or real startup guidance. A future build should log each month phase, payroll, subscriber count before billing, revenue, support cost, action and ending cash.

Write the six prompts
Use one prompt per design decision so later checks have a clear source of truth. These drafts describe Build Cycle; they have not been run and do not represent a generated playable game.
Prompt 1: create company starting state
Create a four-month software studio simulation. Start cash30, one Developer and one Sales employee, payroll5 each month, progress0, no product, zero subscribers.Prompt 2: set monthly resolution order
Each month resolve: payroll, revenue from existing subscribers at4 each, support cost1 each, then one focus action. Existing subscribers pay before a new sale is added.Prompt 3: define build and sales actions
Build adds1 progress; at progress2 product launches. Sell adds1 subscriber only after launch. A new subscriber starts billing the following month.Prompt 4: set goal and failure
Win at end month4 if product launched, subscribers≥2 and cash≥13. Lose if cash≤0 or goal is unmet at deadline. No loans, taxes, churn or variable cost.Prompt 5: handle illegal focus and reset
Reject Build after launch and Sell before launch. If action is invalid, it is wasted after payroll/billing. Restart restores cash, staff, project, subscribers and month1.Prompt 6: prepare future checks
For future checks log monthly phase, payroll, existing subscribers, revenue, support, action, progress, launch, new subscribers and cash. Check billing delay, same-month sale, support cost, launch, deadline and reset. Do not claim tests passed without a build.SEELE’s official page describes general plain-English prompting, a playable first version, browser testing and refinement; it does not verify Build Cycle. See Free AI game maker for workflow context only.
Prepare future build checks
Reconcile the four-month ledger phase by phase. Confirm new subscribers do not bill in the same month, existing subscribers incur support, and the sample ends at 13 cash with two subscribers. These are future checks, not passed tests. Record the before and after state so a later build can be compared with the specification.
| Future check | Expected rule | Evidence to capture |
|---|---|---|
| Payroll | Five cash paid at start each month | Starting and remaining cash |
| Build/launch | Progress2 launches product | Progress and launch flag |
| Billing delay | Only prior subscribers pay at4 each | Subscriber count before/after billing |
| Support | Existing subscribers cost1 each | Revenue and support lines |
| Goal/reset | Two subscribers, cash13 by month4 | End state and restart snapshot |
No real game run, browser test or measured result is available for this fictional example. The illustrations are original concept art and are not screenshots.
Frequently asked questions
What should a software-company simulation prompt define?
Specify build milestones, payroll, sales actions, recurring revenue timing, support costs and the deadline.
When does a new Build Cycle subscriber start paying?
The new account starts billing in the following month, not the month it is sold.
How much does each subscriber generate and cost?
Each billed subscriber brings four cash and incurs one support cost per month.
Were these software-company prompts tested in a playable game?
No. Build Cycle is a fictional simulation example and not real startup advice or a tested product.
How does the sample reach 13 cash?
Payroll leaves 10 by month four; one existing subscriber adds 4 revenue and costs 1 support, reaching 13.


