A shared understanding
An agreed metric, baseline and criteria the team will use to make a decision.
AIStart360 Growth Labs · International business Bootcamps
A practical starting point for the GRI × GTM growth system: choose one growth lever, launch a first AI experiment and inform the next step.
We are gathering interest in future programmes. Dates and terms for each cohort will be agreed separately.
GRI → GTM → experiment
Continue · change · stopBring an existing workflow that can be understood and tested on a limited scale.
Bootcamp / start your growth cycle
Choose the main constraint, establish a baseline and connect GRI findings to a GTM plan. Over 21 days, complete a focused test cycle for one use case.
Test how to reduce losses between an enquiry and a purchase.
Example metric · Paid conversionChoose this leverFind a relevant reason for a customer to return.
Example metric · Repeat purchase rateChoose this leverTest the value of a bundle or a follow-up offer.
Example metric · Gross profit per customerChoose this leverTest one partner sales use case and its economics.
Example metric · Contribution profitChoose this leverTest when customers are willing to refer and what value it creates.
Example metric · Referral purchasesChoose this leverFind a delay in cash movement and test one change.
Example metric · Cash recovery timeChoose this leverThese are test directions, not growth promises. Agree one primary metric, costs and decision criteria for the chosen challenge.
Working programme / 03 weeks
Discuss the challenge, available examples, team involvement and scope. Agree the work before the programme begins.
Week 01
Establish the baseline, identify a constraint using GRI findings, and choose one lever, GTM action and set of test rules.
Week 02
Test a focused solution on agreed examples. Record errors and the human role.
Week 03
Compare observations with the baseline: continue, change, stop or collect more data.
21 days is a focused test. A broader business pilot of around 90 days and subsequent implementation are discussed separately.
How a business pilot worksAn agreed metric, baseline and criteria the team will use to make a decision.
A comparison protocol, observations and limitations. A prototype only within the scope agreed in advance.
A decision and action plan. A 90-day plan, if required, does not include 90 days of implementation.
Demonstration sample
A working document structure, not the result of a completed Bootcamp.
Experiments / from hypothesis to test
Explore where AI changes customer behaviour, team effectiveness and business economics. In the Bootcamp, define a question, choose a metric and test one use case: scale, change or stop.
Proposed hypothesis
Example metricPaid purchase rate among test participants.
Proposed hypothesis
Example metricRepeat paid purchase rate within the agreed window.
Proposed hypothesis
Example metricShare of itineraries accepted after critical-condition checks.
These are research hypotheses from the existing catalogue. HONOR is a client case; 1 MLN KM is our own laboratory. Selecting a hypothesis does not grant access to project data or confirm a Bootcamp launch.
All hypotheses and experimentsInternational network / 06 locations
We are developing opportunities to work together across six locations. These are options for future programmes, not a required route through every country.
GRI × GTM × experiment
GRI findings help identify a constraint. GTM connects the action to the market and customer. An experiment tests whether there is a basis to move forward.
GRI is an author-developed analytical framework, not independent certification, an investment rating or a growth guarantee.
Explore the methodologyPractice beyond the Bootcamp
Connecting retail, digital services, CRM and inventory. Business metrics are not proof of a causal AI effect.
Research into digital travel use cases. A research project, not a verified participant outcome.
These projects show the context of the team’s work. They are not presented as Bootcamp graduates.
Programme organisation
Connects the business challenge, GRI findings, GTM planning and solution testing. The team and expert involvement are agreed around the needs of each cohort.
About the organiserFor local partners
Discuss contributions, responsibilities and terms. These are possible roles, not a list of confirmed partners.
Local organisation → discuss coordination and responsibilities.
Workspace → discuss facilities and the programme format.
Audience connections → discuss suitable challenges and company selection.
Challenges and a team → discuss test scope and employee involvement.
Tools and expertise → discuss suitability, data and quality control.
Check whether the challenge fits, and discuss examples and team involvement. Then agree location, language, format, scope, fees and participation terms.
A focused test of one use case within an agreed scope. Full implementation and a broader pilot of around 90 days are separate engagements.
A general description is enough for the first conversation. Access to working data, de-identification, material rights and external services are agreed before testing.
Attendance, working language, schedule and team involvement depend on the cohort. These are confirmed before participation is agreed.
The scope of logistical services has not been approved. Travel, accommodation and visa support are not included without separate confirmation.
The programme helps inform a next step. Investment, contracts and market entry are not guaranteed; the investment route is considered separately.
Record observations and limitations. A well-supported decision to change or stop an unviable use case can also be valuable.
Start a conversation
A short description, without a lengthy application. Review the message first, then send it yourself in WhatsApp.