Inventory should be one less thing to worry about.
Kellan started with a simple observation: small-business inventory is rarely complicated because the individual items are difficult to understand.
It’s complicated because there are a lot of little things to keep track of, and the person who knows how everything works is usually already doing ten other jobs.
Cups. Lids. Milk. Coffee. Ingredients. Packaging. Cleaning supplies. Paper goods.
The things that quietly keep a business running.
The challenge isn’t understanding inventory.
It’s having enough attention left to stay ahead of it.
The idea came from both sides of the counter
Kellan grew out of our experience running Mauch Chunk Coffee Company, a specialty coffee roaster in Pennsylvania.
Running our own business means managing inventory ourselves. But working with other small businesses gave us another perspective.
Many of our wholesale customers are cafés, coffee trucks, restaurants, and other owner-operated businesses. We see firsthand how much of their day-to-day operation can live in one person’s head: what they’re running low on, where something gets ordered, how quickly it usually gets used, and what needs attention before it becomes a problem.
At Mauch Chunk Coffee Company, we built an internal system that helps predict when our wholesale customers are likely to need more coffee.
One customer operates both a café and a coffee truck. She has a great team, but—as happens in a lot of small businesses—she carries much of the operational picture herself.
Sometimes our system will tell us she’s probably due for coffee before an order arrives.
We send a quick message.
And sure enough, she’s running low.
That experience helped crystallize the problem behind Kellan.
The information needed to keep a small operation running usually exists. The owner knows it. Purchase history hints at it. Employees see pieces of it. Suppliers sometimes notice it from the other side.
But too often, no simple system brings it together.
The owner shouldn’t have to be the system
In many small businesses, the owner knows what “normal” looks like.
They know six bags of coffee is comfortable.
They know two sleeves of lids means it’s time to reorder.
They know which supplier handles the oat milk, which items disappear faster before an event, and which things can wait another week.
That knowledge is valuable.
But when too much of it exists only in one person’s head, the business becomes harder to operate, harder to delegate, and easier to catch off guard.
Kellan is built to help move some of that operational knowledge into a place the whole business can use.
Not by turning every employee into an inventory manager.
By making the important things easier to see.
Small businesses don’t always need bigger software
There are plenty of ways to manage inventory.
A spreadsheet can work.
A notebook can work.
Large inventory platforms can handle purchasing, recipe costing, accounting, forecasting, warehouse operations, POS integrations, and far more.
Those tools solve real problems for businesses that need them.
But many small operators are dealing with a much simpler set of questions:
- What do we have?
- What are we getting low on?
- How much do we like to keep around?
- What should we buy next?
- And where do we buy it?
Kellan is built around those questions.
Built from operating experience. Shaped by software engineering.
The perspective behind Kellan comes from both running a physical-goods business and building software professionally.
Operating a business makes it obvious which problems actually matter.
Software engineering makes it equally obvious how easily a simple solution can become complicated.
That tension shapes how we build Kellan.
We don’t believe every possible feature belongs in the product.
We believe every feature has to earn the additional attention it asks from the person using it.
Simple on purpose
A few principles guide Kellan.
It should take less effort than the problem it replaces.
Inventory software shouldn’t become another system you have to manage.
It should speak like an operator.
If you like to keep six on hand and you have two, Kellan should be able to tell you to add four. You shouldn’t need to translate your business into inventory terminology first.
It should fit the way you already buy things.
Your inventory already comes from suppliers. Items already have units. Things already live on the truck, in the café, at the commissary, or in storage. Kellan should reflect that reality instead of asking you to reorganize the business around the software.
It should make knowledge easier to share.
The person counting cups shouldn’t need to know everything the owner knows. A good system should make it clear what needs attention and give the team enough context to act.
It should be useful quickly.
You shouldn’t need months of historical data, a POS integration, or hours of configuration before Kellan can help.
Complexity has to earn its place.
We’ll keep improving Kellan. But we don’t measure progress by how many settings, dashboards, or buttons we can add. The goal is to make the product more capable without making the business owner think about it more.
Built to be dependable
Kellan is intentionally focused, and built for businesses that need to rely on it.
We take reliability, customer data, support, and long-term product stewardship seriously.
We also believe staying close to the people using Kellan is part of building a better product. The same kinds of businesses that inspired it continue to shape how we think about what belongs in Kellan—and what doesn’t.
We want the product to grow without losing the reason it exists in the first place.
Make inventory quieter
Small-business owners already have enough competing for their attention.
Kellan exists to make inventory easier to understand, easier to share, and easier to act on.
To get a little more of the business out of one person’s head.
To make it easier for a team to know what needs attention.
And ultimately, to make inventory one less thing the owner has to think about.