Map before building
I clarify the goal, map the current journey, locate friction, identify ownership, and define the required next states before deciding what the automation should do.

MARKETING AUTOMATION SPECIALIST
I build practical CRM systems for follow-up, booking, onboarding, retention, and reactivation.
About the work
I focus on the operating path behind a customer journey: what the CRM should record, who owns the next step, and whether the system can be tested and understood later. The portfolio documents that work through practical CRM builds, workflow logic, and visible implementation decisions.
I continue to strengthen this practice through readable CRM structure, deliberate workflow logic, sample-record QA, and documentation that keeps ownership, handoff, and system state visible and easier to inspect.
The work behind the title
A form, calendar, pipeline, or workflow is only one part of the experience. I am interested in how the pieces connect, what the CRM records, when a person steps in, and what happens next.
The small decisions matter: a useful field, a safer exception path, or a clearer handoff can give the next person enough context to act.
I became interested in what a person sees, what they understand, and how an interface makes the next useful action clear.
That attention moved beyond individual pages toward the forms, messages, calendars, records, and human handoffs that continue after submission.
My current direction centres on CRM implementation, workflow logic, operational clarity, sample-record QA, and documented portfolio evidence.
Working principles
Good automation should make follow-up easier to manage, test, and improve.
I clarify the goal, map the current journey, locate friction, identify ownership, and define the required next states before deciding what the automation should do.
I use readable stages, names, and conditions, avoiding unnecessary complexity that makes the workflow difficult for another person to inspect, maintain, or improve.
I run sample records through normal, exception, timing, and handoff paths so the system is judged by complete CRM state changes, not a successful trigger alone.
I record workflow intent, key conditions, ownership, handoff details, known limits, and improvement notes so the implementation remains understandable after the initial build.
Practice and proof.
The practice centres on implementation choices that can be inspected: how CRM state is organized, how workflow logic handles handoffs, and how QA and documentation support the system after configuration.
Verified professional development
Salesforce / Coursera / 2026
Supports pipeline structure, sales-process visibility, lifecycle status, and operational handoff thinking across CRM implementation work and portfolio builds.
Verify Salesforce Sales Operations certificateGoogle / Coursera / 2026
Supports planning, sequencing, documentation, and disciplined handoff decisions across multi-step CRM and workflow implementations in portfolio builds.
Verify Google Project Management certificateGoogle / Coursera / 2026
Supports measurement thinking, reporting context, and operational visibility when evaluating how a system should be monitored and improved.
Verify Google Business Intelligence certificateGoogle / Coursera / 2026
Supports responsible AI-assisted planning, structured analysis, and documentation during scoped workflow work without replacing implementation judgment or evidence.
Verify Google AI certificate