Every business tool starts with a form. Name, email, amount, date, category, submit. We threw all of that away.
The form tax
The old invoice workflow: open your invoicing app, pick a client, select a project, choose hours or line items, set amounts, add tax, preview, send. Four to seven minutes if everything goes right. With Leiko, you type: “Invoice Design Studio for February consulting, 20 hours at 120 per hour” — and in about 15 seconds you have a draft ready to review.
Invoice Design Studio for February consulting, 20 hours at 120 per hour
Why this works
Natural language carries context that forms can't capture. You don't have to remember which project code to select or which rate card applies. You say what you mean; the system figures out the rest.
The hard part: when conversation isn't enough
Ambiguity, complex edits, multi-item inputs — these still need structure. We're not replacing forms everywhere. We're replacing them where the cognitive overhead of filling out fields is higher than the cost of just saying what you want.
The architecture behind it
Intent extraction, context enrichment, tool selection, human confirmation. The flow: parse your message → enrich with unbilled hours, client info, tax rules → call prepare_invoice_draft, check_unbilled_hours, create_invoice — and surface a draft for you to approve before anything hits your books.
What we've learned
- Conversation works best when the user already knows what they want
- Fallback to structured forms is essential for edge cases
- Confirmation is non-negotiable — never auto-commit without human review
- Speed matters: sub-20-second feedback is the threshold where it feels magical
Want to try it? Join the beta →