Portrait of Jonel Ligaya, CRM and marketing automation specialist

MARKETING AUTOMATION SPECIALIST

I build practical CRM systems for follow-up, booking, onboarding, retention, and reactivation.

About the work

I turn unclear follow-up into systems people can use.

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.

Current directionCRM implementation, marketing automation, and operations-oriented system work.

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.

3
Detailed case studies
12
Documented workflows
36
Proof artifacts
Inspect the portfolio evidence

The work behind the title

I care about what happens after someone clicks submit.

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.

  1. 01

    Interface and next-action decisions

    I became interested in what a person sees, what they understand, and how an interface makes the next useful action clear.

  2. 02

    Connected systems and handoffs

    That attention moved beyond individual pages toward the forms, messages, calendars, records, and human handoffs that continue after submission.

  3. 03

    CRM workflow and proof-led implementation

    My current direction centres on CRM implementation, workflow logic, operational clarity, sample-record QA, and documented portfolio evidence.

Working principles

Judgment before automation.

Good automation should make follow-up easier to manage, test, and improve.

  1. 01

    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.

  2. 02

    Keep the system usable

    I use readable stages, names, and conditions, avoiding unnecessary complexity that makes the workflow difficult for another person to inspect, maintain, or improve.

  3. 03

    Test the complete journey

    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.

  4. 04

    Document what matters

    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 work comes first. Training supports it.

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.

01

CRM and operations

  • Pipeline stages and lifecycle state that make ownership visible
  • Fields, forms, calendars, and records that preserve useful context
  • Routing and operational handoffs that clarify the next responsible action
02

Automation

  • Follow-up and appointment workflows with clear timing and stopping conditions
  • Onboarding, retention, and reactivation paths tied to lifecycle state
  • Exception logic and staff notifications for moments automation should not handle alone
03

Supporting practice

  • Sample-record QA and troubleshooting across expected and exception paths
  • Documentation that records workflow intent, ownership, and handoff guidance
  • Measurement planning with responsible AI-assisted support for structured analysis

Verified professional development

Credentials that support the practice.

01

Salesforce Sales Operations Professional Certificate

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 certificate
02

Google Project Management Professional Certificate

Google / Coursera / 2026

Supports planning, sequencing, documentation, and disciplined handoff decisions across multi-step CRM and workflow implementations in portfolio builds.

Verify Google Project Management certificate
03

Google Business Intelligence Professional Certificate

Google / Coursera / 2026

Supports measurement thinking, reporting context, and operational visibility when evaluating how a system should be monitored and improved.

Verify Google Business Intelligence certificate
04

Google AI Professional Certificate

Google / 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

Next step

Read the proof, then bring the messy workflow into focus.

Inspect the portfolio builds for implementation evidence, or start an audit brief when you are ready to clarify where an existing CRM workflow is getting stuck and what should happen next.