11–20 of 24 posts
Almost crapped myself reading this, working on something very similar... I wonder if it will meet the same fate.
I like your observations, especially #1. May I recommend this book before you give it another shot? http://www.amazon.com/E-Myth-Revisited-Small-Businesses-Abou... Related to the pivot idea, I can's seem to find an asset manager that will work for my organization. They are either tied to business processes (e.g. selling products), don't allow custom attributes, etc. I work for a non-profit tied to govt/education and…
This is a good problem to solve. Not sure what efforts did you put in to find the target audience, we have had good results so far in building a solution for similar problem focused on IT Infrastructure. Wish you luck in your future endeavors.
This is a good problem to solve. Not sure what efforts did you put in to find the target audience, we have had good results so far in building a solution for similar problem focused on IT Infrastructure. Wish you luck in your future endeavors.
These articles are great. Sad, but great. They somehow feel more real than the "I made X in a weekend and sold it for a billion dollars" type of stories. I can relate to this story and would combine points 1 and 3. We often do it to scratch an itch or to engineer a beautiful a solution to a non-technical problem. In my last job in IT-healthcare, i learned not to rush to automate any process because the problem is pro…
I think there should be more of these stories. Many people starting companies learn much from success stories through books and blogs but I think there may be more lessons to learn about how not to fail from people that have.
(I have a couple of others linked. Perhaps I should have named them but it did not occur to me.)
Do you have a version of akumulate.com floating around. We are a small business with an asset tracking problem. Just got burned by ManageEngine's AssetTracker and would like something more in depth than SpiceWorks offers. Perhaps I can tour and buy the code base for modest amount for internal use?
We actually never modified the codebase to handle business assets. We were in the discovery phase to find out if we can repurpose the code. When we shut it down, it was still a product for managing personal assets.
My angle is focused more on locating the item than valuing it, (and I have the basics of a barcode inventory system) but I'm also wanting to add valuation (well, and 'where is the invoice') tracking to it.
I think your problem with small companies was that you went after companies that expected to be acquired.
Companies like mine that you expect to run long term are very different beasts with very different needs. And I know it doesn't seem that way in silicon valley, but there are more of us than there are "startups"
I mean, the 'where is the invoice' and the depreciation bit is important if I get audited (and I will, eventually) - but, see, I build computers and maintain networking equipment; I spend more time looking for tools/parts than I spend actually working with those tools/parts.. So a 'where is my stuff' thing is pretty dang useful.
Of course, it probably makes sense to have separate applications for inventory and for accounting value. But there are problems with that, too... for instance, it's dang difficult to come up with a solid/standard UPC database. the nature of barcode stickers is such that you probably have your own, unique numbers (which then, if you had a complete-ish upc database, you could link to) and small items? well, getting durable barcode (or rfid or NFC) tags appropriately sized for small things is usually difficult or expensive or both.
A reasonably written barcode (or rfid or nfc) based inventory thing means that other people can put things away and I can still find them; one of those things that makes living with other people (or hiring other people to help out) much easier.
The problem with asset management is that the concept makes a lot of sense, and sounds very useful, but it requires a great deal of discipline. It's basically like Quicken for businesses. Quicken makes a lot of sense, but unless everything is automated, people get bored, and once you fall 1 month behind, people usually give up. Basically, it's the human element that fails.
It's the same case with asset management. It requires someone to do the boring task of keeping track of everything. The other thing is that GAAP allows for a certain tolerance of things like valuation of assets, depreciation, etc, so you don't need to be exactly right. This gives less incentive for people to maintain a tight inventory on all their belongings.
One of my relatives owns a store, and they track inventory very loosely, because they know that their things will get shoplifted, suppliers will ship them a different amount than they requested, etc. They build in a tolerance for errors, and it's a widely accepted practice. As long as this tolerance is good enough, then having an exact count plus the amount of time required to be exact, makes the entire concept not worth it.
Almost crapped myself reading this, working on something very similar... I wonder if it will meet the same fate.
As with any consumer type app, monetization is key and unfortunately it's something I feel businesses should have a clear path to but many do not. This is part of the reason why we wanted to pivot toward a B2B type service.
Earlier quoted context omitted.
We actually never modified the codebase to handle business assets. We were in the discovery phase to find out if we can repurpose the code. When we shut it down, it was still a product for managing personal assets.
Can you give us a rundown of the codebase / language / db / size / documentation? I can likely repurpose this for my own use as well.