Workflow systems designed
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.
Systems built, configured or implemented
Opportunities assessed
Operational trackers, control systems and working tools
SOPs, maps and workflow documents
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.
Operational Clarity Audit
Helps a business investigate workflow problems before investing in automation, AI, reporting, or process changes.
OCA structures discovery evidence, maps work, tracks uncertainty, and frames what to validate or improve before selecting a solution.
View case study →STATUS
CAPABILITIES
EVIDENCE YOU CAN CHECK
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
CAPABILITIES
EVIDENCE YOU CAN CHECK
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
CAPABILITIES
EVIDENCE YOU CAN CHECK
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.
TECHNOLOGY
I choose tools after I understand the work.
The system comes first. The tools are there to support it.
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.
Business Systems Strategist
I diagnose operating problems, design better systems and workflows, and add automation or AI when they actually help.
Workflow & Process Optimization Specialist
I improved workflows, business systems, CRM processes, and reporting from early discovery through build, testing, documentation, and support.
Ecommerce Operations Lead
Ran day-to-day e-commerce operations across inventory, order processing, customer service, supplier coordination, digital marketing and process improvement.
SAP Business Analyst
Worked with SAP Business Intelligence and operational reporting, turning business data into dashboards and reports.
IT Support
Supported day-to-day IT operations, troubleshooting, users and systems.
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.
BEYOND THE RÉSUMÉ
How I tend to make decisions.
Think before acting.
I like to understand the facts, risks, and tradeoffs before I choose a direction.
Look for the pattern underneath.
When something is messy, I break it apart, trace what is connected, and simplify it from there.
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