A focused course, tailored for you
LatAm Fintech Analyst's Strategic-Authority Playbook
How an analytics IC at a LatAm fintech reframes the seat as strategic-authority through hypergrowth-stage operating-model evolution.
When LatAm fintechs tighten operating models around unit economics, analytics ICs without published strategic-authority narratives read as reporting cost.
$199 one-time
Tailored to your situation. Access within 24 hours. 30-day money-back.
Includes a hand-built implementation playbook delivered alongside course access, generated for your specific situation.
Why this course
LatAm fintechs running hypergrowth-stage operating-model evolution reach analytics IC functions in the same cycle. Senior analysts above are protected by their portfolio ownership; junior analysts below are protected by their direct delivery. The IC layer is the band the deck reviews most carefully.
The analytics ICs who survive own a documented strategic-authority narrative with measurable product-and-business outcomes, a stakeholder map across product and business-line leadership, and a quarterly state artefact the head of analytics reads first.
The course covers the three artefacts and the 90-day path to strategic-authority framing. Plus a hand-built implementation playbook against your real analytics scope.
The 12 modules
Module 1. Reading hypergrowth-stage operating-model evolution for analyst implications
LatAm fintech operating-model evolution reaches analytics IC functions in three predictable phases: enterprise unit-economics review, analytics-function review, and IC-portfolio review. The diagnostic decodes which signals (CAC-payback drift, contribution-margin compression, product-velocity benchmarks, FTE-to-revenue ratios) indicate that the analytics IC layer is in the redraw set. Which ICs survive on reporting coverage and which survive on strategic-authority partnership.
Module 2. Generic IC vs strategic-authority partner
Two structurally different framings of the same LatAm fintech analytics IC seat read very differently to the deck. Generic IC shows up as reporting overhead with a deliverable-cadence ratio. Strategic-authority reads as the leadership the business depends on through scaling: documented product-and-business outcomes, stakeholder map across product and business-line, and quarterly state artefact the head of analytics forwards.
Module 3. Your documented strategic-authority narrative
Construct the strategic-authority narrative as a head of analytics-grade two-page document anchored to measurable product-and-business outcomes: product-velocity improvements (cycle-time, deployment-frequency, change-failure rate), unit-economics outcomes (CAC-payback, contribution-margin), customer-experience outcomes (NPS, support-resolution-time), and operational risk reduction. Three structural templates (product-velocity-anchored, unit-economics-anchored, customer-experience-anchored).
Module 4. Stakeholder map across product and business-line leadership
Map your stakeholders across product (product managers, product directors), engineering (engineering leads, platform engineering), business-line leaders (region general managers, banking-product business leads, credit business leads), and adjacent functions (data, customer experience, compliance). Format: stakeholder name, sponsorship-level, last meaningful interaction, current dependency status. The map the head of analytics cites by IC name.
Module 5. Quarterly state artefact for the head of analytics
The quarterly artefact is a two-page state document covering analytics momentum, product-velocity trends, unit-economics contribution, stakeholder partnership status, regulatory-overlay positioning, and emerging risks. Cadence is end-of-quarter delivery to head of analytics with copies to head of product and business-line leads. Three worked examples from real LatAm fintech analytics IC portfolios at different scaling stages.
Module 6. Working with engineering and customer success
Analytics IC work overlaps engineering (instrumentation, experimentation infrastructure), customer success (support escalation, customer-journey optimisation, churn root-cause analysis), and data (data-pipeline, data-quality). The collaboration pattern that strengthens defensibility: shared analytics rituals, joint incident-post-mortems, cross-function analytics reviews credited by IC name. Examples that elevated an IC to analytics lead.
Module 7. Unit-economics storytelling for finance
Unit economics is what finance reads first in LatAm fintech operating-model reviews. Format the unit-economics story as a four-quarter trend with CAC by acquisition channel, payback period by product, contribution-margin by customer segment, and forward optimisation pipeline. Three storytelling templates for different unit-economics profiles (high-CAC growth-anchored, contribution-margin-defence-anchored, customer-lifetime-value-anchored) and the talking points each gives the head of analytics.
Module 8. Cross-product leverage
Reusable analytics IC practices that scale across product lines: KPI-definition templates, experimentation-governance protocols, customer-journey instrumentation models, unit-economics review cadences. The leverage pattern that signals strategic-authority leadership rather than product coverage. How to convert delivered analytics work into published practice the head of analytics cites in operating-model defence.
Module 9. Regulatory considerations for LatAm fintech
LatAm fintech is regulated under Bacen (Brazil central bank) for payments, banking-as-a-service, and open banking, CVM for securities products, CNBV in Mexico for fintech licensing, and emerging frameworks across other LatAm markets. The compliance overlays that strengthen the analytics narrative as regulator-aware fintech analytics partnership.
Module 10. Scope statement: IC vs Senior IC / Analytics Lead
Two overlapping seats with different scopes. IC scope covers analytics delivery, stakeholder partnership, IP authorship at portfolio level. Senior IC scope adds multi-product strategic-authority leadership, business-case ownership, cross-portfolio leverage. Analytics Lead scope adds analytics-function ownership and analytics-cabinet participation. The scope statement that puts you in the Analytics Lead track defensibly.
Module 11. Promotion mechanics inside LatAm fintech analytics
Internal path from IC to Senior IC to Analytics Lead. The promotion artefact (strategic-authority narrative, stakeholder partnership record, unit-economics contribution, regulatory positioning) and the cycle calendar (mid-year review, year-end performance review, promo committee, announcement). What gets an IC shortlisted, what blocks an IC who is otherwise qualified, and how to time your move.
Module 12. Your 90-day move to strategic-authority framing
Day-by-day plan with daily artefacts. Days 1-7: strategic-authority narrative scaffold drafted from your product-line inventory and KPI baseline. Days 8-21: stakeholder map v1 completed with sponsorship-level confirmations. Days 22-45: quarterly artefact v1 delivered to head of analytics. Days 46-60: multi-product strategic-authority conversation. Days 61-90: Analytics Lead conversation scheduled with analytics-cabinet sponsor identified in module 11.
How this addresses your situation
Specific modules that map to what you said you are dealing with.
Modules 1 and 2 cover the diagnostic.
Modules 3 to 5 produce the three artefacts.
Modules 6 to 9 cover cross-function cadence, unit-economics storytelling, leverage, and regulatory.
Modules 10 to 12 cover scope, promotion, and 90-day execution.
FAQ
Will the head of analytics actually read my strategic-authority narrative?
Module 3 is built around the format heads of analytics read.
What if my scope spans multiple products?
Module 3 covers that case.
Why pay for this instead of reading free analytics content?
Free content covers technique.
Is Senior IC actually open?
Module 11 covers that diagnostic.
What is in the implementation playbook for me specifically?
A draft strategic-authority narrative; a draft stakeholder map; a 90-day plan with conversations against your head of analytics.