18/06/2026
The internal tool a team needs most is usually the one IT never gets to.
Too small for the roadmap. Too specific to outsource. Too useful to keep doing by hand.
A client's sales team had exactly this with their own case archive.
Years of projects lived in people's heads, in a 250MB file, and in a slide deck you could only search with Ctrl-F.
Every new proposal started with the same question: have we done something like this before, and where is it?
So two of them — managers, no engineering background — built the fix themselves.
A two-day hackathon, a few weeks of mentoring. The result is a search service: ask a question, get a short answer and cards of the relevant past projects, links included.
Underneath, a vector index of the archive and an LLM to clean up the phrasing.
The first version held together with workarounds. The clean idea — auto-syncing the archive from the slide deck — never worked.
So one of them packaged the data from a presentation overnight and shipped that instead.
This is the work that never reaches the IT backlog. When a manager can build the first working version themselves, it doesn't wait three to six months for a spec-to-release cycle.
That's what our vibe-coding program is for: managers without a technical background build their own internal tools, while IT sets the guardrails — approved data sources, repositories, review.
Not shadow IT. Not replacing engineers. Closing the gap they were never going to get to.
What's sitting in your backlog right now, waiting for IT bandwidth that isn't coming?