Operations & Automation

I build backend systems that run your business without you.

20 years old. Completely self-taught. I use AI and no-code platforms to architect, direct, and QA every build. I break problems down to a level where the tools can execute, then I piece the system together and make sure it actually works.

That's the skill. Not coding. Thinking through how a business runs and turning that into something that runs itself.

I pick up new software fast. If a client's stack runs on something I haven't touched before, I'll learn it well enough to automate it - or tell you straight up if it can't be automated well. Every tool and platform listed here, I taught myself through building real things. No courses, no bootcamp, no degree in this.

Tools I've worked with
n8n GoHighLevel REISift / DataSift Google Sheets Google Drive Google Maps API Google Forms Gmail API Airtable Notion Trello Slack Telegram Shopify Stripe Cloudflare Pages Playwright DeepSeek Claude API OpenRouter rss.app Hostinger VPS
Client Project

Chris Buys Houses - Full Operations Backend

Real estate investor. 15 workflows. ~60-70 hours of build time.

Chris needed his lead management tool (DataSift) to talk to his sales CRM (GoHighLevel) in both directions. When a lead's status changed in one system, the other had to update automatically. Tags, pipeline stages, sold status, attempt tracking - all of it.

  • Two-way sync between REISift/DataSift and GoHighLevel
  • Automated lead tagging across two priority tiers with overlap dedup
  • Pipeline stage sync (attempts, dispositions, sold status) flowing both directions
  • Token manager for API authentication refresh
  • Internal Slack notifications on key pipeline events
  • Bulk status update handler for batch operations
This wasn't one workflow. It was 15 interconnected pieces that had to stay in sync without breaking each other.
Chris Buys Houses - Back-Office System diagram
Fully functional workflows I built as demonstrations. Real APIs, real data routing, real AI processing. Not mockups.
Demo Build

Client Onboarding Automation

Google Form submission triggers the entire client setup process.

A new client fills out an intake form. From there, everything happens automatically:

  • Creates a project folder structure in Google Drive
  • Spins up a Trello card with a pre-built checklist
  • Sends a branded HTML welcome email to the client
  • Logs the onboarding event to Google Sheets
  • Posts a summary to the team's Slack channel
  • Error handling on every external node so nothing fails silently
One form submission. Five systems updated. Zero manual work.
Client Onboarding Engine diagram
Demo Build

Shopify Custom Order Intake

AI reads order notes, creates production tasks, confirms with the buyer.

Built for a custom product shop (demo brand: "Timber & Thread Co."). When a Shopify order comes in with customization details buried in the order notes field:

  • DeepSeek AI extracts the specs (size, material, color, engraving text, whatever the customer typed)
  • Creates a structured production task in Airtable with all specs broken out
  • Sends a branded HTML confirmation email to the buyer with their customization details listed back to them
The hard part isn't the routing. It's getting AI to reliably parse freeform customer text into structured fields that a production team can actually use.
Custom Order Intake diagram
Demo Build

Revision Request Tracker

Watches inbox for client revision requests. Logs, prioritizes, and alerts.

Monitors a Gmail inbox for emails that look like revision requests. When one comes in:

  • AI parses the email to extract what the client wants changed, which project it's for, and how urgent it is
  • Logs it to Google Sheets with all fields structured
  • If the AI flags it as urgent, fires a Telegram ping to the project owner immediately
  • Sends an acknowledgment email back to the client so they know it was received
The AI classification is the key piece - it has to distinguish "hey just checking in" from "this needs to be fixed before our launch tomorrow."
Client Revision System diagram
Demo Build

Inbox to CRM Pipeline

Email comes in. If it matters, it hits Notion with context. If it doesn't, it gets filtered out.

Not every email deserves CRM attention. This workflow:

  • Watches Gmail for new messages
  • Filters out marketing, newsletters, and noise automatically
  • Runs the remaining emails through DeepSeek to extract sender, intent, urgency, and relevant details
  • Creates a structured entry in Notion with all that context
  • Posts a clean summary to Slack so the owner can scan it without opening email
