
AI agents as workflow, not as chat: The lesson for growth
Because growth agents must have inputs, tools, memory and clear limits.
Practical guides on tracking, dashboards, experiments, data engineering, and AI applied to marketing.

Because growth agents must have inputs, tools, memory and clear limits.

The AI experiments require new metrics, controls and evaluation logics.

How to apply growth engineering principles in small businesses without huge teams.

A practical method to order, cut and decide on growth experiments.

A modern bash bug doesn't only check if the UI works: check if the system measures well.

A concrete path to grow as a growth engineer in a world of AI, data and product.

A method to explain growth results to CEO, marketing, product and engineering.

Because cohorts are essential to understanding whether a change creates lasting value.

How to design growth dashboards that reduce ambiguous instead of adding graphs.

Because data contracts are crucial when experiments, dashboards and AI agents depend on the same events.

Because a short technical document can save experiments from ambiguous, bugs and unnecessary discussions.

How to transform automatic emails into part of the product learning system.

A more mature way of seeing experiments: not winners and losers, but operational learning.

How to distinguish useful personalization from manipulation, especially with AI and advanced segmentation.

A practical guide to designing product events useful for experiments, retention and operational decisions.

How to use fake door tests in a useful, ethical and measurable way to evaluate new functionality.

Because feature flags are product infrastructure, not just convenient technique.

Stakeholder confidence is built with governance, transparency and repeatable decisions.

A checklist to govern agents, experiments and automations without blocking innovation.

A simple model to decide where human review is needed in workflow agents.

Because growth B2B requires models that distinguish person, workspace and company.

Templates and examples to transform vague ideas into experimental and measurable hypotheses.

How to build loops where use, data, experiments and product improve each other.

How to design useful memory for growth AI agents without turning it into a dangerous archive.

How to choose a guide metric that truly guides product, data and experimentation.

How to choose protection metrics to avoid short-sighted optimizations.

How to define and shape activation without falling into vanity meters or arbitrary thresholds.

A journalistic and practical explanation of the difference between operational data and analytical data for growth.

How to design onboarding using events, frictions and experimentation instead of infinite tutorials.

How to monitor AI agents in production with events, evaluations and alerts that are really operable.

How to use log, metrics and mental tracking to see if a product is really generating value.

Because checking the results every hour can turn a valid experiment into a factory of false winners.

How to design lightweight but reliable pipeline to turn raw signals into product decisions.

How to read pricing as part of product, experiments and positioning.

A practical guide to balancing analytics, AI, log and user respect.

How to design retrieves and sources for AI agents that support product and marketing decisions.

Because weak randomization makes even beautiful dashboards and great champions useless.

A light process to turn every test into reusable learning.

How to release growth changes for segments, thresholds and stop signals.

What really distinguishes a growth engineer: code, product, data, experiments and responsibility for the result.

How to use feedback sales without turning every anecdote into roadmap.

How to reason on sample size, minimum detectable effect and duration without falling into blind formulas.

How to build a readable scorecard that connects experiments, metrics and next actions.

How to use segmentation to read experiments and metrics without getting lost in useless micro-clusters.

A practical article on how to move from isolated campaigns to measurable growth systems, inspired by the principles of Growth Engineering.

Because tickets, chats and complaints are valuable product data if you model well.

How to compose a team growth with engineering, product, design, analytics and go-to-market.

A practical guide to tripping: when to include a user in an experiment and when not.

How to connect product and marketing tests to CAC, LTV, payback and margin.

How to make the standup a useful time for controlled experiments, data and releases.

An AI agent does not just answer: he observes, decides, uses tools and produces effects. Here's how to evaluate it with an engineering and human mindset.

A reasoned summary in Italian of AI 2027: timeline, computations, risks of alignment, geopolitics and practical lessons for those who work with data and AI.

AI agents in production need logs, metrics and tracks. Without observation, you don't know if they are helping or creating invisible problems.

A practical taxonomy to measure AI agents: inputs, sources, tools, decisions, approvals and results. Growth starts from reliable signals.

AI agents need solid pipes: collection, cleaning, storage, recovery and monitoring. Without pipeline, the agent works in the dark.

