Calee Enterprise
Connect complex organisations, systems and audiences around the dates that matter.
Calee Enterprise is for organisations whose coordination requirements go beyond a standard platform rollout. We work with your operating model, existing systems, sites and audiences to define a Calee solution under a project-specific agreement.
How an Enterprise engagement is shaped
-
Enterprise environment
Sites · systems · teams · audiences
Where the dates and information your organisation runs on already sit, and who maintains them today.
-
Project definition
Scope · integration · access · governance
What has to be agreed before anything is built, connected or rolled out.
-
Calee solution
Agreed capabilities · deployment · support
Delivered and supported under the terms set out in the project agreement.
How Enterprise is decided
Enterprise is defined by the requirement, not the organisation’s headcount.
The enterprise problem
Complex organisations rarely have one calendar, one system or one audience.
In a complex or distributed organisation, the dates that matter are usually correct somewhere already. The difficulty is that they are spread across groups, systems and audiences that were never designed to line up with each other.
Multiple sites and operating groups
Different sites, divisions, teams, programs or operational units may own different schedules, and each may be maintained by different people to a different rhythm.
Multiple systems and information sources
Dates may originate in different calendar sources, systems, documents or established processes, each of which has its own reason to exist and its own owner.
Different audiences
Different information may apply to staff, teams, customers, members, residents, participants, contractors, families or other external audiences — and rarely the same information to all of them.
Different access requirements
Different audiences may need access to different calendars or information, and which audience sees which calendar is a decision the organisation makes rather than a default.
Distributed consumption
Information may need to appear in more than one place depending on the project: in Calee, on the web, in a compatible calendar app, and on optional shared Calee Displays.
Not every organisation has all of these, and having several of them does not automatically mean an Enterprise project. It usually means the requirement is worth scoping properly before anything is chosen.
How Calee fits
How Calee Enterprise fits an operating environment
An Enterprise project starts from where your information already sits, not from a product tour. The model below is how a Calee Enterprise solution is put together. What each stage actually contains is defined by the project rather than assumed here.
-
Your enterprise
- Sites
- Teams
- Programs
- Systems
- Calendar sources
Where the dates and information that matter originate today, and who currently maintains each of them.
-
Calee Enterprise
- Structure
- Project-defined integrations
- Access
- Calendar workflows
- Distribution
How your organisation is represented, which sources are connected where that is agreed and technically appropriate, who can see what, and how calendars are maintained and published.
-
The right audiences
- Internal
- External
- Site-specific
- Program-specific
Each audience receives the calendars and information the project determines apply to it, and not the rest.
-
Where information is used
- Calee
- Web
- Compatible calendar apps
- Optional shared Calee Displays
The endpoints Calee supports. Which of them a particular project uses is part of its scope.
Integrations are project-specific. Calee does not connect to every system, and what can be connected in a given environment is confirmed during scoping rather than assumed on this page.
What a project defines
What a Calee Enterprise project defines
An Enterprise project is shaped around your requirements, so the areas below are the ones a project can define rather than a list of things every solution includes.
Organisation & access
How the organisation is represented in Calee, how its calendars are run, and who can see what.
-
Organisation structure
How sites, units, teams and audiences may be represented in the agreed Calee solution.
-
Calendar workflows
How the relevant calendars are created, maintained and distributed across the organisation and its audiences.
-
Identity and access
How people are identified, and which information or calendars they can access, where that is defined by the project.
Integration & deployment
How Calee meets the systems you already run, and how the solution reaches your sites and people.
-
Integrations
How the project may connect Calee with agreed systems and calendar sources. Integrations are project-specific and confirmed during scoping.
-
Deployment
How the solution may be rolled out across sites, cohorts or phases rather than everywhere at once.
-
Calee Displays
Optional shared endpoints, for locations where a persistent physical view of a calendar is useful. They are never required.
Governance & project services
How the engagement is owned, reviewed and supported once it is running.
-
Governance
Ownership, responsibilities and the project review arrangements agreed for the engagement.
-
Support
The support arrangements agreed for the project, backed by our Australian team.
-
AI capability
Any AI capability is defined by the project contract. It is not an automatic Enterprise inclusion.
These areas are contract-defined rather than standard inclusions. What a particular Calee Enterprise solution includes is what its project agreement specifies — which is also why we would rather scope your requirement than sell you a list.
Which one applies
Calee Business or Calee Enterprise?
Both are part of the Calee platform. The difference is whether the requirement can be met by scoping the standard Calee organisational platform, or whether parts of it need to be defined and delivered as a project.
Calee Business
Use Calee Business when the standard Calee organisational platform can meet the requirement through an agreed scope covering the organisation’s calendars, users, audiences, locations, optional Displays and services.
- The standard platform, scoped to your organisation
- Users, teams, sites, programs, calendars and audiences
- Optional Calee Displays, onboarding and services
- Being a large organisation does not by itself make it Enterprise
Calee Enterprise
Use Calee Enterprise when the requirement needs a project-specific solution — for example where systems, integrations, access, deployment, governance or other capabilities need to be defined under a project agreement.
- Requirements that go beyond a standard platform rollout
- Bespoke project work, defined and agreed before it is built
- Project-defined integrations with agreed systems and sources
- Deployment, governance and support set out in the agreement
- Commercial terms agreed as part of scoping the project
Calee for Education and Calee for Sports Clubs are packaged solutions built on Calee Business, for schools and sporting clubs. If you are one of those, start with Calee for Education or Calee for Sports Clubs.
If you are not sure which applies, that is a normal place to start a conversation, and it is what the first step of an engagement is for.
Engagement
How a Calee Enterprise engagement works
An engagement moves from understanding the requirement to an agreement that says what will be delivered, how it will be deployed, and how it will be supported.
-
Understand
Understand what the organisation needs to achieve, where the relevant dates and information originate today, and who needs access to them.
-
Scope
Define which capabilities and project work are required, and which parts of the requirement the standard platform already covers.
-
Agree
Document the agreed scope, capabilities, deployment, governance, support and commercial terms in the project agreement.
-
Deliver
Implement the agreed Calee solution, across the sites, cohorts or phases the agreement sets out.
-
Support
Support the solution under the arrangements agreed for the project, backed by our Australian team.
We do not publish fixed discovery, implementation or delivery timeframes. The schedule for a project is part of what is agreed with you, because it depends on the scope, the sites involved and your own operating calendar.
Trust, governance & procurement
What procurement will want to know
Calee is built and supported in Australia by My Calee Pty Ltd, ABN 25 674 810 916.
Who you are contracting with
- My Calee Pty Ltd
- ABN 25 674 810 916
- 100% Australian Owned & Operated
- Local Australian support
Organisational control
- Your organisation remains the source of truth for its own dates
- Your organisation determines what it publishes and who it is shared with
- Project requirements are agreed with you rather than assumed
What a project agreement can define
- Scope
- Responsibilities
- Governance
- Deployment
- Support
- Commercial terms
Where your procurement process has requirements we have not set out here, raise them during scoping. We would rather tell you plainly what we can and cannot commit to than publish a claim we cannot stand behind.
Policies & support
Commercial model
Commercial terms by agreement
Calee Enterprise does not use a published standard price list. Each engagement is scoped as a project, and the applicable capabilities, delivery, support and commercial terms are defined in the project agreement.
That is deliberate rather than evasive. Two Enterprise projects can differ in the systems involved, the sites in scope, the audiences served and the governance required, so a published figure would be wrong for almost everyone it reached.
What the agreement settles
- The capabilities included in the solution
- The project work required to deliver them
- Deployment across sites, cohorts or phases
- Governance and responsibilities
- Support arrangements
- Commercial terms
Standard organisational requirements are handled by Calee Business, which is also scoped rather than sold as one fixed plan.
Talk to us about your requirements
Tell us what your organisation is trying to achieve, where the relevant dates or information live today, and who needs access. We can then determine whether Calee Business or an Enterprise project is the right fit.
Discuss your requirements
Tell us what you are trying to achieve and we will come back to you about whether Calee Business or an Enterprise project fits, and what the next step would look like. Or email info@calee.com.au.
Enterprise questions
What is the difference between Calee Business and Calee Enterprise?
Calee Business is the standard Calee organisational platform, scoped to your requirements across users, teams, sites, programs, calendars, audiences, optional Displays, onboarding and services.
Calee Enterprise is for project-specific requirements that need contract-defined capability, integration, deployment, governance or other project work.
Is Enterprise only for very large organisations?
No. The distinction is the requirement, not simply organisation size. A large organisation can run on Calee Business, and a smaller one with project-specific integration, access or governance requirements may be better served by an Enterprise project.
Can Calee Enterprise integrate with our systems?
Integrations may form part of a project where they are agreed and technically appropriate. We do not promise compatibility with a particular system before scoping it, so tell us which systems and calendar sources are involved and we will tell you what is possible.
How is Calee Enterprise priced?
There is no standard published price. Commercial terms are agreed as part of scoping the project, alongside the capabilities, delivery, deployment and support it covers.
Does Enterprise require Calee Displays?
No. Calee Displays may form part of a project where shared physical visibility is useful in a location, but they are optional and Enterprise does not depend on them.
Can an Enterprise solution include AI?
AI capability may be included where it is explicitly defined by the project contract. It is not an automatic Enterprise inclusion.
What does an Enterprise agreement define?
Depending on the project, the agreement may define the scope, the capabilities included, deployment, governance, support and commercial terms.