Private Beta Launch | One to One Hundred

All the apps built ot the Baseplate will first be launched to a private beta group that will have access to the features early for the purposes of providing feedback on the app and giving us an early base of users with which to launch.

The Private Beta feature allows B2B SaaS applications built on the Baseplate framework to undergo a structured and controlled private beta phase before public launch. This feature enables product teams to handpick beta participants based on role, industry, and company alignment, ensuring high-quality feedback from ideal customer profiles. By leveraging the invite framework, the system can send personalized invitations to selected users, track their engagement, and collect actionable insights to refine the application before its official release.

Users expect a workflow where they can:

Identify potential beta testers via the Organization Graph, filtering candidates based on predefined user personas and company characteristics.
- This is essentially a combined diffbot organization and person query – more information on this in the Creso.ai specification
- This functionality allows us to handpick beta participants—companies or professionals who best align with our target user personas—and grant them controlled access.
Send invitations with unique access links, granting users controlled entry into the beta environment.
Provide testers with an individualized beta portal where they can track their participation status, provide feedback, and transition to a launch edition subscription.
Collect in-app feedback as users interact with different features, enabling real-time insight into usability, functionality, and overall experience.

This approach is inspired by beta testing methodologies used in platforms such as Google Workspace (early access programs), Slack (invite-based workspace trials), and Figma (beta collaboration invites). The ability to integrate feedback loops directly into the product experience ensures that teams can iterate rapidly and launch with confidence.

From a workflow standpoint, the Private Beta Management feature enables us to:

Search the Organization Graph for people that fit the Rich User Personas in the system and work at companies that conform to the ICP for each application
Send personalized invites to those people to engage in a private beta program.
Provide each beta invitee as standalone URI for their beta program “status” including invite status, ability to provide feedback and ability to upgrade to a “launch edition” subscription
Support in-app feedback that collects user comments in the application as they are interacting with specific areas of the app

No additional analytics features would be needed for the beta period with the standard system reporting tools being used to analyze use in the period (Google Analytics and any Firebase production monitoring). We would use these tools to analyze daily active users and feature adoption rates—so we can pinpoint exactly where testers find the app most valuable and where gaps may still exist.

Once the private beta period concludes, we reward these early adopters with an exclusive, discounted launch price—an incentive managed directly within this feature. This rewards testers for their invaluable contributions and secures an initial base of customers, which is crucial to demonstrating early momentum in the market. By maintaining all elements of the beta process within a single, integrated feature, we ensure consistent, meaningful engagement with participants and produce a more polished, market-ready app that genuinely satisfies real user needs.

Role Access and User Stories

System Administrator

System Administrators manage the Private Beta settings at the system-wide level. They configure beta program parameters, oversee invite mechanisms, and ensure that beta testing aligns with security and compliance policies.

As a System Administrator, I want to configure beta program settings so that I can ensure controlled access and compliance.
As a System Administrator, I want to monitor beta invitation analytics so that I can track adoption rates.

Customer Success

Customer Success teams assist beta participants by addressing access issues, monitoring usage, and collecting qualitative feedback from users. They also track conversion rates from beta to paid subscriptions and assist in retention strategies.

As a Customer Success representative, I want to assist beta users with access issues so that they can engage with the program seamlessly.
As a Customer Success representative, I want to collect qualitative feedback from beta users so that I can relay insights to the product team.
As a Customer Success representative, I want to track conversion rates from beta to launch subscriptions so that I can optimize retention strategies.

Customer Administrator

customer Administrators control beta access within their customer. They manage the invitation process, oversee user participation, and analyze engagement metrics to ensure the beta program aligns with the needs of their specific audience.

As a customer Administrator, I want to invite specific users to a beta program so that I can get relevant feedback from my target audience.
As a customer Administrator, I want to review user feedback so that I can understand feature adoption within my organization.
As a customer Administrator, I want to manage beta participant permissions so that I can control who has access.

Manager

Managers monitor their team’s participation in beta programs, ensuring that employees provide structured feedback. They also evaluate how beta features impact workflows and whether the application meets business needs.

As a Manager, I want to track my team’s participation in beta testing so that I can ensure they provide feedback.
As a Manager, I want to evaluate how beta features impact our workflows so that I can determine business value.
As a Manager, I want to provide structured feedback on behalf of my team so that I can consolidate our insights.

Standard User

Standard Users interact with the beta program by accessing the application, testing its features, and providing feedback. They engage with in-app surveys, submit reports on usability, and decide whether to transition to the launch edition.

As a Standard User, I want to access the beta environment so that I can test new features before public release.
As a Standard User, I want to provide in-app feedback so that I can contribute to improving the product.
As a Standard User, I want to track my beta participation status so that I know when my access expires.

Pages and Screens

Beta Participant Selection

A dashboard that enables System Administrators to search the Organization Graph, filter users based on persona criteria, and select beta testers. Includes search and filter capabilities, invite actions, and participant history.

Invitation Management

A centralized panel for sending, tracking, and managing beta invitations. Displays invitation statuses (sent, accepted, declined), allows for invitation customization, and provides bulk invite functionality.

Beta Participant Portal

A personalized page for each beta participant where they can track their invitation status, provide feedback, and view options for transitioning to the launch edition subscription.

In-App Feedback Collection

An interactive feedback module embedded in the application, allowing users to submit comments and rate features directly while interacting with them. Supports contextual feedback tagging.

Beta Analytics Dashboard

A reporting interface that provides insights into beta participant activity, engagement trends, and conversion rates. Integrates with Google Analytics and Firebase for usage tracking.