What happens when Claude Code (Haiku) and WorkSimplified start with the same request for an employee leave management app? This comparison looks at what each route delivered: the features people can use, the time and cost reported, and what the customer receives at handover.
The starting prompt
“Build an employee leave management app where employees can apply for leave and managers can approve or reject it”
The core task: an employee submits a leave request, and a manager approves or rejects it. The table below shows what was delivered around that workflow.
WorkSimplified pilot handover
Leave requests
Employees apply for leave
Manager review
Approve or reject requests
3 user roles
Employee, Manager, Administrator
User manual
Role-by-role instructions
A hosted leave-management demo with employee and manager workflows, administrator access and a user guide. Compare the delivery scope, build time and cost below.
01
Delivery comparison
What each route handed over for the same leave-management use case.
| Delivery criterion | Claude Code (Haiku) · reported build | WorkSimplified · verified pilot |
|---|---|---|
| Core leave workflow | Applications, balances, tracking, approvals, validation and history. | Leave workflow on an Existing ERP System, with Employee and Manager workspaces. |
| User roles | Employee and Manager. | Employee, Manager and a scoped Administrator. |
| Requirements discovery | Not generated by coding agent. | Conversational discovery, requirements review and build confirmation. |
| Administrative controls | Not generated by coding agent. | Manage employees, leave types, allocations and holidays. |
| Deployment handover | Not ready to deploy, as reported. | Working hosted demo delivered. |
| Tested in use | No test results supplied. | Leave requests, manager decisions, balances, role access and the user handover were tested. (See what each group covered below.) |
| User documentation | Not generated by coding agent. | 19-page user manual with nine screenshots covering all three roles. |
| Application foundation | SQLite-backed application. | Existing ERP System. |
What was tested in everyday use
- Could employees request leave and managers act on it?
- Employees submitted leave requests, and managers approved or rejected them. Approval deducted the expected one day from the leave balance; rejection left it unchanged. Cancelling a pending request was also tested.
- Could each person access the right workspace?
- Employee, Manager and Administrator accounts were used to sign in and open their workspaces. Tests also checked that users could not look up employee records or leave balances outside their permitted access.
- Could the customer use what was handed over?
- The public portal displayed account login details and explained the features available to each role. The handover screen was checked at different screen sizes, and the PDF user manual could be downloaded.
WorkSimplified brings the leave workflow, administrative controls, hosted evaluation and user documentation into one handover using an Existing ERP System.
02
Build time, usage and cost
The recorded time, token usage and cost for each leave-management build.
| Pilot measurement | Claude Code (Haiku) · reported build | WorkSimplified · verified pilot |
|---|---|---|
| Pricing reference | Haiku | Haiku |
| Build time | 20 min | 4 min 40 sec |
| Total tokens | 2,192,100 | 271,374 |
| Cost (USD) | $0.4188 | $0.0751 |
03
Scope and delivery details
1Comparison scope
Both routes started with the employee leave-management request quoted above. The Claude Code column reflects the supplied build record; WorkSimplified’s features and workflows were checked in the delivered demo.
2Timing and tokens
Build time covers application generation; requirements discussions, manual investigation and handover review are separate. WorkSimplified reused prepared hosting infrastructure. Token totals are the recorded usage for each build.
3Delivery format
The WorkSimplified handover included a temporary hosted demo, Employee, Manager and Administrator accounts, and a role-by-role PDF user manual. The workflow tests described above cover the delivered leave-management scenario.
Employees could request leave, managers could act on it, and each role had its own workspace.
Comparison based on the leave-management builds recorded on 20 October 2026. Questions: [email protected].