I build tools for the problems I actually face as an IT Business Analyst — requirements wrangling, API documentation, vendor communication. Most started as a script. Some became something better.
Takes vague stakeholder input and turns it into structured user stories, acceptance criteria, and spec-ready requirements. Try it now.
A structured library of functional specification templates — API integrations, feature specs, gap analyses. Built for fintech, usable anywhere.
Hands-on workshop applying AI to real BA workflows — requirements gathering, spec writing, JIRA, vendor management.
Extract structured knowledge from Swagger/OpenAPI files — auto-generating summaries and use-case descriptions for non-technical audiences.
Describe a bug or feature in plain language. Get a properly structured JIRA ticket with title, description, acceptance criteria, and priority.
A searchable, categorised library of AI prompts for business analysts — organised by workflow: requirements, gap analysis, vendor comms, testing.
Every tool starts because I needed it — not because it seemed like a good idea. If I am not the first user, I do not build it.
No feature bloat. Each tool does one thing well. If I am adding a fifth tab, I am probably building two tools.
The people who most need these tools often cannot code. Good UX is not optional — it is the point.
Beta means beta. If you use any of these and something is wrong or missing — tell me. That is the fastest path to better tools.