Building AN2Tech Stock: the internal tool we got tired of not having
We built our own inventory system because the spreadsheet had quietly become load-bearing. What an internal tool must get right that a product does not.
Every company has a spreadsheet that started as a convenience and became infrastructure. Ours tracked equipment, supplies and who had what. It worked until it did not, in the usual way: one person understood it, nobody else dared edit it, and the version in the shared folder was no longer the version that mattered.
AN2Tech Stock is what replaced it — the internal stock and inventory system we built for ourselves to track assets, manage supplies and streamline procurement across the team.
An internal tool has different rules
Building for your own team removes some problems and adds others.
You have no acquisition problem and no patience budget. Nobody has to be convinced to sign up, but they also will not tolerate friction. If logging a piece of equipment takes longer than writing it in the spreadsheet, people go back to the spreadsheet and the project is dead.
Your users will tell you immediately. The feedback loop is a person at the next desk. That is the biggest advantage internal software has, and it only works if you actually change the thing that week.
Edge cases are real, not hypothetical. We knew exactly which cases mattered because we had been working around them for months. No discovery needed — the workarounds were the requirements.
What it had to do
- Track assets, including which person currently has which thing, because that is the question that actually gets asked
- Manage supplies with a low-stock signal, so ordering happens before something runs out rather than after
- Streamline procurement, turning a request into an order into a received item without three separate conversations
- Work across the team, so the record is shared by default rather than owned by whoever set it up
The part that decides whether internal tools survive
Entry friction, and nothing else.
An inventory system is only as true as its least-motivated user. If logging something takes six fields and two dropdowns, people batch it, then forget, and within a month the data is wrong. Wrong data in an inventory system is worse than no data, because people stop trusting it and go back to asking each other.
So the entry path is short, sensible defaults are filled in, and anything the system can infer is not asked. Everything else in the product was negotiable; that was not.
Why it is worth mentioning at all
Because it is the clearest example of the thing we say on the custom platforms page: custom software is worth building when your process is the thing that makes you work, and bending it to fit someone else's product costs more than building your own.
We are not going to pretend we evaluated every inventory SaaS on the market. We needed a small number of things to work exactly the way our team already worked, we build software for a living, and the build was shorter than the evaluation would have been.
That is not the right answer for most companies most of the time, and the test on that page still applies: build when the process is a competitive advantage, buy when it is not. It was the right answer here.
Where it is
AN2Tech Stock runs at an2tech-stock.com. It is internal, it is live, and we use it every week — which is the only reason we notice the things that would otherwise sit in a backlog forever.