Why this exists

I am Ryan. I built Quiver because my own bikes lived in a spreadsheet I had stopped trusting. Every bike had a tab, every tab had a column I had given up maintaining, and the answer to "what fork is on the trail bike, and what did it cost" was somewhere between that file, a folder of receipts, and my memory.

That is a silly problem to have and a surprisingly annoying one to fix. Typing a full build sheet by hand is a chore nobody finishes. So Quiver starts from the other end: you name the bike, and it goes and finds the factory build, part by part, with the source recorded for each spec.

Who I am

I spent about fifteen years designing products at big tech companies, as an individual contributor and then a manager. I ride road and dirt around the Bay Area, and I have more bikes than I can defend at dinner. I am the person this app is for, which is the only reason I trust my own judgment about it.

The one principle

If we are not sure, we say so. Quiver records where every spec came from and marks anything unconfirmed instead of presenting a guess as fact. A missing value costs you a minute. A confident wrong answer can cost you money, or a part that does not fit.

Quiver is young. The standard is not. The catalog grows every day, and a bike that is missing goes straight onto the research list.

How small this is

There is no team behind Quiver. It is me, and the catalog engine that keeps researching bikes whether or not I am awake.

Talk to me

Email [email protected] and a real person reads it, because there is only one. Missing bike, wrong spec, a feature you want, all of it is useful, and the missing-bike reports go into the research queue directly.

Quiver is on Instagram as @ride_quiver and on Reddit as u/ridequiver.