SYSTEMS BEFORE TOOLS

Understand the work. Design the system. Implement with control.

I look at how the work is really done, find where it breaks, then build a better way to run it.

DELIVERY EVIDENCE

What I have worked on.

These ranges come from work I have designed, built, reviewed, and documented.

01
WORKFLOW DESIGN

Workflow systems designed

15–25
02
IMPLEMENTATION

Systems built, configured or implemented

~5
03
AUTOMATION ASSESSMENT

Opportunities assessed

50+
04
BUSINESS SYSTEMS

Operational trackers, control systems and working tools

10–15
05
DOCUMENTATION

SOPs, maps and workflow documents

20–30

These ranges come from documented work. Some projects appear in more than one category, so the numbers should not be added together.

01 · SELECTED WORK

Systems built around real work problems.

Selected examples of how I find the problem, design a better way to work, and build it with clear checks.

COMMERCIAL SYSTEMS

02 / 03

Lead-to-Client System

Helps a business keep leads from getting lost between inquiry, qualification, follow-up, sales, and client handoff.

I built LCS to follow a lead from first inquiry to client handoff, keep the owner and next step clear, prevent missed or duplicate actions, and send uncertain decisions to a person instead of letting the workflow guess.

View case study →

STATUS

WORKING SYSTEMRUNTIME TESTED

CAPABILITIES

Commercial Systems DesignWorkflow DesignFact-Based Review

EVIDENCE YOU CAN CHECK

01 Lead-to-Client Snapshot 02 Working lead-response + CRM flow 03 Failure recovery + test results

OPERATIONS CONTROL

03 / 03

Operations Control System

Makes overdue, failed, blocked, or unowned work visible, gives it a clear owner, and keeps escalation, recovery, and closure under control.

I built OCS for operational problems that should not disappear between tools and people. It takes problems such as overdue work, a failed workflow, a missed handoff, or a missing owner and gives them a clear owner, acknowledgement, escalation path, recovery path, closure, and history.

View case study →

STATUS

WORKING SYSTEMTESTED · RELEASE VERIFIED

CAPABILITIES

Operational Control DesignWorkflow ArchitectureSystems Integration

EVIDENCE YOU CAN CHECK

01 Problem → owner → closure 02 Escalation + recovery path 03 70 checks + 10/10 release test

HOW I WORK

How I turn an unclear problem into a working system.

I choose the tools after I understand the work.

01UNDERSTANDWork · information · ownership
02DIAGNOSEEvidence · exceptions · failure points
03DESIGNWorkflow · rules · architecture
04IMPLEMENTSystem · integration · automation · AI
05VALIDATEBehavior · failures · controls
06DOCUMENTSOPs · handoff · guidance
07IMPROVEMonitor · learn · refine

02 · CAPABILITIES

How I take a messy problem and turn it into a working system.

I use these skills together. I first understand the problem, then build the right system, test it, and make sure people can use it.

The systems shown beside each step are examples of where I use these skills in real work.

01

UNDERSTAND + DECIDE

See what is really happening before changing anything.

I look at the work, the facts, and where things get stuck. Then I decide what needs attention first.

CAPABILITIES

Operational Diagnosis · Business Systems Design

02

DESIGN + IMPLEMENT

Turn the problem into a clear system people can use.

I set the steps, owners, handoffs, tools, and rules. I add automation or AI only when it helps.

CAPABILITIES

Workflow Design · CRM Implementation · AI & Automation Implementation · Systems Integration

03

CONTROL + HAND OFF

Make sure the system works, can recover, and is easy to hand over.

I test what can go wrong, set clear limits, and write down how the system should be used and maintained.

CAPABILITIES

Validation & Controls · Documentation & Handoff

03 · SYSTEMS LIBRARY

Systems I can reuse when the same kind of problem shows up again.

These are working approaches I can adjust for a new business instead of starting from zero every time.

Opportunity Fit Review Lead Qualification & Client Routing AI-Assisted Review with Human Approval Approved Company Knowledge System Find the Problem → Set the Priority Decision + Outcome Tracking Operational Problems → Ownership → Closure
Explore Systems Library →

TECHNOLOGY

I choose tools after I understand the work.

The system comes first. The tools are there to support it.

Automation & Workflown8n · Make · Zapier
CRM & Sales SystemsHubSpot CRM · GoHighLevel · Salesforce · Zoho
AI & IntegrationOpenAI / ChatGPT · Claude · Gemini · REST APIs · Webhooks · JSON · Google Apps Script
Business SystemsGoogle Workspace · Notion · Airtable · ClickUp · Slack · Asana · LarkSuite · Monday.com · Trello
Analytics & ReportingPower BI · Tableau · Google Sheets
Technical LiteracyBasic SQL · Python · HTML · CSS · JavaScript

PROFESSIONAL EXPERIENCE

The systems work comes from years of hands-on operations experience.

I have worked across IT support, reporting, business operations, process improvement, business intelligence, and systems strategy.

2026 → PRESENT
VELZENITH

Business Systems Strategist

I diagnose operating problems, design better systems and workflows, and add automation or AI when they actually help.

2022 → 2026
OLAVIN CORP.

Workflow & Process Optimization Specialist

I improved workflows, business systems, CRM processes, and reporting from early discovery through build, testing, documentation, and support.

2014 → 2022
DEZENITH

Ecommerce Operations Lead

Ran day-to-day e-commerce operations across inventory, order processing, customer service, supplier coordination, digital marketing and process improvement.

2013 → 2014
FASTTRACK SOLUTIONS INC.

SAP Business Analyst

Worked with SAP Business Intelligence and operational reporting, turning business data into dashboards and reports.

2010 → 2013
AXIS GLOBAL TECHNOLOGIES

IT Support

Supported day-to-day IT operations, troubleshooting, users and systems.

Portrait of Rael Ferrer

04 · ABOUT

I like to understand the work before I try to improve it.

I'm Israelito Ferrer, known professionally as Rael. I work on business systems, workflow improvement, automation, and AI implementation.

A lot of the problems I work on look like tool problems at first. I usually find the real issue in ownership, handoffs, information, or decisions.

01Systems before toolsUnderstand the problem before deciding what to build or automate.
02Evidence before certaintySeparate what we know from what we assume and what still needs checking.
03Implementation with controlTest what we build, plan for failure, document it, and make sure someone can maintain it.

BEYOND THE RÉSUMÉ

How I tend to make decisions.

01

Think before acting.

I like to understand the facts, risks, and tradeoffs before I choose a direction.

02

Look for the pattern underneath.

When something is messy, I break it apart, trace what is connected, and simplify it from there.

03

Remember the people using the system.

A process can be technically correct and still fail if it does not work for the people expected to use it.

05 · CONTACT

Need a clearer way to run the work?

01
Professional opportunity Hiring for business systems, workflow, automation or AI implementation work.
Discuss opportunity →