Initial controlled beta
Beta Participation Rules
The initial cohort is intentionally small so we can observe real hotel planning use, resolve defects quickly and learn which workflows matter before access is expanded.
1. Cohort size and access
The initial controlled-beta target is about 20 participating hotels. This is an onboarding and support target, not the technical database ceiling and not an automated registration cap. We may stagger onboarding, temporarily pause invitations or registration, or expand access after reviewing reliability, support load and feedback from the first group.
Creating an account does not guarantee permanent beta availability or a future commercial plan. Beta capacity and eligibility may be adjusted as we learn from usage.
2. Pilot scope
- One principal hotel workspace is included per pilot account unless additional access is explicitly approved.
- The limited beta currently focuses on annual monthly budgeting, historical comparison, assumptions, budget analysis and review, consolidated reporting, checks and export.
- Actuals Management, Budget-vs-Actual and Forecast foundations exist in the wider platform but remain deliberately deferred for limited-beta accounts until the pilot access policy is expanded.
- Detailed professional budgeting depth, recurring monthly management-cycle automation, multi-property tenanting and daily MIS continue to develop.
- An optional AI variance-commentary path exists for supported management-package workflows when configured. It drafts commentary only, cannot alter financial tables and requires human review before acceptance.
- The beta is not a general ledger or statutory accounting system.
3. Data suitable for the beta
Use realistic hotel-level aggregated financial and operating data needed for budgeting and performance review. This can include monthly revenue, occupancy, ADR, covers, payroll totals, staffing plans, departmental expenses, historical actuals and management assumptions.
No guest names, card information, passport/identity documents, passwords, health data or unnecessary employee personal records should be placed in templates, uploads, assumptions or comments. Aggregate data before using the beta.
4. What we ask beta participants to do
- Use the product on realistic hotel planning cases rather than only clicking through screens.
- Challenge results that look commercially or financially wrong and compare important outputs with your existing planning process.
- Report errors, confusing terminology, missing hotel use cases, performance delays and workflow friction.
- Identify whether Guided/Simplified mode is sufficient and where Professional detail is genuinely needed.
- Keep exported copies of approved or important work while the software remains in beta.
- Use the account only for authorized hotel work and keep credentials secure.
Participation does not require you to publish your hotel’s confidential financial figures, give a testimonial, or allow the hotel to be publicly identified. Any public attribution should be separately agreed.
5. What participants can expect from us
- A private authenticated workspace separated from the public demonstration environment.
- Ongoing regression checks around key financial calculations, database behavior and browser workflows.
- A clear distinction between features available to limited-beta accounts, built foundations that remain deferred, and roadmap items.
- A feedback route for defects and product questions.
- Reasonable investigation of material beta failures, recognizing that uninterrupted operation cannot be guaranteed during a pilot.
6. Feedback and support
Use the application’s feedback/support channel when possible. If you cannot sign in, or your question is not about a specific workspace, email camanish.gupta@outlook.com. Useful reports include the page/module, what you were trying to do, the result you expected, the result you received, and whether the issue can be reproduced. Avoid putting passwords or prohibited personal information in a support message.
Authorized administrators may need to inspect relevant account, workspace or technical information to reproduce and resolve a reported problem. The Privacy Notice explains that access boundary.
7. Product changes during the pilot
Screens, workflow labels, performance behavior and beta limits may change. Calculation changes should continue to be subject to reconciliation and regression controls, but participants should still review material results and keep their own approved exports.
Roadmap items are product direction rather than committed release dates.
8. Leaving the beta
You can stop using the beta at any time. You may request help with account or workspace deletion through the support channel. Normal backup, security-log or recovery copies may remain for a limited period before expiry, as described in the Privacy Notice.
We may also pause or end participation for material misuse, security concerns, repeated violation of the data rules, or when the controlled pilot concludes.
9. Before you start
Explore the public demo → read the Privacy Notice and Beta Terms → create the hotel workspace → use aggregated planning data → export important approved outputs → send practical feedback.
By participating, you should also review the Privacy Notice and Beta Terms of Use.