Skip to main content

Agentic AI / RevOps / Google Cloud / Business Automation

I build AI-orchestrated business systems for sales and operations.

I connect CRM, automation, AI agents, Google Cloud tools, dashboards, approvals, and backend workflows into infrastructure teams can run, inspect, and improve.

From lead capture to human approval queues, every handoff should be visible, traceable, and easier to improve.

NVIDIA Developer Program member - Google Developer Program member - Based in the Philippines, building for global teams.

AI RevOps and Business Infrastructure

A short walkthrough on connecting CRM, AI, automation, approvals, and reporting

TALKING HEAD

Watch the training first, then inspect the portfolio

Demand needs a system

JD SYS

AI-orchestrated revenue workflow, from signal to manager view.
01
The Real Problem

The issue is not just demand. It is disconnected infrastructure.

Customer signals already move through Facebook, Messenger, Viber, calls, walk-ins, referrals, websites, ads, events, salespeople, CRM records, support tickets, API events, orders, and bookings. The real problem is what happens when CRM records, AI drafts, automation triggers, and human handoffs are not connected.

If the system cannot show who owns the next step, what AI proposed, what changed, and what needs approval, the operation is guessing.

Messy system

JD SYS

What breaks when CRM, AI, tools, and handoffs are disconnected.
01

AI drafts, CRM records, and workflow triggers sit in different places with no clear operating view.

02

Teams cannot see which handoffs are human-owned, automated, waiting, or blocked.

03

Agents respond too early when context, timing, and approval rules are not designed.

04

Reports depend on manual checking instead of logs, events, dashboards, and source-to-outcome traces.

05

Customer work moves across tools, but the system does not explain what changed or why.

06

Leaders cannot tell if the problem is acquisition, routing, AI quality, follow-up, fulfillment, or infrastructure.

02
Who This Is For

Built for teams that need AI support without losing control.

This is for employers, operators, RevOps teams, and builders who need AI-assisted workflows tied to real CRM logic, automation, dashboards, and human approval.

Buyer fit

JD SYS

For teams that need AI-assisted work with human control.

Hiring Teams

You need someone who can connect AI workflow logic, CRM operations, automation, dashboards, and business-facing product work.

RevOps Teams

You need cleaner pipeline movement, source tracking, handoff rules, automation recovery paths, and manager visibility.

AI Operators

You need human-in-the-loop queues, approval states, prompt context, agent routing, and traceable AI-assisted work.

Founders And Builders

You need practical infrastructure that connects real customers, tools, data, and workflows without pretending AI fixes weak operations.

Industry Systems

Common places where the operating system gets messy.

The industry changes the modules. The core job stays the same: make the work after the inquiry, order, or booking clear enough for the team to run.

Retail proof

JD SYS

The Vape Shop admin dashboard showing branch, product, sales, and sync operating metrics.
The Vape Shop branch POS cashier screen with product grid and stock badges.

Branch POS

The Vape Shop checkout flow with branch selection and customer order details.

Checkout flow

01 / The Vape Shop OS

02 / Omnichannel customer and order view

03 / POS and Shopify operating flow

04 / Inventory and fulfillment tracking

Storefront, POS, inventory, and admin proof from The Vape Shop OS.

Unified Commerce Systems

Retail & Commerce

For stores, distributors, and commerce teams that need sales, inventory, fulfillment, channels, and reporting to stop living in separate places.

Proof: The Vape Shop

View Industry System

CRM proof

JD SYS

Fastrack Money Success GoHighLevel workflow map showing CRM automation paths.
SolarOps rooftop assessment proof for solar lead qualification.

SolarOps

The System dashboard proof for AI-assisted revenue operations.

The System

01 / Sales pipelines

02 / CRM workspace

03 / Fastrack GHL workflows

04 / SolarOps pre-sales assessment

GHL workflows, SolarOps assessment, and AI revenue system proof.

CRM + Revenue Operations

Service Businesses

For service businesses where leads come in from calls, referrals, ads, Messenger, websites, or salespeople, then need booking, follow-up, routing, and clear manager views.

Proof: Fastrack Money Success, The System, SolarOps

View Industry System

Booking proof

JD SYS

Real Estate Revenue Architecture listings home proof showing property discovery flow.
Real Estate Revenue Architecture listing detail proof showing property inquiry context.

Listing detail

