← All case studies

Built with UCAGEN / Business application

Banking Manager

A banking client application developed autonomously by one developer in 11 hours.

Human involvement during the reported run: approving permission requests.

Autonomous development
11 hours
Logic atoms
258
Java classes
827
Lines of code
~83,000
Tests
1,312

Results reported by the creator in the UCAGEN presentation, slide 4.

The manager workspace, shown with demo customer data. Click to enlarge; close the preview to return here.

A Workspace for Banking Operations

Customers and daily work

The displayed workspace includes a customer directory with search, sorting, status filters, pagination, and actions to create or open a customer record.

Connected areas of the application

The navigation exposes requests, tasks and appointments, notifications, applications, a product catalogue, settings, and a timeline and audit area.

One Developer. An Autonomous Workflow.

The reported 11-hour run belongs to one developer, not a development team. UCAGEN supplies the deterministic application architecture, with AI assistance before and after skeleton generation.

  1. Prepare the specification. Clarify the application's purpose, user workflows, and expected behaviour.
  2. Generate the architecture. UCAGEN produces the application skeleton using the Invariant Pattern.
  3. Implement the application. AI post-processing works within the generated structure to implement logic, interface elements, and tests.

The creator reports approving permission requests as the human involvement during autonomous development.

Understanding the ~100× Estimate

Reported run: 11 hours of autonomous development by one developer.

The creator estimates an acceleration on the order of 100× compared with conventional development by a senior developer using AI agents. This is an indicative comparison, not a measured head-to-head benchmark.

The presentation uses an illustrative baseline of six months at 160 working hours per month: 960 hours. Dividing that estimate by the reported 11 hours gives approximately 87×, expressed at a rounded scale as ~100×.

The conventional-development baseline is an estimate. Actual time depends on scope, developer experience, quality requirements, and the definition of completion.

Explore What You Could Build

See how the same approach applies to a different kind of client application, or learn how to define your first UCAGEN project.