Current Direction
Free service tracking
for commercial locations.
TradeBoost is moving away from the old retainer story. The new direction is a free app that helps locations track service requests, equipment history, PM context, invoices, and vendor records in one place.
The app is useful on its own. Vendor matching is optional. When TradeBoost helps route real work, the vendor still bills the customer directly.
One place for the stuff
that usually lives in chaos.
Service Requests
Track what was requested, when it happened, and what still needs follow-up.
Equipment History
Keep a memory of units, repairs, recurring issues, and replacement context by location.
Vendor Records
Store who worked on what, what they charged, and what proof or notes came back after the visit.
PM Visibility
See what is due soon, what got skipped, and where preventable maintenance risk is stacking up.
Set up locations
Add one site or many. Invite the people who actually handle service.
Track requests
Log service requests and tie them to the right location, unit, or issue.
Build history
Keep invoices, vendor notes, photos, and service history attached to the place they matter.
Route work when needed
If a customer wants help finding a vendor, TradeBoost can help match the job without becoming the contractor.
Built for real-world ops.
Good fit
- Commercial locations with recurring service needs
- Groups with one site or many sites
- Teams tired of service info living in texts and memory
- Operators who want clearer equipment and vendor history
Not the point
- Another expensive software contract
- A promise that TradeBoost does licensed trade work
- A vendor portal requirement for day one
- A giant enterprise facilities platform in v1
Is the app free?
That is the current direction. The working model is free for the location, with TradeBoost making money when matched vendor work happens.
Do vendors bill through TradeBoost?
No. The current rule is that vendors still quote and bill the customer directly.
Is this just old AI consulting with new words?
No. The repo was cleaned to remove that old story. The current direction is a useful operating layer first, not an AI retainer pitch.
What gets better over time?
The service history, equipment memory, PM context, and vendor record at each location. The longer a customer uses it, the more helpful it should become.
Want early access?
Tell us what kind of locations you run, what is messy today, and what the first version should help with.
Join Early Access