01 / Reservations

02 / Availability tracking

03 / Real Estate Revenue Architecture

04 / Guest CRM

Real estate revenue architecture proof for listing and buyer-lead workflows.

Booking Operations Infrastructure

Hospitality & Bookings

For hospitality, accommodation, venues, and booking-led operators that need reservations, availability, guest CRM, retention, and concierge work to be easier to manage.

Proof: Real Estate Revenue Architecture

View Industry System

AI ops proof

JD SYS

Sagad OS command center showing queue health, SLA risk, approval load, pod coverage, and channel readiness.
Sagad OS attention queue showing review worklist, confidence, priority, and attempts.

Attention queue

Sagad OS conversation review showing draft reply, AI decision trail, knowledge context, and QA compliance gate.

Review surface

01 / Sagad OS

02 / AI draft review

03 / Human-in-the-loop approvals

04 / Queue and SLA visibility

Sagad OS preview proof for AI-assisted queues, approvals, QA context, and handoff work.

AI Operations Infrastructure

AI BPO / Call Center

For BPO teams, call centers, appointment setters, and support-led sales teams that need AI-assisted queues, approval workflows, QA context, escalation visibility, and cleaner handoffs.

Proof: Sagad OS

View Industry System

The Tech

Tools I use to build AI-orchestrated CRM, automation, Google Cloud, search visibility, dashboards, and business-facing apps.

AI Orchestration

Agent workflow boundaries, retrieval context, approval queues, and prompt observability.

OpenAIClaudeLangChainLangGraphLangSmithRAGPrompt systemsNVIDIA Developer Program

CRM & RevOps

Pipeline movement, follow-up logic, source visibility, and manager handoff.

GoHighLevelGHL WorkflowsHubSpot future-useSalesforce future-useSlackPostHog

Google Cloud & Search

Search visibility, analytics, maps, cloud infrastructure, storage, data, and AI paths.

Google Developer ProgramGoogle Search ConsoleGoogle Analytics 4Google Tag ManagerGoogle SheetsGoogle Maps APIsGoogle Compute EngineCloud RunCloud StorageBigQueryGemini / Vertex AI

Automation & APIs

Tool connections, event handoffs, structured triggers, retries, and recovery paths.

n8nZapierMakeREST APIsWebhooksTrigger.devPostman

Business Apps & Delivery

Operator dashboards, admin views, data apps, deployment paths, and business-facing tools.

ReactNext.jsTypeScriptSupabasePostgreSQLVercelDockerGitHubCloudflare Workers
03
Global Delivery

Based in the Philippines. Building for global teams.

I work remote-first with teams that need AI, CRM, automation, Google tooling, dashboards, and backend workflows to be clearer, more traceable, and easier to improve.

Global delivery

JD SYS

Based in the Philippines. Building for global teams.

Philippines Origin

I am based in the Philippines. The work is built for remote collaboration and global delivery.

Global Teams

Remote-friendly AI, CRM, Google Cloud, automation, dashboard, and business-app infrastructure for teams outside the local market.

04
The System

A modern business system is the layer between signals, AI, and action.

It captures the signal, routes the work, gives AI controlled context, keeps humans in the loop, syncs the tools, and shows the team what happened. The tools can change. The job is always the same: make the workflow visible and reliable.

After awareness

JD SYS

Capture, route, orchestrate, approve, sync, report.

Module 01

Capture Signals

Bring leads, customer updates, orders, tickets, CRM events, or manual entries into a reliable intake path.

Module 02

Route The Work

Make ownership, priority, next action, and escalation rules clear before automation moves anything forward.

Module 03

Orchestrate Agents

Use prompts, tools, retrieval context, workflow timing, and guardrails to support the work without losing control.

Module 04

Approve Risk

Keep humans in the loop for low-confidence replies, customer risk, tool actions, escalations, and sensitive handoffs.

Module 05

Sync The Stack

Connect CRM, spreadsheets, APIs, webhooks, Google tools, dashboards, and backend workflows around the same operating path.

Module 06

Observe And Report

Give teams a clear view of what moved, what stalled, what AI did, what humans approved, and what needs attention.

05
Before And After

From scattered updates to clear next steps.

Before and after

JD SYS

From opaque tools to traceable operating paths.

