Ninefold Scout
For programs focused on JUCO discovery, evaluation, and board organization.
Scoped proposal
- Scout pilot access
- Covered player and team data
- Discovery, filters, and comparisons
- Defined board workflow
- Onboarding and support scope
Software pricing
A defined scope before a number.
Ninefold uses guided pricing because the product, number of users, data work, implementation, and support differ by program. Buyers receive a clear scope before they are asked to evaluate a proposal.
Program Hub
For programs prioritizing development, analytics, reporting, or recurring operations.
Scoped proposal
- Defined program workflow
- Configured workspace
- Agreed data inputs
- Coach-ready outputs
- Implementation and review cadence
Ninefold Complete
For programs building toward a connected prospect-to-roster player lifecycle.
Scoped proposal
- Scout and Program Hub scope
- Shared lifecycle planning
- Organization and access roadmap
- Phased implementation
- Connected data model requirements
Founding Program
For selected programs willing to evaluate a focused pilot and provide structured feedback.
Scoped proposal
- Defined pilot question
- Direct product feedback
- Transparent limitations
- Agreed responsibilities
- Written pilot and commercial terms
Software proposals should state product access, users, data, implementation, support, term, payment, renewal, cancellation, and each party’s responsibilities.
What determines price
The product is only one part of the scope.
A professional proposal should state what is included, what requires configuration, and what the program is responsible for providing.
Product access
Scout, Program Hub, Complete, or a defined Founding Program pilot.
Users and roles
Number of coaches, analysts, administrators, and program workspaces.
Data scope
Coverage, imports, file formats, historical records, cleaning, matching, and validation.
Implementation and support
Onboarding, configuration, training, feedback cadence, custom reporting, and ongoing support.
Commercial process
From first conversation to pilot proposal.
Ninefold does not use a self-service checkout for college programs. The sales process is designed to prevent both sides from agreeing to an unclear implementation.
01
Discover
Identify the workflow, users, current tools, data, decision, and source of friction.
02
Scope
Define the product, pilot boundary, responsibilities, timeline, support, and success criteria.
03
Configure
Prepare the workspace, data, permissions, views, reports, and training needed for the evaluation.
04
Evaluate
Review reliability, usefulness, adoption, time saved, limitations, and next-stage requirements.
A good pilot can end with “not yet.”The purpose is to produce an honest decision about product fit, data readiness, implementation effort, and next steps.
Pricing FAQ
What buyers can expect.
Not yet. Ninefold is validating product scope, onboarding effort, support requirements, and pilot terms before standardizing public pricing.
Pilot terms depend on the scope, product maturity, implementation work, and feedback commitment. Any cost or discount should be stated in writing.
Yes. Scout, Program Hub, and Complete are separate starting points. The best option depends on the workflow the program wants to improve first.
Product access, users, data, implementation, training, support, term, payment, renewal, cancellation, responsibilities, and success criteria.
Next step
Get a scope your program can actually evaluate.
Start with a short conversation about users, data, workflow, timing, and the decision you want Ninefold to improve.