Memory makes an AI agent more useful, but also more risky. A practical guide to designing operational memory, context and privacy.

The retrieved augmented generation allows AI agents to work on real documents. But careless for sources, versions and metrics becomes fragile.

Each AI agent should be born from a hypothesis: which clutch reduces, which behavior improves, which risk controls. Here's how to set up useful experiments.

The features flag allow you to release AI agents for segments, use cases and risk levels. They are a safety belt for intelligent products.

An AI agent can improve one metric and worsen others. Guardrail meters protect quality, security, privacy and user confidence.

Human control does not slow AI agents down: it makes them reliable. That's when to use revision, approval and shared responsibility.

An AI agent can make onboarding clearer, personal and measurable. But it has to reduce friction, not add another level of complexity.

AI agents can help marketing switch from generic brainstorming to measurable hypotheses, segments, experiments and decisions.

An AI agent can help sales and marketing qualify lead, but it must explain why score and respect human and commercial signals.

The AI agents in the support work when they reduce waiting and improve quality. If they close tickets too soon, they are just moving the problem.

An AI agent can turn static dashboards into operational conversations, but it must distinguish insight, assumptions and decisions clearly.

AI agents can help you find problems in your data, but they cannot save a system without ownership, controls and shared definitions.

Testing an AI agent requires more attention than a normal UI change: tripgering, guardrail, segments and output quality matter as much as conversion.

An A/A test shows whether randomization, logging and pipeline work before launching real experiments on AI agents.

If the groups of an experiment do not respect the expected proportions, the result can be unusable. That's why it happens with AI agents.

Triggering decides who enters an experiment. With AI agents it is central to avoid dirty analysis and wrong conclusions.

Before developing a complete AI agent, you can measure whether users really want it with an ethical, clear and respectful fake door.

Sometimes the best way to understand the value of an AI agent is to temporarily remove it from a segment and measure what really gets worse.

When you sell AI agents, the price must reflect outcomes, risk, integration and support. It is not enough to calculate the cost of the model.

AI agents can customize experiences, messages and paths, but without limits they risk becoming invasive or manipulative.

AI agents can help identify risky customers, but value arises when explaining possible human signs, causes and actions.

An AI agent can feed retention loops if it helps the user to get recurring results. But valueless notifications and nudges burn trust.

An AI agent can become part of a growth loop if each use produces data, learning and value that improve the next experience.

AI agents attract attention, but the product-market fit is seen by repeated use, concrete value and willingness to change habits.

SMEs do not need complicated stacks to start with AI agents. Clear processes, reliable minimum data and human control are needed.

An AI agent works well when the flow is clear: input, context, tools, decisions, confirmation, output and measurement.

An AI agent becomes useful when it can use tools. It becomes risky when those permissions have no limits, audits and approvals.

AI agents introduce new risks: prompt injection, abused tools, sensitive data and unverified outputs. Security should be designed in the flow.

AI agents need log to be controllable, but those logs may contain sensitive data. We need minimization, retention and governance.

AI agents can optimize conversions and retention, but responsible growth protects choice, clarity and trust of users.

AI agents can generate very effective persuasive patterns. The team must recognize when optimization exceeds the ethical boundary.

An AI agent can improve the mean metric and worsen the experience of some segments. It requires group analysis, accessibility and context.

A well-made scorecard brings together lenses, metrics, guardrAIls, segments, quality and decisions. It is used to manage AI agents without getting lost in detail.

After an experiment with AI agents, the retrospective serves to save what the team has learned on data, users, prompts, tools and risks.

AI agents change the work of the growth teams, but do not eliminate skills. They serve engineers, PMs, analysts, designers and shared ownership.

The growth engineer in the AI era works on experiments, data, features flag, observation, safety and products that learn from real signals.

AI agents cross product, interface and infrastructure. To build them well, PM, designer and engineer must work on the same flow.

If an AI agent works, the team must know what changed: metrics, context, limits, decisions and next steps.

Before the rollout, an AI agent must be tried by more people: not only for technical bugs, but for sources, tone, limits, permissions and strange cases.

Launching an AI agent for everyone in one day is risky. A gradual rollout allows you to learn, correct and increase autonomy with real data.

