# Melanys Figueredo Toledano — Full Reference (LLM-friendly) > Long-form companion to /llms.txt. Per-route H1, tagline, hero body, outcomes, and every FAQ question and answer. > MarTech consultant turning scattered data into systems your team can run. CDP implementation, server-side tracking, vendor architecture, marketing automation, and the data architecture connecting marketing, product, and engineering. Programs delivered against GDPR, IAB TCF v2.2, and GPP. --- ## /services/cdp-implementation — CDP Implementation **Tagline.** A customer data platform that actually ships, not one that lives in a roadmap deck. **Hero body.** A CDP implementation is the program that lands a single customer profile across web, app, and CRM, with identity resolution, consent governance, and activation built into the same system. End-to-end programs delivered on Tealium, Segment, and RudderStack, from data model design through audience activation. **Outcomes.** - **One profile, every surface.** Web, app, CRM, and product behaviour resolved into a single customer view your teams can trust. - **Identity that holds up.** Deterministic and probabilistic matching, decay rules, and an audit trail you can defend in a privacy review. - **Consent baked in.** TCF and GPP signals propagated to every destination. No quiet leaks, no after-the-fact retrofits. - **Activation tied to revenue.** Audiences flowing into ads, email, push, and product experiences from day one of activation, not after the platform is fully finished. **FAQ.** - **Which CDP should I choose?** Tealium, Segment, and RudderStack each fit different shapes of company. Tealium leads on enterprise compliance and EU data residency. Segment suits product-led SaaS teams. RudderStack appeals to teams who want a warehouse-native architecture. The right answer comes from your stack and team, not a vendor leaderboard. - **Do I actually need a CDP, or is a tag manager enough?** GTM solves tag deployment. A CDP solves identity, audiences, and activation. If your problem is fragmented user profiles across web, app, and CRM, a CDP is the right tool. If your problem is just shipping pixels reliably, a tag manager is enough and a CDP is overkill. - **Can you migrate us off our current CDP?** Yes. Migrations work best when paired with a data model revision rather than a like-for-like swap, since the previous model usually carries a few years of compromise. Past replatforming work covers Tealium, Segment, and mParticle, including parallel-run cutovers. - **How do you handle GDPR and consent?** Consent runs through the CDP as a first-class signal, not a sidecar. Each source emits a consent state, and destinations only fire when permitted. The implementation aligns to TCF v2.2 and GPP, with audit trails your DPO can hand to a regulator without rewriting them. - **Will you work with our existing engineering team?** Yes, almost always. The handover plan assumes your team owns the platform at the end of the engagement. The work includes documentation, paired build sessions, and enablement so the program does not collapse on rollover. - **What drives scope and cost on a CDP program?** Scope is driven by the number of source systems, the destination footprint, identity complexity, consent and regional governance, and the depth of activation required at launch. Each of those moves the engagement substantially. Cost and timeline are scoped during discovery against the specific shape of your stack, never quoted blind. - **What is the difference between a real-time CDP and a warehouse-native one?** A real-time CDP, like Tealium AudienceStream, resolves identity and activates audiences inside the platform itself, with low-latency triggers. A warehouse-native CDP, like RudderStack or Hightouch-style architectures, leaves the data in your warehouse and syncs audiences out via reverse ETL. Real-time wins on activation latency and operator UX. Warehouse-native wins on data ownership and modelling depth. --- ## /services/martech-architecture — MarTech Architecture **Tagline.** Stack decisions you can defend in five years, not five quarters. **Hero body.** A MarTech architecture engagement designs the system underneath your marketing, not the tools on top. The work covers a full audit of the current stack, a model of the data and integration flows that connect it, and a defensible target state with vendor selection and a phased rollout plan. **Outcomes.** - **A target stack you can defend.** A documented architecture with the trade-offs written down, so the next CMO inherits decisions, not folklore. - **Vendor choices grounded in your reality.** Procurement picks made against your data volumes, team skills, and compliance posture. Not against analyst quadrants. - **Integrations that survive a re-org.** A reference data flow connecting CRM, CDP, automation, ads, and analytics, with contracts that hold when ownership changes. - **A sequencing plan with clear gates.** A phased roadmap with dependencies and stop/go decision points, so leadership always has the option to pause or pivot. **FAQ.** - **What does a MarTech architecture engagement actually deliver?** A target-state architecture, a vendor shortlist for the categories that need a decision, and a sequenced roadmap with named owners. The deliverable is a defensible plan your team and your CFO both believe in, not a 90-slide deck that sits in a folder. - **How is this different from buying a Gartner report?** Analyst reports rank vendors by category. They do not score them against your data volumes, your team skills, or the contracts you already have. This engagement starts from your stack and your constraints, then narrows the field to the real candidates that fit. - **Do you take vendor commissions or referral fees?** No. The engagement fee is the only revenue from the project. That keeps the recommendation honest, and it keeps procurement comfortable when I sit in on negotiations. - **Can you stay on after the roadmap is signed off?** Often, yes. A common follow-on is leading the first implementation phase or sitting as a fractional advisor through procurement and the early build. That keeps the design intent intact while the team is ramping. - **What inputs do you need before the engagement starts?** A short list of stakeholders, access to current contracts and a high-level data flow, and a sense of the question that prompted the engagement (vendor decision, re-platform, post-merger consolidation, governance reset). The rest gets uncovered in audit. --- ## /services/data-strategy — Data Strategy **Tagline.** A data strategy that survives contact with the team that has to run it. **Hero body.** A data strategy engagement defines what is worth measuring, who owns it, and how it gets used. The output is a governance model, a measurement framework, and an activation plan tied to revenue, not a dashboard wishlist. **Outcomes.** - **Metrics tied to decisions.** Every metric in the framework points to a real action a real person takes. The rest get cut. - **Governance that holds.** Owners, definitions, and SLAs documented in one place. Disputes resolved by reading the doc, not by the loudest voice in the room. - **Activation as a first-class step.** Data leaves the warehouse and shows up in product, marketing, and sales workflows on a schedule, not on request. - **A path off vanity metrics.** Reporting reframed around input metrics teams can move, instead of output metrics no one can directly affect. **FAQ.** - **What is the difference between data strategy and analytics?** Analytics answers questions. Data strategy decides which questions are worth answering, who owns the answers, and how they end up in a workflow. Without strategy, analytics teams ship dashboards no one opens. - **Do you write SQL or build dashboards?** Not as the deliverable. The engagement defines what to build and who builds it. If the team needs hands-on help producing the first reference dashboards, that gets scoped as a follow-on rather than rolled into the strategy fee. - **Will the strategy work for our warehouse setup?** Yes. The framework is warehouse-agnostic and travels cleanly across BigQuery, Snowflake, Redshift, and Postgres-shaped warehouse setups. The governance and activation patterns stay the same; the implementation details adapt. - **Who needs to be in the room for this to work?** A senior owner who can resolve cross-functional disputes, plus marketing, product, finance, and data leads. Without that owner, the strategy stalls in committee. Naming them early is part of the engagement design. - **How do you handle data that lives in spreadsheets?** Honestly. Some of it gets brought into the warehouse on a schedule, some of it stays in spreadsheets but with an owner and a freshness rule, and some of it gets retired. Forcing every spreadsheet into a pipeline is how strategy projects collapse under their own weight. - **What is the smallest version of this engagement that still produces value?** A focused listening tour plus a measurement framework. That alone gives leadership a defensible answer to "what are we actually measuring and why," and surfaces the highest-leverage gaps. Everything else (governance, activation, rollout) layers on top. --- ## /services/marketing-automation — Marketing Automation **Tagline.** Lifecycle programs that read like the brand, not like a template library. **Hero body.** A marketing automation engagement turns a roadmap into running lifecycle programs. The work covers audience logic, journey architecture, and content systems on Braze, Iterable, Customer.io, and HubSpot, then ships the first programs end-to-end with the in-house team. **Outcomes.** - **Lifecycle programs that ship.** Onboarding, retention, win-back, and post-purchase live in production with a measurement plan, not perpetually in draft. - **Audience logic that scales.** Segment definitions written once, reused everywhere, and easy for the next operator to read. - **Content that does not embarrass the brand.** Templates and tone guides aligned with the brand team. No more emails that look like 2014 Mailchimp. - **A measurement loop you can act on.** Holdouts, send-time experiments, and unsubscribe diagnostics designed in, not added as a retrofit later. **FAQ.** - **Which marketing automation platform do you work with?** Braze, Iterable, Customer.io, and HubSpot are the platforms I work with most often. Braze and Iterable for enterprise B2C, Customer.io for product-led SaaS, and HubSpot when the team needs CRM, marketing, and CMS in one place. - **Can you migrate us between platforms?** Yes. Migrations work best when paired with a journey redesign rather than a like-for-like rebuild, since the previous platform usually shaped the programs in ways the new one does not need. Past migrations include moves between HubSpot, Braze, and Customer.io. - **Do you write the email and push copy?** The engagement covers journey design, audience logic, and the content system. Copy itself is usually written by the in-house brand team or a copywriter, with input from me on structure, length, and journey fit. If copy is the bottleneck, a writer can be brought in for the duration of the program. - **How do you handle deliverability?** Deliverability is a baseline requirement, not an optimisation. The engagement covers domain warming, list hygiene, suppression logic, and authentication (SPF, DKIM, DMARC). For platforms with managed deliverability, the work coordinates ramp-up with the vendor team. - **Can you work alongside our existing CRM and lifecycle team?** Yes, that is the default mode. The team owns the platform after I leave, so the engagement is designed around pairing, documentation, and certification on the runbook rather than handing back a sealed black box. - **Which lifecycle program tends to ship first, and why?** Onboarding usually goes first. It has the cleanest audience entry rules, the fastest feedback loop, and the most direct line to activation metrics. Retention and win-back come later because they need a steadier signal of what good usage actually looks like for your product. --- ## /services/tracking-implementation — Tracking Implementation **Tagline.** Tracking that holds up under audit, ad blockers, and the next privacy update. **Hero body.** A tracking implementation engagement designs and ships the measurement layer underneath your site, app, and ad spend. Tag management, server-side tracking, consent enforcement, and conversion APIs delivered as one system. **Outcomes.** - **Measurement that survives ad blockers.** Server-side tracking and conversion APIs that recover the signal browsers and extensions block client-side. - **Consent enforced before tags fire.** TCF and GPP signals checked on every event. No leakage, no after-the-fact retrofits. - **A tag library you can read.** GTM containers documented, naming standardised, and dead tags removed. The container makes sense to the next person who opens it. - **A tracking plan tied to outcomes.** Events mapped to revenue, retention, or product KPIs. No more 400-event taxonomies that no one queries. **FAQ.** - **Why bother with server-side tracking?** Browsers, extensions, and OS-level privacy features now block a meaningful share of client-side hits depending on industry. Server-side tracking and conversion APIs recover that signal, keep first-party data inside your domain, and reduce reliance on third-party cookies. - **Do you do server-side GTM (sGTM) or Tealium EventStream?** Both, plus Stape and self-hosted server-side containers when the use case calls for it. The choice depends on your existing stack, hosting preference, and how the team wants to operate the system day-to-day. - **Can you fix a broken tracking implementation we already have?** Yes. Recovery engagements start with an audit and reconciliation against ad platforms and backend systems. The output is a prioritised list of fixes ranked by attribution impact, then the implementation work to close the gaps. - **How do you handle GDPR and IAB TCF?** Default-deny consent posture, with TCF v2.2 and now GPP signals checked at the tag and the server-side endpoint. Restricted-geography suppression and audit trails are built in. The DPO gets a doc they can hand to a regulator without rewriting it. - **Will you train our team to operate it?** Yes. Handover includes a runbook, a change-control process, alerting on tag failures, and enablement sessions for the team that owns the container after I leave. The system does not require me to stay. - **What variables make a tracking project hard to scope upfront?** The number of source surfaces (web, app, kiosk), the consent regime, the number of ad platforms with conversion APIs, the depth of reconciliation needed, and the maturity of the existing GTM container. Each of those moves the engagement substantially. Scope and timing are agreed during discovery, never quoted blind. --- ## /work-with-me — Work With Me **Three engagement shapes.** - **Strategy sprint.** Focused, fixed-scope engagement to answer one big question. Stack audit, measurement framework, vendor recommendation, or roadmap. Output is a written brief and a readout. - **Implementation lead.** End-to-end implementation engagement on CDP, tracking, lifecycle, or MarTech rebuild. Discovery to handover, with the in-house team owning the system at the end. - **Fractional MarTech advisor.** Monthly retainer. A standing seat at the table for a leadership team without an in-house MarTech leader. A few days a month of strategy, vendor reviews, hiring input, and on-call advice. **What I do not take on.** - Pure ad media buying or paid acquisition campaigns. - Static brand websites without data, integration, or systems work. - Engagements where success depends on hiring an internal team I will not meet. - White-label work for agencies that does not name the client to me. - Anything I do not believe I can deliver real value on inside the engagement. **FAQ.** - **Do you work remotely or onsite?** Mostly remote, with onsite for kickoff, mid-engagement working sessions, and any moment where being in a room with the team unblocks a decision. Bologna-based, comfortable across European time zones. - **Do you sign NDAs?** Yes, mutual NDA on request before the scoping conversation. The scoping doc and proposal are covered by it. - **Can you work alongside an existing agency?** Yes, often. Strongest fit is when the agency owns delivery and I sit on the data, MarTech, or measurement layer as a senior counterpart. Less good fit when the lines of ownership are not agreed in advance. - **How do you handle confidentiality of past work?** Client names listed on this site are mentioned with permission. In conversation, scope and approach are shareable, but specifics on data, results, and internal politics stay with the client unless we have explicit go-ahead. - **Do you take on multiple clients at the same time?** Yes, but with a hard cap on active hours per week so each engagement gets its committed time. Implementation leads usually run as a single primary engagement plus one or two advisory retainers. - **How does scope and pricing get agreed?** Both surface through discovery, not a price list. The intro call frames the problem; a written scoping doc captures what success looks like; the proposal lays out scope, deliverables, and commercial terms against your specific situation. Every engagement is shaped by team size, business model, data sources, and tooling, so there is no useful generic answer in advance. - **What does the first conversation cover?** A 30-minute call to understand the situation, the question driving the engagement, who else is involved, and what good looks like for you. No deck, no formal pitch. The goal is mutual clarity on whether the work fits, not a sale. --- ## /speaking — Speaking & Podcasts **Tagline.** Conversations on data, MarTech, and how careers actually shift. Podcast guest, panelist, workshop host. Working in English, Spanish, and Italian. **Recent podcast appearances.** - **Embracing Curiosity and Continuous Learning.** Women In Tech Talks (WIT), February 2025. On resilience, self-learning, and the path from outside the industry into senior MarTech work. Born in Cuba, raised in Italy, built a career bridging marketing and technology, and now help others find their own way in. - **My Journey into Tech and AI Innovation.** Storytime Radio, April 2025. A conversation about data platforms, web development, AI integrations, and the choices that shape a career as a digital consultant and builder. **Talks I can give.** - **CDP implementation in regulated industries.** How to ship a customer data platform in finance, telco, or healthcare without breaking consent, identity, or legal review. Identity resolution, consent orchestration, and what an enterprise rollout actually looks like. - **Server-side tracking and consent in the EU.** GDPR, IAB TCF v2.2, and GPP in practice. Why client-side tracking is degrading, how server-side and conversion APIs recover signal, and how to keep consent enforced end to end. - **First-party data strategy for D2C and growth brands.** Identity resolution across web, app, and CRM without a 12-month replatform. The data model, the activation surface, and the small set of decisions that determine whether the program ships. - **MarTech architecture: stack audits, vendor selection, and sequenced rollouts.** The difference between a roadmap that names owners and a slide deck that names categories. Tealium, Segment, RudderStack, and how to choose between real-time and warehouse-native. - **Marketing automation, measured against revenue.** Lifecycle programs on Braze, Iterable, Customer.io, and HubSpot. Onboarding, retention, win-back, and how to design a measurement framework that survives contact with a CFO. - **AI-driven growth without the hype.** Where AI changes growth work in 2026 (segmentation, content, prediction, decisioning) and where it does not. Practical patterns for teams that already have a data and MarTech stack. - **From bartender to MarTech consultant.** A career story for anyone outside the industry looking in. Self-learning, the systems-thinking shift, and what made the difference between dabbling in tech and getting paid to ship it. **Available for.** Podcasts (editorial interviews on MarTech, CDPs, data strategy, career-shift stories). Panels and keynotes (conferences and meetups for marketing, data, or product audiences, remote or in-room). Workshops and AMAs (hands-on sessions for in-house teams: CDP rollouts, server-side tracking, lifecycle programs). --- ## /collab — Collaborate **Tagline.** Let's build something together. Outside of full project engagements: podcasts, panels, advisory calls, open-source, technical reviews, joint writing. **Open to.** - **Podcast invitations.** MarTech, CDP, data strategy, server-side tracking, AI-driven growth, or career shifts into tech. Comfortable in English, Spanish, and Italian. - **Speaking and panels.** Keynotes, panels, technical AMAs, and workshop sessions for marketing, data, or product audiences. Remote or in-room. - **Advisory roles.** A few hours a month for founders or leadership teams shaping a MarTech, CDP, or data strategy program. Strategy, vendor reviews, hiring input. - **Open-source and side projects.** Tooling around CDPs, tag management, server-side tracking, or developer ergonomics for marketing teams. Bring the repo and the problem. - **Technical reviews.** Independent review of a MarTech architecture, CDP rollout, or measurement framework. Useful before a vendor decision or a board check-in. - **Content collaborations.** Joint writing, research, or long-form pieces with practitioners and platforms working on data, marketing, and AI in Europe. **FAQ.** - **What kind of collaborations are you open to?** Podcast invitations, speaking, panels, advisory roles, open-source contributions, and technical reviews. The common thread is MarTech, customer data, server-side tracking, AI-driven growth, or career-shift stories. If it does not fit but you think it should, send the brief anyway. - **Do you charge for podcasts and speaking?** Podcast appearances are usually unpaid for editorial shows; speaking gigs depend on format, audience, and travel. Either way, scope and any fee surface during the intro conversation. - **In what languages can you speak or be interviewed?** English, Spanish, and Italian. Comfortable in all three for podcasts, panels, and workshops. - **How much notice do you need?** For podcasts and panels, two to three weeks is comfortable. For workshops or technical reviews, more, since prep matters. Tighter timelines are workable when the topic is in my regular orbit. - **How is this different from working with you on a project?** Project work runs through /work-with-me and goes through scoping. Collaborations here are bounded by their own format, podcast, talk, advisory call, review, and do not need a full engagement to happen. --- ## /it/consulenza-martech — Consulenza MarTech (Italiano) **Tagline.** Audit dello stack, scelta dei vendor, architettura target. Owner per ogni snodo, niente PowerPoint da archivio. **Hero body.** Quando lo stack di marketing tech smette di parlarsi, la colpa raramente è del tool. Mappo le decisioni che ti tengono fermo, scelgo i vendor che reggono al tuo modello operativo, e consegno una roadmap che il team interno può portare avanti senza di me. Trasformo dati frammentati in sistemi che il team interno può gestire dopo il passaggio di consegne. **Risultati.** - **Stack mappato come decisione, non come inventario.** Audit operativo che parte da chi fa cosa, perché, e con quale dato. Non un elenco di logo, ma le dipendenze che fanno saltare i progetti. - **Vendor scelti contro vincoli reali.** Selezione che parte da consenso, identità, modello dati e compliance, non dal magic quadrant. Tealium, Segment, RudderStack, sGTM, Stape: la scelta dipende da te. - **Roadmap con owner e gate di decisione.** Sequenza di rollout in fasi, ognuna con responsabili nominali, milestone misurabili, e un punto in cui la direzione può scegliere se proseguire o cambiare. - **Handover che resta dopo di me.** A fine ingaggio il team in-house ha la documentazione, gli accessi, e il modello mentale per continuare. Non lascio black box. **FAQ.** - **Qual è la differenza fra architettura MarTech e selezione vendor?** La selezione vendor risponde a "quale tool". L'architettura risponde a "come fanno a parlarsi", "chi è owner di cosa", "dove sta il consenso", "come si aggiorna il modello dati". L'una senza l'altra fa danni: lo stack giusto montato male non funziona; lo stack sbagliato montato bene è una zavorra. - **Lavorate solo con Tealium?** No. Tealium è la specializzazione più profonda, ma la scelta del CDP o del tag manager dipende dal tuo modello dati, dal volume, dalle integrazioni esistenti, e dal team. Segment, RudderStack, mParticle, sGTM, e tag manager nativi sono tutti opzioni valide a seconda del contesto. - **Servirà sostituire tutto lo stack attuale?** Quasi mai. La maggior parte degli ingaggi di architettura porta a sostituire una o due componenti chiave e a ricablare il modo in cui il resto si parla. Sostituzioni ampie partono solo se i debiti accumulati sono insostenibili e la direzione lo decide consapevolmente. - **Come gestite consenso e GDPR a livello di stack?** Il consenso è un livello dell'architettura, non un plugin. Lavoro con CMP TCF v2.2 e GPP, e disegno l'orchestrazione in modo che ogni evento, server-side incluso, rispetti la scelta dell'utente. Compliance e attivazione marketing non sono in conflitto se l'architettura è progettata bene. - **Lavorate con team interni o solo in autonomia?** Sempre con il team interno. L'obiettivo è che a fine ingaggio il team possa proseguire senza di me. Non sono un fornitore esterno che lascia un manuale, sono un consulente che lavora dentro la cabina di regia. - **Si può cominciare senza un audit completo?** Si può, se la direzione ha già una decisione precisa. Più spesso, l'audit è il passaggio che evita di buttare via mesi di rollout su una scelta di architettura sbagliata. Il discovery è breve e mirato, non un esercizio accademico. --- ## /it/consulenza-cdp — Consulenza CDP (Italiano) **Tagline.** Modello dati, identità, consenso, attivazione. Un sistema che il tuo team possiede, non una black box che dipende da me. **Hero body.** Una customer data platform non si misura dalle feature del vendor, ma da quanti casi d'uso accendono i marketing operations dopo il go-live. Lavoro su Tealium, Segment, e RudderStack per brand italiani ed europei: dal modello dati alla risoluzione dell'identità, dal consenso all'attivazione, fino alla cassetta degli attrezzi che il team in-house si porta a casa. **Risultati.** - **Profilo cliente unificato fra web, app e CRM.** Identity resolution che sopravvive a logout, browser privacy, e cambi di device. Niente silos di prima e seconda mano da ricucire ogni volta. - **Consenso applicato di default, ovunque.** IAB TCF v2.2 e GPP integrati a livello di CDP, non come tappo finale. Server-side e attivazioni rispettano la scelta dell'utente by design. - **Audience attivabili nei canali che usate già.** Audience costruite nel CDP, attivate nel CRM, nelle piattaforme di lifecycle, e nelle conversion API senza pipeline di emergenza. - **Team in-house autonomo a fine progetto.** Documentazione, runbook, e capacity transfer. Il sistema è del cliente, non del consulente. **FAQ.** - **Qual è la differenza fra un CDP e un tag manager?** Un tag manager (GTM, Tealium iQ) governa il rilascio dei tag e degli eventi a livello di sito o app. Un CDP costruisce e mantiene il profilo cliente nel tempo, risolve l'identità fra device, e rende quei profili attivabili nei canali a valle. Servono entrambi, ma risolvono problemi diversi. - **Real-time CDP o warehouse-native?** I CDP real-time (Tealium AudienceStream, Segment) vincono su latenza di attivazione e UX per gli operatori marketing. I CDP warehouse-native (RudderStack, Hightouch-style) vincono su proprietà del dato e profondità di modellazione. La scelta dipende da chi opera lo strumento, da dove vive il dato canonico, e dai casi d'uso. - **Quanto tempo richiede un'implementazione CDP?** Dipende da casi d'uso, fonti dati, e maturità del team interno. Il discovery serve proprio a inquadrare la sequenza realistica, e nessun progetto serio si stima al telefono. La prima iterazione mira sempre a far accendere casi d'uso veri, non a un go-live cerimoniale. - **Lavorate con CMP italiane o solo internazionali?** Entrambe. Quello che conta è che la CMP scelta supporti TCF v2.2 e si integri pulitamente con il CDP e con il livello server-side. Funziono con la CMP che hai, salvo che la sua architettura blocchi i casi d'uso prioritari. - **Cosa succede dopo il go-live?** Il team in-house diventa il primo livello di gestione, con runbook e formazione documentati. Posso restare disponibile in advisory leggero per i mesi successivi, ma il sistema deve poter girare senza di me. - **Posso partire senza sostituire il MarTech esistente?** Spesso sì. Il CDP si integra con il MarTech che hai (HubSpot, Salesforce, Braze, Iterable, ESP nazionali), accendendo identità, audience e attivazioni senza sostituire l'intera filiera. Sostituzioni ampie partono solo se i vincoli del MarTech esistente bloccano il caso d'uso. --- ## Past Clients Vodafone Italy, Unipol, De'Longhi, Leroy Merlin Italy, Alpitour, EdenViaggi, Twinset, ho.mobile, Edenred, Sky Italy. Names listed with permission. No project-specific outcomes shared publicly. ## Contact - Email: hello@melanys.me - LinkedIn: https://www.linkedin.com/in/melanysft/ - GitHub: https://github.com/melanyss - X: https://x.com/MelanysFT - Medium: https://medium.com/@melanyss