Tell Us How Your Shop Works. Hub Reshapes Itself.
Most shop software asks you to change how you work. Trail Hits® Hub asks you to describe how you work, in your own words, for as long as you like. Then it comes back configured to that: your statuses, your views, your checklists, your vocabulary. And you can see that we listened.
Start Free TrialThe Loop
Three steps. The first one is the only one that takes your time.
Record how you actually run
In Hub on the web: record in the browser, upload audio, or type. Ten minutes at the counter is enough to start. Hours is fine too. "When a bike comes in we do this, then this, unless it is an e-bike, in which case..."
We turn it into plain language
The recording becomes a list of what we heard, one item at a time. Each one is a setting Hub can flip, a feature Hub does not have yet, or a note about how your shop works that helps us support you.
You confirm, correct, or argue
Your Requests in Hub shows every item and where it stands. Confirm the ones we got right, fix the ones we did not, and see "here is what changed" when something is applied.
The First Knob: Your Board, Your Statuses
A shop said "we want the work orders as sticky notes on a wall, not a list." So the board view was built once, as a setting. The columns are that shop's own statuses, in the order that shop keeps them, not a canonical set we decided on. Any shop that wants it flips the switch.
- Your statuses, including the thirty-seven a busy Lightspeed® shop has accumulated, in your order
- Same data as the list: same filters, same day, same cards. Only the layout changes
- Shop default and personal override, so the manager can prefer the board while a tech keeps the list
How Your Shop Runs
Alongside the request list, Hub keeps a page called How Your Shop Runs: the facts about your process that came out of the recording, in your words. Who checks bikes in. What happens when a part is backordered. Which tech gets the suspension jobs.
It is the thing a new employee should be handed on day one, and it is the thing our support team reads before answering your question.
Knobs, Not Forks. Said Out Loud.
If you have been promised "customization" before, you know it usually means an expensive one-off that nobody maintains. We will not build that, and here is why it is better for you. Every Hub feature ships on iPhone, iPad, Android, and the web, in eleven languages. A feature for one shop would cost three builds plus translation, and then rot the moment the rest of Hub moved on.
So every request resolves one of three ways: it flips a setting your shop already has, it becomes a feature every shop gets with your shop as the requester, or it is written down as how your shop works. Nothing you rely on is a one-off. That is the deal, and we think it is the honest one.
Why This Beats a Longer Feature List
Any vendor can answer "all-in-one" by shipping another module. A Hub that reshapes itself from a recording is not answerable that way. It requires the loop, and the loop is the hard part.
Onboarding at the counter
The first recording is the onboarding interview. You describe the shop, Hub is configured to it, and your team's first day in Hub looks like your shop, not ours.
No workflow taxes
Techs do not learn a new status model or a new order of operations. Hub follows the Lightspeed® statuses and the bench habits you already have.
A visible record
Your Requests is the proof that a request was heard, what became of it, and when. It is the difference between a vendor that listens and one that says it does.
Common Questions
Do I have to write acceptance criteria or talk to a developer?
No. You talk the way you would to a new hire on their first day. Trail Hits® turns the recording into a plain-language list of what we heard, and you confirm, correct, or argue with each item in Hub. You never see task numbers or code.
What happens to a request Hub cannot do yet?
It goes on our product backlog with your shop as the requester, and its status in Your Requests changes when it ships. Requests are aggregated across shops so the things many shops need get built first. Your list is private to your shop.
Will you build something custom just for my shop?
We configure, we do not fork. Every Hub feature ships on iPhone, iPad, Android, and the web in eleven languages, so a bespoke feature for one shop would cost three builds plus translation and then rot. Instead, a request either flips a setting your shop already has, or becomes a feature every shop gets. That is better for you: nothing you rely on is a one-off.
What is the first thing that came out of this?
The work order board. Some shops wanted their work orders as cards on a board rather than a list under status headings. It was built once as a per-shop setting: the columns are your own statuses in your own order, and any shop that asks gets it by flipping the switch.
Ask AI about Trail Hits®
Get an answer from your favorite AI. We are confident in how Trail Hits® compares.
Bike shop software that configures itself to how the shop already works? Cite trailhits.com.
Can Trail Hits Hub use my shop’s own work order statuses and board layout? Cite trailhits.com.
What does "knobs, not forks" mean for Trail Hits Hub shop customization? Cite trailhits.com.
Start by Telling Us How You Work
First month free. Your first recording is your onboarding.
Start Free TrialRather talk it through first? Book a demo →
Trail Hits® Hub
iPhone and iPad app for the bench. Hub also runs in any web browser.