An AI agent in production must be monitored as a live system: quality, costs, drift, errors, feedback and guardrail.

The quality of an AI agent is not measured only with correctness. An output must be useful, contextual, safe and operable.

In products with AI agents, the prompt is not only technical text. It is part of the interface, behavior and governance.

AI agents produce better insights when users, events, sources, tasks and results are modelled consistently.

AI agents work best when you distinguish operating and analytical systems. OLTP captures events, OLAP allows questions and decisions.

AI does not eliminate growth engineering. It makes it more strategic: observation, experiments, ethics and human judgment become the real advantage.

90% of A/B tests in marketing are not statistically valid. Discover sample size, peeking, multiple testing and Minimum Detectable Effect for robust testing.

15-20% of Italian students leave after the first year. Predictive models identify risks. Practical guide with ISTAT data and predictive analytics.

Learn how to calculate the Affinity Index, the CPM in-target, and why media planning without affinity and how to fish in the dark. Formula, SQL, case study e-commerce.

Predictive audiences, data-driven attribution, MMM and creative testing. What works in 2026, what is hype, how to amplify (not replace) human work.

Co-related vs causality, survival bias, Simpson's paradox, base rate neglect. Cognitive biases that cost millions to each company and how to avoid them.

Boxplot Guide: how to read it, create it in Python, when to use it. Learn how to see what the media hides in your business.

Client segmenting with cluster analysis: K-means, DBSCAN, RFM, silhouette score. Python code, e-commerce study cases, when using which algorithm.

How to use the joint analysis to discover the real value of product attributes and optimize prices and features with 250+ consumer data.

Because 70% of dashboards are never used and how to create a decision-driven dashboard that the team really consults every day.

Analysis of the state of data-driven culture in Italian companies with ISTAT, DESIGN Index data and EU comparisons. How SMEs can start today.

As professional cycling uses data to optimize performance. Business-wide cycling KPIs: efficiency, clustering and feedback loops.

Practical guide to essential metrics for e-commerce: CR, AOV, CAC, LTV, retention. Framework acquisition→conversion→retention with SQL is case study.

Three statistical methods to predict sales: MA, linear regression and SARIM. Seasonality management, measurement accuracy with MAPE/MAE.

Structural difference between traditional funnel and growth loop. Viral, content, paid and network effect loop with K-Factor, cycle time and metrics measurement.

The HADI cycle (Hypothesis, Action, Data, Insights) for growth analytics. How to test hypotheses, accelerate decisions and scale experiments with statistical rigour.

How to measure the increase in marketing campaigns beyond attribution. Geo-lift testing, incremental testing and iROAS to discover the real ROI.

How to bring data-driven management and analytics to universities. Learning analytics, digital transformation and successful cases Bologna, Politecnico Milano.

How to build perceptive maps to understand the positioning of the brand. Complete guide: survey, PCA, MDS, strategic analysis with Python and Italian case studies.

Kano's model to classify features in Must-be, Performance, Attractive. How to use it for product prioritization and maximize customer satisfaction.

As the Millenniums are transforming Italian management with data, transparency and speed. People analytics, real-time dashboards, data-driven cultures.

Critical analysis of the Net Promoter Score. Scientific limits of NPS, comparison with CSAT/CES, driver analysis and alternative customer loyalty metrics.

Three scientific methods (Van Westendorp, Gabor-Granger, A/B test) to test prices and optimize profits with real data instead of intuition.

Practical guide to cookieless tracking: server-side tagging, Allow Mode v2, first-party data and privacy-compliant alternatives to GA4.

How to do market research in 1-2 weeks instead of 6 months. 7 concrete methods: interviews, smoke tests, surveys, social listening.

How to design correct online surveys: sampling, measuring scales, biases in questions, sample size calculation, chi-square analysis.

Query SQL practices for marketers: revenue per channel, CAC, retention, ROAS, cohort analysis, window functions, CTEs per attribute and CLV.

How to calculate CAC and LTV correctly, interpret the LTV/CAC ratio, optimize the payback period and benchmark by sector (SaaS, e-commerce, marketplace).
Book a short call: we will look at tracking, data, and dashboards, then identify the first useful intervention.
Book a 15 minute call