Onboarding
Evaluate, then adopt
Request an evaluation to explore CryspIQ®. Approved customers receive 14 days with free licence access and up to AU$500 in Azure credits. We agree the use case, data scope and success criteria before activation. Where a purchase decision needs structured evidence, we can scope a Proof of Value around agreed business outcomes, or a Proof of Concept around a specific technical requirement.
Once you decide to adopt CryspIQ®, choose guided onboarding or a coached use case, or continue self-guided. If you ask us to keep the data, relevant work completed during evaluation carries forward into delivery, and the remaining scope is agreed before onboarding begins.
What each path costs is on the pricing page.
How long it takes
Evaluate
The evaluation decision belongs here. A Proof of Value or a Proof of Concept is a separate engagement, scoped when the 14 days are not enough evidence.
| Engagement | Duration | What you decide |
|---|---|---|
| 14-day evaluation | 14 days, or until the Azure credit is used | Whether CryspIQ® is suitable. The evaluation starts when access is ready and ends after 14 days or when the AU$500 credit is used, whichever comes first. |
| Proof of Value | Scoped | Whether CryspIQ® will deliver measurable value for one use case. It ends with evidence and a purchase decision. |
| Proof of Concept | Scoped | Whether CryspIQ® will work with a specific integration, data requirement or technical constraint. |
Adopt
Onboarding starts when you commit to adoption, with a purchased licence or an agreed purchase date. The duration follows the delivery, not the trial calendar.
| Option | Recommended duration | How delivery runs |
|---|---|---|
| Self-guided | Self-paced | You work through setup from the guides and validate an initial use case. |
| Guided | Four weeks | Six sessions: two in week one, then one in weeks two and three, and two in week four. |
| Coached use case | Six weeks, planned | Six sessions and three workshops. Delivery depends on the agreed scope and data readiness. |
If a Proof of Value progresses to purchase, its business definitions, configuration and validated findings carry into onboarding. Review what remains and agree the scope before delivery starts, so you know what you are paying for at each stage.
This onboarding is for the CryspIQ® cloud service. Private cloud installations are set up differently. Contact us if you're installing CryspIQ® in your own cloud.
14-day evaluation
This is where you decide whether CryspIQ® is suitable. Request an evaluation. Approved customers receive free licence access and up to AU$500 in Azure storage and compute credits.
We will contact you within one business day. We agree your use case, data scope and success criteria before activation, and we confirm the approved credit allowance with you then. The evaluation starts when access is ready and ends after 14 days or when the credit allowance is used, whichever comes first. We notify you as you approach the limit. There are no automatic charges. You won't be charged unless you agree to continue. Additional usage or an extended evaluation requires your agreement.
You explore the product yourselves: guides, videos, a sample dataset, and group office hours. Office hours are shared Q&A. They are not a coach working through your use case.
At the end you decide whether to stop, to ask for a Proof of Value or a Proof of Concept, or to adopt. When the evaluation ends, the data you loaded is deleted unless you ask us to keep it. Tell us on the evaluation request call, before it ends, if you want a copy or if you want the data kept. After purchase, Azure storage and compute are charged separately. The detail is on the pricing page.
Proof of Value
Use this when a purchase decision needs evidence, not just a look at the product. It is our structured evaluation option. See pricing.
You agree one use case and the business measures that will show value. The engagement ends with that evidence and a purchase decision. It is scoped separately from the licence and from onboarding.
If you go on to purchase, the definitions, configuration and findings come with you. Onboarding then covers what is left, not the work you have already done.
Proof of Concept
Use this when a technical uncertainty has to be resolved: an integration, a data requirement, or a constraint. See pricing.
It is scoped to that question and ends with a result you can act on. It is not a substitute for a Proof of Value, and it is not onboarding.
We coach. Your team does the work.
CryspIQ® onboarding is not a project we deliver to you. It is coaching, and it starts once you have decided to adopt.
The roadmap is four workstreams: master data, security and access, data quality, then context and AI readiness. Each one builds on the last. Your people do the work. We show them how, and step back as they take over.
The same roadmap is used in two ways.
- Guided is structured guidance through the workstreams. Your team completes the setup.
- Coached applies that same roadmap to one business use case, on your data.
Self-guided follows the roadmap from the guides, with group office hours when you have a question. There is no one-to-one session.
The coaching roadmap
We coach. Your team does the work. Four workstreams, each building on the last. Guided teaches the concepts. Coached applies them to your use case.
Your people can sign in to CryspIQ® with their own work accounts, starting with your Company Administrator.
What success looks like, who owns the work, and which business question is in view.
One definition, one owner, one source of truth.
- A dimension has one definition and one owner
- Unknown master data waits, it is not loaded half-complete
- Stewards can map the next source themselves
New data stays hidden until a steward decides who can see it.
- Stewards define the groups
- Access is granted to those groups
- People are checked against what they should see
Problems caught as data loads, not found later in a report.
- Rules and an owner, checked as data arrives
- A Parking Lot for records that need attention
- A score people can act on
A business question in plain English, and a way to check the answer.
- Definitions, relationships and classification in the model
- A question asked in plain English
- The answer checked against the data
The work is accepted against what you agreed. Then you carry on, extend it, or stop.
Guided teaches this roadmap as CryspIQ® concepts. Coached applies the same roadmap to one business use case.
Before you start
Every licence starts with Connect. Onboarding itself starts when you commit, with a purchased licence or an agreed purchase date.
CryspIQ® runs in its own Microsoft Entra ID tenant. Your people sign in with their own work accounts, as invited users of that tenant, so nothing needs to be set up in your own directory.
- Your IT team confirms your organisation allows its people to accept invitations from another Microsoft Entra ID tenant. Some organisations block this by default.
- Your Company Administrator is invited, accepts, and signs in.
- Your Company Administrator invites the people who will do the work and gives them their functional roles.
The roles follow the DAMA-DMBOK data governance framework, as set out in Data Roles: an Executive Sponsor (the Data Owner), a Business Data Steward, a Technical Data Steward, and the Company Administrator.
Self-guided
You follow the four workstreams yourselves once you have decided to adopt. See pricing.
You get videos, practical guides and a sample dataset, an in-app checklist, and scheduled group sessions and office hours. Office hours are shared Q&A. They are not a coach working through your use case.
You are finished when the checklist is done and you have validated a first use case on your own.
Guided
Recommended for Pro, and optional. It is also included with Enterprise. Six one-hour sessions on Microsoft Teams, starting once you commit to adoption. See pricing.
The sessions are structured guidance through the coaching roadmap. Your team completes the setup. You also get everything in Self-guided, plus session notes. Between sessions your team practises on the guides and the sample dataset.
- Connect and kick-off. Who signs in, who owns the work, and what success looks like.
- Master Data. One definition, one owner, one source of truth. A business key, so unknown master data waits instead of loading half-complete.
- Security & Access. New data stays hidden until a steward grants it. Groups, access, and a check that people see what they should.
- Data Quality. Rules and an owner as data loads. The Parking Lot for what needs attention, and a score people can act on.
- Context & AI Readiness. Definitions and relationships in the model, a question in plain English, and how you check the answer.
- Accept and decide. What done looks like, and how the team carries on without a coach in the room.
Coached
The same six one-hour sessions, and the same four workstreams, applied to one business use case on your data, plus three two-hour specialist workshops. Planned six-week delivery, subject to agreed scope and data readiness. Preparation and review sit around the live time. It starts once you commit to adoption. See pricing.
Before the first session you agree the question, the dimensions, the sources, the people and the acceptance criteria. Bring one question you would act on, a source or two, and the lists you already keep. Name your Data Stewards and Data Administrators. If one person needs to keep that moving, that is the Workstream Lead.
The six sessions follow the roadmap, on that use case:
- Kick-off. Your question, the dimensions in scope, the stewards, and the acceptance criteria.
- Master Data. Your definitions, owners and sources of truth. Your stewards map the source.
- Security & Access. The groups your stewards define for this data, and a check that people see what they should.
- Data Quality. Rules and owners for this data, and a score your owners act on.
- Context & AI Readiness. The question from kick-off, answered on your data, and checked.
- Accept and decide. Accepted against the criteria from kick-off. Then you run it yourselves, extend it, or stop.
The three workshops are where that use case is worked through in the room:
- Use-case design, business context and master data.
- Data quality, stewardship and access.
- Output validation, operational readiness and handover.
Further sources, use cases or custom development are scoped separately.
You are finished when the agreed data is flowing, context and access are configured, the outputs meet the acceptance criteria, and your team has a handover. Because your stewards did the work, they can add the next source, rule, question or user without us.