jcds/systems

Work / 01–06

MNL · SG · QLD

Selected work.

Revenue systems, AI infrastructure, and applications I help ship. From the first customer signal to the software behind the next decision.

01 / ChiefAI-Officer · product engineering

Scaling Up Platform v2

A workshop and assessment platform connecting demand generation, coach workflows, and participant reporting.

Organization projectWorkshop + assessment platform
  1. 01Campaign
  2. 02Assessment
  3. 03Responses
  4. 04Coach report
  5. 05Workshop
Context
Coaches and operators needed one place to deliver workshops, manage assessments, and turn responses into usable reports.
My role
Contributing engineer · ChiefAIOfficer.com
System
A Next.js and TypeScript application with assessment templates, public campaigns, coach reports, workshop assets, and release controls.
Evidence boundary
Public repository and commits under jcbdelo26 document contributions to report pagination, group-report access, workshop image uploads, and promotion workflows.
  • Next.js
  • TypeScript
  • React
  • Prisma
  • Vercel
  • React PDF

02 / GTM engineering

ChiefAIOfficer revenue system

Helped ChiefAIOfficer grow from bootstrap to consistent $118K bottom-line revenue through website detection, speed-to-lead, and sales nurturing systems.

Project outcome$118K bottom-line revenue
  1. 01Intent
  2. 02Qualification
  3. 03First touch
  4. 04Human follow-up
Context
Website activity, qualification, and follow-up lived in separate parts of the revenue process.
My role
GTM Engineer
System
Website Lead Detection paired with GoHighLevel speed-to-lead email automation and signal-aware follow-up.
Evidence boundary
Connected website intent, rapid follow-up, and ongoing sales nurturing to support consistent revenue. Outcome supplied by Joshua Delos Santos.
  • GoHighLevel
  • lead detection
  • lifecycle automation
  • email operations

03 / Agentic systems · DevOps

HITL OS

A local-first operating environment that gives agents one knowledge layer and humans explicit control.

Project outcomeOne operating surface
  1. 01Operator
  2. 02Gateway
  3. 03Agent
  4. 04Read-only knowledge
Context
Agent execution, persistent business context, messaging access, and operational verification were fragmented.
My role
Founder · system operator
System
A unified WSL runtime connecting a local dashboard, Hermes agent, Telegram gateway, and read-only Vault retrieval through QMD.
Evidence boundary
Documented architecture with live runtime checks; private paths and authentication details are intentionally omitted.
  • WSL2
  • Hermes
  • QMD
  • Obsidian
  • Telegram
  • Bun

04 / Development operations

Governed GoHighLevel operator platform

A local automation control plane where plans, approvals, effects, and evidence stay separate.

Project outcomeLocal platform complete
  1. 01Intent
  2. 02Plan
  3. 03Approval
  4. 04Effect
  5. 05Evidence
Context
CRM automation needed a safe path from intent to provider action without hiding authority, ambiguity, or recovery decisions.
My role
System designer · operator
System
Blueprints, provider contracts, approval envelopes, inert execution, independent observation, reconciliation, recovery, and redacted receipts.
Evidence boundary
OPR-01 recorded 170/170 tests. This is local synthetic evidence—not a claim of live-provider or production readiness.
  • Python
  • JSON Schema
  • SQLite
  • REST
  • MCP
  • supervised UI

05 / GTM automation

Nonagon production system

Productized outbound, content, proposal, and lead-intake systems for a B2B production agency.

Project outcome₱16K → ₱56K MRR
  1. 01Signal
  2. 02Content
  3. 03Conversation
  4. 04Proposal
Context
The agency needed a repeatable acquisition and proposal operating system rather than isolated campaign work.
My role
HITL systems builder
System
LinkedIn outbound, Growth Clips generation, proposal generation, and voice-led intake connected as one delivery surface.
Evidence boundary
Agency outcome in the cleared evidence record; separate end-client work reached a six-figure MRR top-of-funnel.
  • LinkedIn outbound
  • content automation
  • proposal systems
  • voice intake

06 / GTM automation

Legacy Production outbound engine

Automated personalized video outreach and short-form top-of-funnel production.

Project outcome₱50K → ₱92.5K MRR
  1. 01Account
  2. 02Insight
  3. 03Video
  4. 04Conversation
Context
High-context outbound video was valuable but too manual to operate as a repeatable growth channel.
My role
HITL systems builder
System
A Loom-style outbound-video workflow and short-clip production system with repeatable personalization.
Evidence boundary
Three-month outcome in the cleared HITL public evidence record.
  • video automation
  • personalization
  • outbound operations
  • content systems

Built with ChiefAI-Officer.

Organization ↗

Contributing to Scaling Up Platform v2, the organization’s public workshop and assessment application. A closer look at the features I’ve worked on:

Assessment reporting

Report pagination, authored content, and public assessment presentation.

View contribution ↗

Coach workflows

Five Dysfunctions group reports with team responses and respondent averages.

View contribution ↗
More on GitHub · @jcbdelo26 ↗

Need this range inside one role?

I work best where GTM decisions must survive technical implementation.

Start a conversation

Go to