The filtering is what makes this useful. Without it, you're just dumping every email into a CRM and making more noise, not less.
Inbox to CRM Pipeline diagram
Demo Build

Lead Triage System

Inbound form submission gets scored by AI before anyone touches it.

When a lead comes in through any web form:

  • Normalizes the form data regardless of which form platform sent it
  • DeepSeek scores the lead on quality (budget signals, urgency, fit)
  • Logs to Google Sheets with the score and reasoning
  • Fires a Slack alert with the score so the sales person knows whether to prioritize it or let it sit
Saves the first 5-10 minutes of every inbound lead that would otherwise go to manual review.
Lead Triage diagram
I run an automation agency. These are the internal systems I built to run it. They're not demo projects - they run daily in production.
Production System

Cold Outreach Engine

7+ workflows. Runs daily.

A Google Maps scraper feeds prospect data into a two-account Gmail outreach system with automated follow-ups. The whole pipeline runs on its own.

  • Google Maps scraper pulls business data by niche and location - a free alternative to paid lead databases
  • AI writes each cold email from scratch based on the prospect's business - no templates
  • Two Gmail accounts with staggered send windows (cold: 8-10am, FU1: 10am-12pm, FU2: 12-2pm)
  • Cross-account dedup so the same prospect never gets emailed twice
  • Row-level tracking in Google Sheets (even rows = Account A, odd = Account B)
  • Bad email format detection and auto-skip
  • Five rotating templates per follow-up stage
Passive Lead Generation Engine diagram
Production System

Facebook Lead Scout

4+ workflows. Runs continuously.

Passively monitors 20 Facebook groups for potential clients:

  • RSS scanner watches all 20 groups on a loop
  • AI classifier reads every post and decides GO, MAYBE, or SKIP based on buying signals
  • Dedup sheet so no lead gets surfaced twice
  • Telegram alerts on every GO with context and the direct link to the post
The classifier prompt alone went through 10+ iterations to cut false positives from ~90% down to a usable rate. Runs in the background while I work on other things.
AI Lead Scout Engine diagram
I don't write code.

I use Claude (AI) as my build tool - and I'm transparent about that because it doesn't change what gets delivered. What I bring is the part no AI can do on its own:

Spot the leak
Look at how a business actually runs and find where time and money are draining out.
Design the system
Break it down into inputs and outputs across whatever tools the business already uses.
Learn fast
If it's new software, I'll dig into docs, APIs, and limitations before touching a single node.
Direct with precision
Every build gets directed with enough specificity that the AI executes it right the first time.
QA everything
Catch edge cases, stress-test it, iterate until it holds up in production.
Own the lifecycle
Scoping, building, testing, deploying, monitoring, and fixing what breaks at 2am.

Everything here was self-taught. No formal training, no bootcamp. I've built 50+ production workflows across n8n, connecting tools like Shopify, Gmail, Google Sheets, Airtable, Notion, Trello, Slack, Telegram, GoHighLevel, REISift, and multiple AI APIs.

Three ways to work together.
1

Revenue-share partnership.

You're an agency owner or consultant with clients who need automation built. You bring the relationships, I build the backend. We split revenue on a fair cut. You don't need to understand n8n - that's my side.

2

Remote ops or automation role.

Part-time or full-time. If your business has manual processes eating hours, I'll turn them into systems. I work best when someone says "here's the problem" and I come back with the thing that fixes it.

3

Hire me directly for a build.

Need something automated? Email me at Joseph@zeitra.ai or visit zeitra.ai to fill out the intake form and see pricing. Scoped, quoted, and built through my agency.

I'm not looking for a title. I'm looking for work that actually uses what I'm good at, with people who move fast and don't need me sitting in a chair from 9 to 5 to prove I'm working.

Let's talk about what you need built.

Email me, watch the walkthroughs, or check out the agency.