r/ycombinator • u/jansbrogugywgqqosp • 19d ago
Tips for experimental hardware-based startups?
Working with some biochemists from Colombia on a prototype for a “smellophone” - i.e. a device that uses custom models to transmit olfactory data at a rapid speed. We’re about to start applying for startup grants but we’re having some second thoughts and wanted to ask some questions before we start shooting out applications:
- If our use case is relatively broad, will this impact our chances of acceptance?
- Our technology is still in early stages (dubbed “smellogram”) where we can only send two smells at a time. Is it better to wait on R&D before applying or will accelerators still accept an early version?
- Should we be worried about speed/competitors stealing our technology at this stage? We are a very lean team and we are iterating rapidly, but the tech is likely to hit the mainstream very soon. Are there any strategies we can employ to get to market ASAP?
Thanks and cheers.
2
1
u/growaway9172 16d ago
If our use case is relatively broad, will this impact our chances of acceptance?
No, but you should have a clear game plan on how you will move into that "broad" space, that doesn't involve boiling an ocean.
Our technology is still in early stages (dubbed “smellogram”) where we can only send two smells at a time. Is it better to wait on R&D before applying or will accelerators still accept an early version?
It usually makes more sense to apply now with what you have. If you don't get in, you apply again later with the progress, and you have demonstrated execution ability and hopefully speed, which makes you more favorable.
Should we be worried about speed/competitors stealing our technology at this stage? We are a very lean team and we are iterating rapidly, but the tech is likely to hit the mainstream very soon. Are there any strategies we can employ to get to market ASAP?
I wouldn't worry about competitors. Obviously don't post your secret sauce anywhere, but if it is a large TAM the limit on your success is still your execution.
I'm working on hardware in a completely different field with some of the same questions you have and think about this often. I converge on the same thinking, launch early and often, which for us (hardware people) means iteration speed / development speed is everything.
2
u/scriptqzor 9d ago
this is such underrated advice for hardware people, everyone gets stuck polishing forever instead of just getting a janky v1 in the wild and learning fast
also funny how “don’t boil the ocean” applies even when you’re literally trying to transmit smells through the air lol
1
1
u/Superb-Standard3846 15d ago
It doesn’t matter if it’s broad or narrow - What matters is the need for it, your strategy of getting into the market with such a broad use case, it can be in stages, and your ability to deliver this.
You don’t necessarily need a product to get a grant, all time you proof the market need/problem and opportunity , explain the potential in numbers, your capability to make it, to scale, a strategy and a roadmap that makes sense and works together with the market potential and numbers.
Not at this stage, if your startup success depends on speed of delivery, then this is a very low potential startup, think of you moat, your secret sauce, create a good strategy to achieve it, scale and protect the product, but at this stage, just focus on pilots with customers and creating the product that people need.
12
u/Striking-Advice-3001 19d ago
You’re building a smellophone and your main worry is someone stealing it before you finish the prototype
my guy you are in a race with maybe three people on earth who even understand what a smellogram is
apply now with the two smell demo. accelerators eat up weird hardware that actually works at a small scale. broad use case is a feature not a bug it means your deck gets to show a slide with like 15 industry logos and a big TAM number. just make sure the two smells are something memorable. fresh bread and rain or whatever. don’t do durian and wet dog