Problem
Validation lived across devices, manual counting and scattered checks. The same failure patterns resurfaced across markets and campaigns.
Operational friction,
made legible.
CRM SYSTEMS · LIFECYCLE AUTOMATION · QA INFRASTRUCTURE · FRONTEND TOOLING
I work inside CRM operations and build reusable systems around recurring work: validation, lifecycle decisioning, migration, reporting, and interfaces that make complex workflows easier to inspect and run.
5+years CRM16+marketsSFMC+ IterableBerlinbased
CAPABILITY MAP
Public artifacts are only part of the work.
QA infrastructureOlympus
Lifecycle decisioning / governanceDecision Engine
CRM migration systemsTemplate Conversion
Reporting automationPerformance Reporting
Lifecycle / journey operations16+ markets · professional scope
SFMC / IterableProfessional scope
Frontend systemsMind Museum
Some systems can be shown. Some can only be described. The distinction is intentional.
01DEPTH 015M
CRM QA SYSTEM · PUBLIC RECONSTRUCTION
Olympus
A browser-based QA system that consolidated recurring pre-flight checks across SMS, push, deep links and AMPscript into one validation layer.
CAMPAIGN QA~1 day → 15 min
Mobile campaign validation after recurring checks were moved into one pre-flight layer.
CHECK FAMILIES4
SMS · Push · Deep Links · AMPscript
PUBLIC PROOF BOUNDARYSynthetic data
The public reconstruction uses generic branding and synthetic data only.
APOLLO / PUSH QA
VALIDATION SURFACECopy → width → preview → verdictPUBLIC RECONSTRUCTION · SYNTHETIC DATA
System decision
Separate QA rules from campaign execution, encode them once, and make the result available before a test send.
Role
Problem definition, interface design, frontend implementation, validation logic and iteration.
02DEPTH 035M
LIFECYCLE DECISIONING / GOVERNANCE
Decision Engine
A deterministic decision layer for eligibility, risk, offer resolution, generation boundaries and measurable outcomes.
PROFILE C · SYNTHETICTHE MODEL CAN WRITE. IT NEVER GETS TO DECIDE.
USER_CONTEXT
consent: true
open_service_issue: true
contact_risk_flag: true
authorized_offer: null
offer_resolution_status: "not_evaluated"DECISIONHARD STOP
Promotional path ends before offer resolution or generation.
DECISION TRACE
signal · profile entered route
gate · contact_risk_flag=true
suppression · STOP
routing · service path only
Problem
Decision logic tends to leak into journeys, templates and channel rules, making the system difficult to inspect and govern.
System decision
Put deterministic eligibility and risk checks before content, resolve offers outside generation, validate before action and log every route.
Boundary
Independent concept. Sector-neutral, synthetic and anonymized. The local prototype demonstrates decision logic; generation is simulated.
03DEPTH 055M
CRM MIGRATION SYSTEMS
Legacy Template Conversion
A rule-based HTML conversion workflow that turns repeated legacy-email cleanup into an editable migration system with visible output and quality checks.
01SOURCE HTML
<font color="#111111">
<b>{{OLD_HEADLINE}}</b>
</font>
<br>
<a href="{{OLD_URL}}">
Read more
</a>02RULE MAPPING
<b>→<strong><font …>→<span style=…><br>→<br />{{OLD_HEADLINE}}→{{ headline }}{{OLD_URL}}→{{ destination_url }}03CONVERTED OUTPUT
<span style="color:#111111;">
<strong>{{ headline }}</strong>
</span>
<br />
<a href="{{ destination_url }}">
Read more
</a>QUALITY CHECK9 RULES ONANGLE PAIRS · BALANCEDFORMULA-DRIVEN
Why it existed
Migration work required the same template reconstruction patterns repeatedly across markets.
System decision
Represent transformations as editable rules that run in order, so source HTML, converted output and quality checks stay in one inspectable workflow.
Stack
Google Sheets · formulas · HTML/CSS · migration rules · modular content systems
04DEPTH 075M
SALESFORCE AUTOMATION · PUBLIC RECONSTRUCTION
Automated Performance Reporting
A scheduled SFMC reporting chain that replaced a repeated morning reporting routine with an automatically generated and delivered report.
Scheduled SQL→Validate→Build HTML→Email
PERFORMANCE REPORTING · PUBLIC RECONSTRUCTION
Problem
Campaign data pulls, metric checks and formatting were repeated manually during high-volume periods.
System decision
Connect scheduled SQL, validation, HTML generation and email delivery into one repeatable chain.
Platform
Salesforce Marketing Cloud · Automation Studio · SQL · HTML
05DEPTH 100M
FRONTEND / INTERACTION SYSTEM
Mind Museum
This site: a state-based, canvas-assisted personal archive whose atmosphere is implemented as a frontend system rather than a set of decorative effects.
MIND MUSEUM / 2026The interface is part of the argument.
The proof is not the crystal. It is the system underneath it: chamber state, canvas layers, responsive behavior, reduced-motion handling and event tracking working as one authored interface.
STATEchamber transitionsCANVASambient layersRESPONSIVEmobile → desktopREDUCED MOTIONmotion fallbackEVENT TRACKINGinteraction events
Role
Concept, information architecture, visual system, frontend implementation and iteration.
Stack
Vanilla JavaScript · HTML/CSS · Canvas · event tracking
Constraint
Keep the personal archive atmospheric without making professional work difficult to find. This /works layer is the answer.