AIStart360 / growth lever / 06
Predictable receipts. Clear commitments.
Design a cash-flow stabilisation system using advance payments, prepaid customer balances, subscriptions, partnerships and agent sales. Choose a suitable model and connect terms, payment, fulfilment and cash controls in one workflow.
These are test directions, not growth promises. Agree one primary metric, costs and decision criteria for the chosen challenge.
06 / Cash-flow stabilisation
Choose a model that fits your economics and customer behaviour. Start with one segment and one change, then connect working mechanisms into one system.
Agree what the customer pays before work begins and receives at each stage. Connect the receipt to procurement, a reservation or work commencement, with clear rescheduling and refund terms.
What we track: Advance-payment share, time to payment and cost of concessionsCustomers fund a balance for future purchases or services. Track the remaining amount, each use and any refund; agree validity and reminders. Account for future delivery.
What we track: Unused balances, usage, refunds and fulfilment costPackage recurring value with a clear service scope and period. Configure invoices, authorised renewals and failed-payment handling, with a transparent cancellation process.
What we track: Actual receipts, renewals, churn and marginChoose partners with a relevant audience or complementary product. Agree the offer, responsibilities, ordering and settlement schedule. Keep promised volume separate from paid orders.
What we track: Paid orders, settlement timing and concentrationRecord deal attribution, the commission basis and when it becomes due. In the pilot, test settlement after confirmed customer payment, adjusted for refunds; agree terms and authority in advance.
What we track: Cash after commission, refunds and payout timingCombine the models in a rolling 13-week plan: forecast and actual receipts, fulfilment, refunds, commissions and committed outflows. Reconcile weekly and refresh assumptions.
What we track: Minimum balance, cash shortfalls and forecast deviationsThe first 21 days cover a focused test of one model. Assess renewals, seasonality and receipt stability over a longer period. Faster payment does not equal higher profit.
Design a cash receipts systemAI must not invent prices or terms, send important messages without agreed oversight, change agreements or execute payments.
Invoices paid in full on time / all initial-cohort invoices that have fallen due. Report overdue balances, unconfirmed promises and partial payments separately.
Compare forecast and actual receipts and outflows by week, keeping the original forecast version. A signed contract, MRR or expected renewal is not an actual cash receipt.
For each week, check the cash balance after expected receipts, fulfilment, refunds, commissions and committed outflows. Track unused customer balances and the reserve under the agreed policy separately.
Receipts less refunds, commissions and related outflows — reported separately from margin. Also track subscription renewals and churn, advance-payment discounts, disputes and dependence on a single partner.
GRI is an author-developed analytical framework, not independent certification, an investment rating or a growth guarantee.
Find an observable loss and test possible explanations against the facts.
Define the segment, value, offer, channel, funnel step, economics and accountability.
Specify the inputs, expected output, limits and employee’s role.
Agree a metric and comparison method, check quality, include costs and decide the next step.
The shared Bootcamp structure. Data, actions and the metric are tailored to the chosen lever.
Discuss the challenge, available examples, team involvement and scope. Agree the work before the programme begins.
Days 1–701
Review the workflow and data, choose a constraint and one lever, define the GTM action and experiment rules.
Session: map the customer journey and locate the loss
Process map and challenge statementCollect examples; check IDs and dates
Data dictionary and missing-data listReview relevant GRI areas and test two or three explanations
Evidence-backed constraint mapSession: choose one lever, segment and GTM action
GTM on one pageDescribe the usual process, a non-AI improvement and an AI variant
Technology role and comparison variantsDefine cohort, metric, observation window, costs and stopping rules
Experiment brief v1Checkpoint: agree the solution scope
Build / revise / prepare dataDays 8–1402
Prepare context, build the AI workflow, test typical cases and exceptions, and define human handover rules.
Session: create a context base and first prompt
AI scenario v0.1Run typical cases and verify source facts
Error and correction logTest missing data, conflicts, duplicates and refusal
Exception set and human handover rulesSession: independent quality review on held-out examples
Readiness assessment and critical defectsRun in shadow mode without contacting customers
Time measurement and staff usefulness reviewPrepare the log, group assignment and instructions
Launch pack with prompt versionCheckpoint and owner decision
Limited-test approval or correction planDays 15–2103
Check execution, compare available outcomes, account for costs and limitations, and prepare team handover.
Session: check the first live events and stopping procedure
Working limited testReview deviations and protocol adherence
Event and error logReconcile customers, orders, payments, costs and time
Observed-results tableReview group comparability and alternative explanations
Limitations of the conclusionSession: calculate measures and economics
Draft report and decisionPrepare instructions, materials and continuation plan
Handover packReview: continue, change, stop or extend
Approved report and 30/60/90 planA long sales or repeat-purchase cycle may require more than 21 days to assess a monetary effect. In that case, the result is tested execution and a plan for continued observation.
Proposed format: six 90-minute working sessions and three 30-minute checkpoints. Indicative time for the experiment owner: 7–9 hours per week plus 2–3 hours of preparation. This is not an approved package; scope and involvement are agreed separately.
Outputs include rules for the selected model, a register of receipts and future fulfilment, a CRM and payment workflow, reconciliation instructions and a rolling 13-week cash calendar. Track unused customer balances, renewals, refunds, partner settlements and commissions separately. Test one segment in the first cycle; agree wider implementation after reviewing the results.
A 90-day plan is a document, not 90 days of included implementation and support. Production integration, data migration, licences and ongoing support require separate agreement.
06 / Cash flow
Research and cases inform hypotheses; they do not guarantee the same result in your company. External companies are not Bootcamp clients or partners. Not every case concerns generative AI.
Materials: 10 / 10
Using [reconciled invoices], [due dates], [partial payments] and [disputes], classify delay reasons and missing evidence.
R — You are a careful business workflow analyst for this specific task. A — Using [reconciled invoices], [due dates], [partial payments] and [disputes], classify delay reasons and missing evidence. Calculate amounts with checked rules, keeping currencies and disputed balances separate. F — Evidence and source IDs; observations; missing facts; draft action; human review checklist; metric, costs and limits. T — Clear, specific and without growth promises. Before starting, ask the clarifying questions needed to understand the context, objective and limits. Do not proceed until the inputs and rules are clear.
Limits of the findingUse permitted or anonymised data. A person verifies facts and approves consequential actions.
Bootcamp practiceReplace bracketed inputs with approved context. Test typical cases, exceptions and stopping rules before operational use.
Using [verified balance], [contract terms] and [last action], draft a staff next step or reminder.
R — You are a careful business workflow analyst for this specific task. A — Using [verified balance], [contract terms] and [last action], draft a staff next step or reminder. Do not alter bank details, deadlines, discounts or contracts, issue unauthorised claims or execute payments. F — Evidence and source IDs; observations; missing facts; draft action; human review checklist; metric, costs and limits. T — Clear, specific and without growth promises. Before starting, ask the clarifying questions needed to understand the context, objective and limits. Do not proceed until the inputs and rules are clear.
Limits of the findingUse permitted or anonymised data. A person verifies facts and approves consequential actions.
Bootcamp practiceReplace bracketed inputs with approved context. Test typical cases, exceptions and stopping rules before operational use.
Using [initial invoice cohort], [receipts], [due dates] and [costs], calculate timely full payment and remaining overdue balances.
R — You are a careful business workflow analyst for this specific task. A — Using [initial invoice cohort], [receipts], [due dates] and [costs], calculate timely full payment and remaining overdue balances. Faster receipts are not new profit. Report reconciliation gaps and stop unsafe external action. F — Evidence and source IDs; observations; missing facts; draft action; human review checklist; metric, costs and limits. T — Clear, specific and without growth promises. Before starting, ask the clarifying questions needed to understand the context, objective and limits. Do not proceed until the inputs and rules are clear.
Limits of the findingUse permitted or anonymised data. A person verifies facts and approves consequential actions.
Bootcamp practiceReplace bracketed inputs with approved context. Test typical cases, exceptions and stopping rules before operational use.
Cash is King describes cash flows of US small businesses in a bank-client sample. The historical median buffer covered about 27 days of normal outflows.
Limits of the findingThis is a historical sample description, not a 2026 global benchmark or a reserve rule for your company.
Bootcamp practiceBuild your own receipts and obligations calendar; assess delays using your economics.
Original sourceBarrot and Nanda study the US Federal Quickpay reform, finding recipient employment effects alongside displacement of other firms.
Limits of the findingThis is a payment-reform study, not an AI-tool trial or universal collection return. Company and economy-wide effects differ.
Bootcamp practiceIdentify controllable billing and payment delays; faster cash is not automatically additional revenue or profit.
Original sourceA Danone representative describes cash-application automation in a HighRadius-hosted webinar, reporting 95% automatic matching and 75% lower process costs.
Limits of the findingParticipant and supplier-platform report, without an independent audit. Matching received money is not faster customer payment.
Bootcamp practiceUse exact reconciliation rules first; ambiguous matches remain accountant-reviewed exceptions.
Original sourceA 2023 Microsoft presentation describes collection worklists and reports a 10% improvement in collection efficiency.
Limits of the findingA company slide without the detailed metric formula. It cannot be translated into 10% more cash, lower DSO or higher profit.
Bootcamp practiceUse reconciled debt records and explainable priorities. AI drafts contacts without changing contracts or executing payments.
Original sourceA discussion excerpt for the cash flow route. Use the source’s own context, not as a promise of programme results.
Limits of the findingAn expert quote is not causal evidence or a universal business rule.
Bootcamp practiceUse the question to sharpen your own hypothesis, metric and decision criteria.
Profit is not an event. Profit is a habit!Original source
Understand financial statements, assumptions and the difference between profit and cash. Reconcile explanations with accounting records.
Limits of the findingThe AI exercise is an original Bootcamp adaptation, not content attributed to the book. The programme uses publisher descriptions and open excerpts, not a claimed analysis of every full text.
Bootcamp practiceUnderstand financial statements, assumptions and the difference between profit and cash. Reconcile explanations with accounting records.
Original sourceUse as a practical approach to money-management discipline rather than a universal allocation rule. Authorised people decide payments and distribution.
Limits of the findingThe AI exercise is an original Bootcamp adaptation, not content attributed to the book. The programme uses publisher descriptions and open excerpts, not a claimed analysis of every full text.
Bootcamp practiceUse as a practical approach to money-management discipline rather than a universal allocation rule. Authorised people decide payments and distribution.
Original sourceSelected from AIStart360 Growth Labs, edition 2.0, 26 October 2026. Each item retains its provenance, limitations and links to original publications.
Economics
Separate revenue, variable costs and fixed costs. Compare acquisition cost with customer contribution over a consistent period. Do not treat projected LTV as fact: show scenarios and unknown inputs.
AI & operations
Start with a repeated task, its cost and quality requirements. Compare AI with the current process on equivalent examples. Include review time, correction costs and data constraints. Speed without acceptable quality is not value.
Growth readiness
GRI examines demand, trust, the business model, cash flow, operations, the team and the founder’s role. Start with the intended outcome, collect evidence, choose one constraint and plan how to test it. This guide does not assign scores or predict guaranteed growth.
Cash flow · AI
AI can surface recurring delays and unusual movements in de-identified data. Make financial decisions using verified records and an accountable specialist.
External research and cases inform hypotheses; they do not promise the same outcome. Check current conditions and relevance to the specific challenge.
Field evidence on productivity and heterogeneous effects across worker experience.
Shows how performance changes when knowledge work sits inside or outside the model’s capability frontier.
Explains AI through the economics of prediction and redesign of decision systems.
Strategy as diagnosis, guiding policy and coherent action—not a list of ambitions.
Design product, packaging and pricing around willingness to pay and value metrics.
Seven implementation lessons connecting evals, domain experts, product workflows and iterative deployment.
A field guide for finding, prioritizing and expanding AI use cases from tasks into end-to-end workflows.
Empirical patterns of how AI supports tasks, occupations and human–AI division of work.
A decision-first lens that separates objectives, actions, uncertainty and evidence before choosing models.
A detailed operating guide to CAC, LTV, churn, payback and the metrics that explain recurring-revenue growth.
A warning against false precision in early-stage unit economics and a guide to the data maturity needed for credible ratios.
Twelve metrics for diagnosing the health, efficiency and scalability of a SaaS growth engine.
A simple model connecting annual contract value, required customer count and the resulting sales and marketing motion.
How can a company with a powerful brand, manufacturing expertise and distribution lose a market it helped build? Nokia's story illustrates a change in the basis of competition. Customers increasingly evaluated a smartphone as a software platform: interface, applications, developer support and connected services. Hardware remained necessary but was no longer sufficient. Nokia did not disappear or enter bankruptcy as a result of this episode; it sold substantially all of its Devices & Services business and continued in other activities.
Read the case
What changes first: strategy, or the culture that must execute it? Microsoft's renewal suggests that the question is often a false choice. Cloud investment, subscription relationships, developer tools and cross-functional learning developed together. Revenue growth cannot be attributed solely to one leader, one cultural practice or a slogan.
Read the case
Why did an early digital-camera prototype not secure a profitable digital future? Kodak's case concerns the replacement of a business model, not a company that never noticed digital technology. It invested in multiple forms of renewal. The commercial question was how to replace the economics of film and printing with a durable new source of customer value and profit.
Read the case
The useful question is not whether AI can replace people, but which requests it can resolve well at a lower complete cost while preserving trust and access to human help. Klarna's public figures must be read as company statements with defined periods and channels, rather than a universal staffing formula.
Read the caseTerms and participation
Check whether the challenge fits, and discuss examples and team involvement. Then agree location, language, format, scope, fees and participation terms.
A manual workflow usually needs a process owner and permitted data. Integration with operational systems requires technical participation and a separately agreed scope.
A company works on one lever per cycle. The others inform the next step; they are not six parallel projects.
Establish minimum record-keeping and test on permitted examples first. Never replace missing facts with invented data.
Document quality, costs and limitations. A justified stop helps avoid expanding an uneconomic solution.
Licences, integration development and ongoing support are included only when explicitly agreed in the scope.
It depends on the workflow and customer cycle. The 21 days cover a limited scenario; long-term effects are assessed separately.
Agree permitted materials, anonymisation, access and external services before starting. The first-contact form does not need customer databases or documents.
