Built around your team
Use your roles, workflow, examples, and questions instead of a generic demo.
Customer Success Programs
Explore our business growth programs, made to help you grow faster.
HoopAI Customer training
HoopAI customer trainingTrain around the work your team owns.
Choose a private learning path built around your roles, operating workflow, questions, and real HoopAI environment.
Practice, not spectatorship
Work through guided exercises and decisions with a HoopAI trainer.
Materials to keep
Leave with the agenda, exercises, notes, and an agreed follow-up path.
The job behind the service
Training becomes operational when people practice the decisions they will make after the session.
What the engagement covers
A scope people can read before they sign.
Every engagement names the work, owners, limits, timing, and handover so expectations stay visible.
- 01
Agenda and workflow intake
Defined against the agreed operating job and acceptance check.
- 02
Dedicated HoopAI trainer
Defined against the agreed operating job and acceptance check.
- 03
At least eight hours of guided practice
Defined against the agreed operating job and acceptance check.
- 04
Materials and follow-up path
Delivered with the open limits, decisions, and next owner recorded.
How the work moves
Structured enough to trust. Human enough to adapt.
The delivery path stays consistent while the details follow the system, team, and outcome in scope.
- 01
Name the operating job
Start with the result, owner, systems, and deadline instead of choosing a package by label alone.
- 02
Choose the service path
Match the job to the onboarding, migration, training, support, consulting, or web scope that owns it.
- 03
Confirm fit and limits
Review eligibility, volume, dependencies, exclusions, and the evidence needed for acceptance.
- 04
Open the bounded scope
Move into the detail page and written agreement that govern delivery for the selected service.
A human handover
The people doing the work should leave stronger.
Each principle is built into scoping, working sessions, verification, and the final handover.
HoopAI delivery principle
Clarity
The owner can explain the workflow and its boundaries.
HoopAI delivery principle
Practice
The team works through the real path before handover.
HoopAI delivery principle
Continuity
Open risks, limits, and next actions keep their owners.
“The work is finished when the operator can run it, the system can be checked, and the remaining limits have owners.”
Related HoopAI customer story
Evidence from work already in the field.
This published customer story is related to the service area. It is shown as real HoopAI evidence, not as a promise of identical results.
Read the full story AYTOZEE Solutions
Running SaaS product and consulting from one workspace
“"Customers see value faster through a single branded portal and clear success plans."”
- 228%
- MRR growth
- 41%
- Faster onboarding
- 38%
- Higher NPS
AYTOZEE combined a SaaS product with a tech-enabled agency. Trials, demos, SOWs, sprints, and tickets share the same context, so teams move faster and clients see value sooner.
Open customer storyProject pricing
Choose the private training path.
Customer and partner training each offer virtual and in-person delivery. Travel is separate for onsite sessions.
Customer Training
From €6,830
Private training around your team and HoopAI workflow.
- At least eight hours
- Up to 20 participants
- Virtual or in person
Partner Training
From €6,860
Private training around partner implementation and delivery.
- Partner delivery scenarios
- Up to 20 participants
- Virtual or in person
Prices exclude applicable taxes and third-party costs. The signed scope controls the final deliverables, timing, eligibility, and acceptance criteria.
Before kickoff
Inputs and limits stay visible.
Useful service design shows what each side brings and where a separate scope begins.
Engagement facts
- Capacity
- Up to 20 participants
- Format
- Virtual or in person
- Pricing
- From €6,830
What we need from you
- One operating job or decision to evaluate
- A named owner for the next scoping conversation
- Known systems, volume, constraints, and target timing
Outside the standard scope
- A catalog page is not a signed implementation scope
- Third-party license, media, travel, and vendor costs
- Work not listed in the selected service agreement
Questions before the scope
Clear answers before work begins.
Bring the unusual edge cases into the scoping conversation. The written agreement should carry the answer.
01What is the difference between customer and partner training?+
Customer training is built around one team operating HoopAI. Partner training uses implementation and delivery scenarios for teams that configure, explain, and hand over HoopAI for clients.
02How is the final scope confirmed?+
We confirm the outcome, systems, volume, owners, dependencies, exclusions, timeline, and acceptance checks in writing before delivery begins.
03Can the scope change after kickoff?+
Yes. We document the change, its effect on price and timing, and the revised acceptance check before adding it to the engagement.
04Does the price include third-party costs?+
No. Software subscriptions, paid media, travel, data vendors, and other third-party charges are separate unless the signed scope says otherwise.
Start with the job
Plan the next move with the scope visible.
Bring the job, systems, constraints, and deadline. We will turn them into a bounded scope with a clear path to handover.
Talk to sales
Need help choosing? We will route the job to the right service path.