If a product on the market solved it, you would have bought it.
BearLog builds new products and internal systems, takes over software somebody else started, and keeps what is already live working. Four shapes of problem, one starting point: yours, never a package.
- 01
Custom software development
You need a product, platform, or system that does not exist yet.
From a business problem to software people rely on. We start with the smallest version that is genuinely useful, put it in front of the people who have to live with it, and let what they do decide what comes next.
Queue went from nothing to a working line, on real phones, with staff calling numbers from a browser.
- 02
Internal tools and workflow systems
A spreadsheet, a paper process, or six tools that do not talk to each other.
Replace the workarounds with software built around the actual job. The people doing that job help shape it, which is the whole difference between a system that gets used and one that gets worked around.
Heimdal replaced a paper sign-in book with a kiosk that nobody has to be trained to use.
- 03
Takeover and rescue
Your existing software needs a dependable owner.
For code that is unfinished, unstable, or abandoned by whoever wrote it. We read it before promising anything, then repair what is fragile while the business keeps running on it.
The same reading discipline both products get: nothing is rewritten before it is understood.
- 04
Ongoing support and improvement
It is live, and it has to stay useful.
Launch is the start of the work, not the end of it. Keep it reliable, respond to what people actually do with it, and pick the next improvement from evidence rather than opinion. It is how we run our own products.
Queue and Heimdal are both still maintained by the person who wrote them.
Built for real operating conditions
Queue and Heimdal are production products, not portfolio concepts. Building them has meant solving the same difficult problems that show up in commissioned software: reliability, shared state, offline work, and simple experiences for people who have a job to do.
- State that has to agree across several screens at once, when any of them may have been asleep for an hour.
- Capture that continues through a dropped connection and reconciles cleanly when it returns.
- A way in with no account, no install and no password to forget.
- Screens nobody logs into, running unattended on a wall or a door all day.
- What a screen is allowed to show when it can no longer reach anything.
- Keeping only the data the job needs, and forgetting the rest on a schedule.
What would better software make easier?
Name the process that is costing your team the most time. That is enough to start a useful conversation.