CRM at scale
Lifecycle and CRM work around an 8M+ user database, commercial campaigns, segmentation, and adoption inside a large beauty retailer.

I build the systems behind creative work.
I moved from marketing and brand into CRM, luxury retail, and visual practice. Now I build AI-assisted tools that keep context and judgment in the loop.
Lifecycle and CRM work around an 8M+ user database, commercial campaigns, segmentation, and adoption inside a large beauty retailer.
Portfolio projects built as working prototypes: Campaign Pulse, DemandOS, Campaign Sandbox, DataBrief AI, Website Audit Agent.
Photography, visual studies, luxury references, and brand systems used as the judgment layer around technical tools.
About
Operational taste means knowing what to structure, what to leave editable, and when people need to decide.
Málaga is the origin. Madrid sharpened the practice through IE University, marketing, CRM, and commercial teams.
Orlando changed how I read service. Primor brings the pressure of lifecycle work, segmentation, luxury partners, and scale.
The portfolio turns that thinking into campaign tools, data products, brand systems, and visual studies.



A compact read of the contexts that shaped the work: markets, delivery, service, building, scale, and the current loop.
01
Business, marketing, digital analytics, and the first technical vocabulary for turning customer behavior into decisions.
02
Project work with deadlines, partners, and team handoffs: strategy only counted when it became something delivered.
03
A semester at the University of Central Florida sharpened the read on service, retail behavior, and cultural expectations.
04
Campaign tools, data products, image systems, and site architecture turned positioning into usable interfaces.
05
Large audiences, commercial cadence, segmentation, partner expectations, and internal AI adoption make the work accountable.
06
Building the loop between workflow logic, interface design, brand memory, data boundaries, and human review.
The work starts with the decision and ends with a surface people can review, use, and improve.
Decision
What does the user need to understand, choose, approve, or repeat?
Workflow
Inputs, constraints, handoffs, review points, risks, and outputs.
Interface
Prototype the surface where the work becomes visible and usable.
Intelligence
Use AI or ML where it improves speed, synthesis, or diagnosis — not where it removes accountability.
Taste
Brand voice, image logic, pacing, and visual judgment remain part of the system.