Ruben Mendoza
What I buildDelivery

Three systems that remove the manual step.

Each engagement starts with the process that is still running by hand. The tool choice follows the process, not the other way around.

01

Lead & booking systems

Capture, qualify, respond, book and follow up without someone watching the inbox.

GoHighLevelTwilioWebhooksCalendar API

The problem

New enquiries wait, replies are typed by hand, appointments are scheduled manually, and no-shows disappear.

What you get

A lead gets a response in under 60 seconds and the next step is already running.

What I build

  • Webhook intake from forms, ads and landing pages
  • Instant SMS and email response with a booking link
  • Conditional routing by reply, sentiment or stage
  • Reminder cadence and no-show recovery
  • Post-job review request with an exit on engagement
02

Order-to-invoice automation

Take an order from webhook to logged, confirmed, stock-checked and invoiced.

ShopifyMakeGoogle SheetsZohoXero

The problem

Orders are re-keyed into spreadsheets, invoices are typed manually, and duplicate customer records accumulate in the accounting system.

What you get

Five tested order scenarios, zero manual handoffs, and an invoice reference that ties back to the order.

What I build

  • Shopify or form webhook intake
  • Order log in Google Sheets as the running record
  • Customer confirmation through Gmail or SMTP
  • Stock and price check before invoicing
  • Contact resolution before the invoice is created
  • Referenced invoice output with a test log
03

Reconciliation & reporting

Make two or three systems agree, then keep the exceptions out of the report.

PythonSQLExcelGoogle SheetsERP / CRM exports

The problem

Account data lives in different systems, records are matched by hand, mismatches are found late, and the weekly figures are rebuilt from scratch.

What you get

One reviewed ledger, a clear exception queue, and reporting that stays comparable week to week.

What I build

  • Extract and normalise each source into a common schema
  • Match on a stable identifier, with name and address fallback
  • Flag near-duplicates instead of silently merging them
  • Isolate unmatched and conflicting records into a review queue
  • Generate daily and weekly reporting from the reconciled dataset
EngagementHow it runs

Audit, map, build, prove.

No six-month discovery. The first deliverable is a clear read on the process and the exceptions that need a decision.

01

Audit

Walk the current process, find the handoffs and measure where the time actually goes.

02

Map

Define the source of truth, the identifiers, the event flow and the exception paths.

03

Build

Implement the workflows and integrations in the tools the business already uses.

04

Prove

Test the happy path and the ugly cases, then hand over the evidence and the runbook.

Start with the process

Send the process that is still running by hand.

You get a written read on what can be automated, what it would take, and what it removes from the week. No pitch deck required.

Schedule a systems auditOr connect on LinkedIn

rubenjohn6969mendoza@gmail.com