Internal Stabilization
Approximately two weeks. No outside testers. Obvious defects and trust-critical failures are addressed first.
Beta program
Structured testing. Measurable results.
The beta exists to determine whether NPS is trustworthy, understandable, useful, and recoverable under real working conditions.
Core promise
Beta-ready does not mean feature-complete.
The external beta begins only when the core promise works consistently: stable records, accurate calculations, reliable income and expense tracking, stable route tracking, working backups, basic reporting, and clear privacy messaging.
Program phases
A controlled 60–90 day process.
Guided Beta
Approximately four to six weeks. Testers receive assigned missions with overlapping coverage on critical workflows.
Sandbox
Approximately two to four weeks. Testers explore freely, attempt unexpected workflows, and try to break assumptions.
Release Candidate
A short validation period confirms fixes, migration safety, backup recovery, and readiness for public release.
Tester responsibilities
Useful participation requires more than installation.
- Complete the assigned primary mission.
- Use the application during normal work where practical.
- Submit reproducible steps, expected behavior, and actual behavior.
- Report data loss, incorrect calculations, backup failures, privacy concerns, or route failures immediately.
- Avoid submitting confidential employer, customer, financial, or identity information.
Participant recognition
Meaningful participation may be rewarded.
Qualifying testers who participate through the completion of the beta may receive 6–12 months of NPS Pro after official launch and possible Founding Beta Tester recognition.
Final eligibility and benefit duration will be defined before enrollment. Merely joining the waitlist does not establish eligibility.
Apply for Early Access