09 Internal tools · Build In build
One front door for every internal tool a 250-person company builds
Teams across a 250-person company were each building their own internal apps, with no shared place to find, vet, or trust them. We built the directory that fixes it.
- A team builds a tool
- Submission
- Searchable catalogue
- Ratings & governance
/ The numbers
- 250
- person company, one directory
- SSO
- frictionless, secure sign-in
- Reviewed
- every tool, before it lists
01 The problem
Across a company of 250 people, individual teams had started building their own small internal apps. Useful, but invisible. Nobody outside the team that built a tool knew it existed.
The result was duplicated effort, no quality bar, and no way for an employee to find the tool that would save them an afternoon.
02 The approach
We built an internal app directory: one place every team publishes the tools they build, and everyone else discovers them.
Single sign-on so it is frictionless, a submission flow with an admin review step so quality stays high, and ratings so the good tools rise.
03 What we built
- Internal app catalogue, searchable and filterable by team and scope
- Single sign-on through the company's existing identity provider
- Submission flow for any team to publish a tool
- Admin review console to approve, organise, and govern entries
- Ratings and reviews, so quality is visible
- A role and permission model across the whole directory
04 The outcome
- Internal tools stopped being invisible to the people they would help
- Every new tool passes a review before the company sees it
- Teams stop rebuilding what another team already shipped
Anshul's just been a terrific partner. He's very trustworthy, uses a lot of discretion. He is very fast at turning things around.