Agent-led dev use case
Build Internal Tools From Process Notes Instead Of Waiting For A Project
Many useful internal tools never get built because they start as messy spreadsheets, Slack threads, or process notes rather than polished specifications.
Codex internal tools training Switzerland
Swiss SME workflow
Workshop-ready
Human approval by design
Before AI
How it looks today
- Operations teams maintain manual trackers.
- Developers ask for clearer requirements.
- Temporary spreadsheets become permanent systems.
- Small tools never justify a formal project.
What AI can do
The first useful pass
- Convert a workflow description into an app skeleton.
- Generate forms, tables, filters, and simple dashboards.
- Create tests and validation rules.
- Iterate the UI with the people who do the work.
Humans approve
What stays in human hands
- Data storage and access model.
- Production hosting.
- Integrations with finance, CRM, HR, or customer data.
Tools involved
The stack we usually meet
- Codex
- Claude Code
- GitHub
- Vercel
- Railway
- Postgres
- Google Sheets
Workshop exercise
Build internal tools from notes
Bring one spreadsheet or process note. We turn it into a scoped internal tool prototype and define what must be true before launch.
Expected outcome
A working prototype path for small internal tools that would otherwise stay trapped in spreadsheets.
Bring this to a workshop →