The one problem underneath all three.

I'm Omar Quesada, founder of Pockets Full Systems.

For five-plus years I've worked inside Salesforce orgs, usually as the only technical resource in the room. That's a specific kind of education. When there's nobody to hand a problem to, you learn every layer of it: the flow that fires, the data underneath it, the person upstream who forgot, and the customer downstream who paid for the forgetting.

And you learn something else: sales problems, support problems, and ops problems are usually the same problem wearing different job titles — work that depends on memory instead of a system. A lead waiting in an unwatched queue and an assessment trapped in a PDF are the same leak. The tooling changes. The leak doesn't.

That's the company's whole thesis, and its name. The money is already in your business — it's leaking out through the gaps in your processes. My job is to close the gaps so your pockets stay full. (Yes, that's where the name comes from.)

How I work

Find the gap. Build the catch. Hand it back running. The longer version is on the home page, but the part I'd underline is the third step: everything I build is documented, tested, and maintainable by your own team. The nightly job in my case studies runs on a flow the client's own admin maintains. You shouldn't need me twice for the same leak — a consultant who engineers his own permanence into your org has built you a new leak.

The stack

Deepest: Salesforce — Service Cloud above all, plus Flows, Apex, LWC, Agentforce and AgentScript, Experience Cloud, and Nonprofit Cloud.

Around it: Make.com, n8n, Zapier, Airtable, and REST/SOAP integrations — because half of every leak lives outside Salesforce, in the connection that was never built.

Certifications: Agentforce Specialist · Salesforce Certified Administrator · Platform App Builder · Platform Developer I · Service Cloud Consultant.

Beyond the three case studies: a case-management layer for a nonprofit that turned assessments into reportable records against an 11,700-record catalog, with HIPAA-conscious data masking — and a delegated-access portal where a third party sees exactly the billing items they're allowed to see, with access enforced in code, not in a training document. Different industries, same shape: decide who should see what and when, then make the system enforce it instead of a person.

The practical details

Based in Orlando, Florida. I work in English and Spanish — including orgs where the team operates in both at once. Solo by design: the person you talk to on the first call is the person who builds the system and the person who answers for it after.