Case study · New contest product

One engineer. A whole product.
Written by AI.

A daily sports-contest product — accounts, contests, subscriptions, payouts — was written entirely by AI and directed by a single engineer. The Laravel API, the web front end, and the mobile app shipped together. The mobile app was released on the App Store in about four to five months.

Industry
Daily sports contests
Engagement
New product, AI-written
Team
1 engineer
Timeline
~4–5 months to the App Store
1
Engineer on the build
Directing the work
100%
AI-written code
API, web, and mobile
3
Surfaces, one pass
Backend, web, mobile app
~4–5 mo
To the App Store
From an empty start
The starting point

The usual way this gets built is a team

Nothing was broken, because nothing existed yet. A product like this — sign-up, contests and markets, a leaderboard, subscriptions, payouts, notifications, support — is normally a human workflow from the first ticket. Specialists write the API. Other specialists write the web UI. Another group writes the mobile app. A store release sits at the end of all three calendars.

That default is the thing this project replaced:

  • Hand-written, by a team. Application code is something people type, review, and hand from one specialty to the next. Headcount is how scope gets covered.
  • Three surfaces, three schedules. A Laravel API, a web front end, and a mobile app rarely start together or finish together.
  • The store is the last mile. An App Store release usually means the people are done, which means the calendar was already long.
  • The workflow is the cost. The expensive part is the human chain that produces the code, long before hosting or the store listing.
What we built

The whole product, written by AI

One engineer directed it. AI wrote the application: the backend, the web front end, and the mobile app. The result is a daily contest product a member can join, play, subscribe to, and get paid from — including the app that went to the App Store.

  • The Laravel API. Accounts, contests, sports data, subscription billing, and payouts. The system of record for the product.
  • The web front end. The same product in the browser, on that API, built in the same pass.
  • The mobile app, on the App Store. Sign-up, contests and markets, a leaderboard, subscriptions, payouts, and the account itself. It shipped.
  • One engineer across all of it. The API, the web UI, and the mobile client were produced the same way. A human implementation team was never the plan.
Before & after
 Human workflowAI workflow
Who wrote the codeA team, by handAI, directed by one engineer
SurfacesSplit across specialtiesAPI, web, and mobile together
WorkflowHuman, from the first ticketAI, from the first commit
TeamThe usual several1 engineer
ReleaseThe end of a long buildThe App Store
CalendarQuarters per surface~4–5 months for the product
How one person did it

AI wrote it. A person directed it.

This was an AI workflow from the start. The engineer’s job was the product: what to build, in what order, and whether it was actually the app a member would use. The application code — backend, web, and mobile — was produced by AI.

100%
of the application code was written by AI. One engineer directed the Laravel API, the web front end, and the mobile app through to an App Store release.

What that covered:

  • All three surfaces, one method. The hand-off from a backend team to a web team to a mobile team never had to exist.
  • A store release. The mobile app went to the App Store. That is a product a member can download.
  • The same window as a conversion. About four to five months, which is how long these engagements run — here, from an empty start to the store.

It sits beside a different kind of proof. A five-year sports platform, already in market on a Laravel API and mobile apps, made the opposite move in a similar window: a large human operation turned over to an agent model and a knowledge graph, inside the product customers already used. Read that story.

The impact

A shipped product, staffed as one person

The outcome is the scope that made it to the store, and how few people it took to get there. The calendar is the same length we quote for converting a live product.

1
Engineer
Directing AI across the API, the web front end, and the mobile app.
100%
AI-written application
Backend, web, and mobile. The implementation was the AI workflow.
~4–5 mo
Empty start to the App Store
The whole product, in the window these engagements run.

Four to five months is the window the build ran in. “100%” is how the application was produced: AI wrote the code, one engineer directed it, across the API, the web front end, and the mobile app.

A product you want in market, without a team to type it?

API, web, and mobile, directed by one person and written by AI. Fifteen minutes is enough to see whether the thing you want fits that shape.

Book a call→All case studies