Show HN: The missing link of a bookstore's tech stack (bookhead.net)
I built Bookhead because I used to work as a bookseller and I wasn't happy with the software options when I decided to sell my own collection online (with the hopes of one day growing so I can open my own brick & mortar). So I decided to make my own bookselling app...a classic hacker distraction.
Bookhead has two main parts: 1. an inventory management app that allows a bookseller to list their books anywhere they want to sell books (like Squarespace, Biblio, eBay, Shopify (coming soon!), etc) 2. an e-commerce platform with a CMS for selling books and letting a store control their online brand
I have a very exciting roadmap that I'm not ready to fully reveal, but it's all based on books. I'm building a sorta Zapier-like platform for independent booksellers. Everything is so fragmented and disconnected, which makes it hard for booksellers to do their work. I'm hoping to change that. I have a blog post that lays out my vision here: https://bookhead.net/blog/fragmented/
The current iteration is like "data engineering as a service for books." A book is a powerful thing. I'm hoping to give a bookstore everything they need to sell books online. Inventory, e-commerce, marketing, etc. It's a crowded market but I've had fun making the bookselling app that I believe should exist.
If you know any booksellers, please let them know about this! I'm onboarding my first customer right now and the biggest bottleneck is the other bookselling software providers, despite my intention to collaborate instead of compete. It's frustrating to wait for two weeks for a point of sale provider to setup an integration. It's almost like they don't care about their customers. Some providers even require ethernet cables for their software...still partying like it's 1999. Perfect for early-adopter booksellers frustrated with current tech who understand the power of automation.
I'm currently looking for funding so I can focus on this full-time. My biggest problem right now is time (aka money) because I have to sell my time to make rent etc, and can't focus on this project like I need to. I've gotten good validation from booksellers and other technically savvy folks in the industry (I've heard from two different companies that they've considered building something like this), so I believe I have something valuable. I'm not interested in funding from somebody who doesn't share my love for books or doesn't support my mission: help people use technology to promote literature. I believe that literature is one of humanity’s most prized creations, and we can use technology as a tool to keep this gift alive.
Please email me at sam@bookhead.net if you know of booksellers who might want to be an early adopter, or know of any funding opportunities that might be a good fit.
11 comments
[ 3.4 ms ] story [ 27.9 ms ] threadI know some stores that use Shopify or Adobe Commerce. When it comes to books, there are a LOT of SKUs (think IC has 2-3 million on it's built-in catalog). 5 years ago, that was a big challenge for folks wanting to sell on Shopify (which is IMO the best eCommerce platform)
- If you're _not_ using AWS, I'd explicitly mention that somewhere. I know there are a lot of indie bookstores who care about avoiding Amazon and any Amazon services. If you _are_ using AWS, well, you might find that you get more business from indie booksellers by not using it.
- I'd add an explicit list of supported POS systems in the Overview of the docs. This was one of the very first things I wanted to check. (My store's POS isn't supported, btw.)
- I'd add an explicit list of supported channels in Overview of the docs, as well. This was also one of the very first things I wanted to check.
- I'd focus on adding Square as a supported POS. From what I see in the ABA forums, this kind of thing might appeal to the bookstores using Square as a POS. Especially if you can load the book data you have into their POS, possibly based on SKU? Maybe that actually would warrant a separate product you could offer (or that someone else could make).
> I have a very exciting roadmap that I'm not ready to fully reveal
actually means:
> I've made up a list of cool / fun to build features with no user input whatsoever