Before

  • CRM data, chat threads, AI drafts, spreadsheets, and reports scattered across tools
  • No clear owner for customer handoffs
  • AI responses without reliable approval or timing rules
  • Manual checking to understand what changed
  • No trace from source to outcome
  • Managers guess whether the issue is sales, support, AI, or infrastructure

After

  • Every signal captured into an inspectable workflow
  • Every customer, record, or task routed to an owner
  • AI draft, confidence, context, and approval state visible
  • CRM, automation, and Google tools synced around the same path
  • Logs and dashboards show what moved or stalled
  • Leaders see the operating system behind the customer workflow
06
How I Build It

Map first. Build second.

I do not start by forcing an AI tool. I start by mapping how records, customers, approvals, tools, and handoffs move, then build the smallest reliable infrastructure around the real workflow.

Lead-to-sale chain

JD SYS

Map the workflow before adding agents.

Step 01

Workflow Map

I map how customers, records, messages, tools, and handoffs currently move through the business.

Step 02

Infrastructure Map

I design the CRM model, automation events, AI boundaries, approval states, dashboard views, and cloud paths.

Step 03

Agent Boundary

I define what AI can draft, what it can route, what needs human approval, and what must stay logged.

Step 04

Build And Sync

I connect CRM, APIs, Google tools, databases, dashboards, and automation workflows into one operating path.

Step 05

Observe And Improve

We use logs, reports, review queues, and operator feedback to improve reliability after real work moves through it.

07
Ways To Work

Custom builds for different levels of AI and operations complexity.

Every build depends on the CRM, channels, approval rules, data sources, Google tools, team structure, automation paths, and where AI is allowed to help. This is infrastructure work, not a generic software setup.

Portfolio Proof

JD SYS

Start with portfolio proof before booking a review.

Portfolio Proof

For hiring managers, employers, recruiters, or clients who need to inspect CRM, AI workflow, automation, cloud, and business app proof.

  • CRM workflow proof
  • AI orchestration and handoff proof
  • Retail OS and dashboard proof
  • Google and business app proof

AI RevOps Build

JD SYS

Three paths: proof, build, infrastructure review.

AI RevOps Build

For teams that need CRM, automation, AI approval queues, Google Cloud paths, dashboards, and backend workflows connected.

  • CRM and pipeline architecture
  • AI draft and approval workflows
  • n8n, API, and webhook orchestration
  • Google Cloud and search tooling
  • Dashboard and reporting views

Infrastructure Review

JD SYS

Infrastructure review for messy AI, CRM, and automation paths.

Infrastructure Review

For teams with tools already in place, but unclear AI behavior, weak reporting, broken handoffs, or fragile automation.

  • CRM and automation cleanup
  • Agent workflow boundary review
  • Approval and escalation mapping
  • Source, event, and log tracking
  • Manager and operator visibility
08
Not For Everyone

This is not another cheap software setup.

Not a fit

  • Only wants AI hype without workflow discipline
  • No real customer, sales, support, or operations process
  • No clear owner for approvals or escalations
  • Refuses to log decisions, handoffs, or tool actions
  • Only needs posting, boosting, or surface-level content
  • Expects agents to fix weak demand or a weak offer

Good fit

  • Teams that want AI support with human control
  • RevOps leaders who want clearer handoffs
  • Builders who need CRM, APIs, dashboards, and automations connected
  • Operators willing to improve the system behind the workflow
  • Companies that value inspectable infrastructure over generic subscriptions
09
FAQ

Common questions before you start

Global teams that already get inquiries, orders, bookings, or customer requests and need cleaner CRM, AI workflow, follow-up, approvals, reporting, and operating visibility.
Yes. This works best when demand is already coming in. The problem I fix is what happens after the inquiry, order, booking, or customer request arrives.
This is not a fit if you have no active demand, no clear offer, no person responsible for the work, or no willingness to track follow-up, sales, fulfillment, and reporting activity.
CRM is part of it, but not the whole thing. I build around how leads, customers, AI-assisted steps, approvals, follow-up, fulfillment, dashboards, and reports actually move.
That is common. The first step is to map where work currently lives, then build a cleaner system for capture, ownership, follow-up, booking, commerce, fulfillment, and sales updates.

Portfolio

Inspect the systems before we talk.

Start with the proof. The portfolio shows CRM, automation, AI workflow, Google tooling, commerce, dashboard, and business app builds before you decide whether to reach out.