Spur review

Spur is a hosted coaching-business application, not a library, CLI or self-hosted server. Coaches use it as a branded workspace for client training and nutrition plans, messaging, progress tracking, course sales and payments. Its stated aim is to bring those business workflows into one place instead of having coaches switch among separate apps.

In a typical stack, Spur sits alongside a coach’s website and business operations as the system clients use to receive plans and communicate with their coach. The homepage promotes a custom-branded app and an AI engine for workout generation and predictive analytics. That makes it a packaged service for running a coaching business, rather than a documented platform for building a separate product on top of Spur. Teams evaluating it for a software workflow should first confirm whether the vendor supports their required data exchange or integrations.

Spur’s public homepage describes a coach-client workspace, not a developer integration surface. The vendor publishes no API contract, SDKs, supported programming languages, CLI or webhook documentation on the homepage. We would not plan an integration around a REST API or event hooks without getting confirmation from Spur and reviewing its developer documentation.

The available surface described there is the branded app: coaches create plans, message clients with videos, photos or notes, track progress and sell courses. A customer testimonial mentions Garmin integration, but the homepage does not describe its scope or setup. Ask Spur which integrations are supported, whether they are one-way or bidirectional, and whether data can be accessed programmatically. Confirm SDK support and documentation with the vendor before making Spur a dependency in an application or automated workflow.

Spur is priced by client capacity, not API calls, compute or developer seats. Starter is free forever for up to two clients. Pro is billed monthly: $19 for five clients, $29 for 10, $49 for 20, $100 for 50 and $190 for 100. The pricing page lists no annual rate. Enterprise is for 100+ clients and requires contacting the vendor for a custom price.

The listed tiers make client-count costs visible, but the vendor does not publish overage charges, add-on prices or a free-trial term in the pricing details. The homepage advertises a trial that can accommodate up to 100 clients without a credit card, so confirm its duration and terms before relying on it. For a production coaching business, ask what happens when the account exceeds its chosen client tier and whether payment processing or other services carry separate charges. These prices buy the coaching application, not API usage.

Spur is presented as a branded coaching workspace accessed through its app, not as downloadable software. The vendor does not publish an open-source licence or source code availability on its public homepage. It also does not publish a self-hosting option, so teams should treat the service as hosted unless Spur confirms otherwise.

Data export and migration documentation are not published on the homepage. Before moving client records, workout histories, nutrition plans or messages into Spur, ask what can be exported, in which formats, and whether the export includes files and historical data. Migration difficulty depends on those answers and on whether the next system can import them. The branded app and client workflows can make switching more involved than replacing a standalone planning tool, so establish an exit path before onboarding a large client base.

The clearest published capacity boundary is client count: Starter covers up to two clients, Pro lists tiers through 100, and Enterprise is for 100+ clients. The homepage also advertises a trial for up to 100 clients, without a published duration in the pricing details. Ask how client limits are counted, what happens at a tier boundary and whether upgrading is immediate.

The vendor does not publish API rate limits, uptime commitments, incident procedures or service-level terms on the homepage. Security controls, data retention, backups and compliance certifications also need confirmation before storing sensitive client or health-related information. The feature list includes HRV and sleep tracking, so clarify what data is stored and who can access it. For production use, confirm export procedures, account recovery and support response expectations as well as the pricing tier.