Current State
60+ workflows plus a 73-route, 19-table CRM.
Project
UYSP
Outreach automation and client management portal — converting leads to meetings with built-in compliance and operator visibility
An AI BDR that works the top of the funnel.
AI BDRCRMCampaign managerClient work
The Problem
What problem was worth solving?
I build things to solve a specific pain, not to decorate a portfolio. This is the pressure that made this project necessary.
UYSP needed to convert high volumes of coaching leads into qualified meetings without hiring a proportional sales team.
The outreach system had to be compliance-safe (geographic restrictions, business hours, opt-out handling) while still running enrichment, sequencing, and meeting booking automatically.
Client teams also needed a dedicated management portal for campaign visibility, performance tracking, and operational control.
The Build
What I built around the problem
Two integrated systems delivered as one client engagement: (1) an outreach engine with 46 automated workflows handling lead enrichment, compliant sequencing, engagement tracking, and meeting booking, and (2) a client management portal with 73 API endpoints for campaign operations and performance visibility.
Outreach automation
46 automated workflows
Full pipeline: lead intake, data enrichment, outreach sequencing, compliance checks, engagement tracking, and monitoring.
Architecture
Three-pillar system
Each platform has a clear role: Airtable manages lead state, Clay handles data enrichment, Azure orchestrates the workflow execution.
Client portal
73 API endpoints · full management system
A complete campaign management portal with 36K+ lines of code and 9 database tables — built as part of the same client engagement.
Operational reliability
160+ versioned backups
Every workflow is version-controlled and backed up — production operations are recoverable and auditable.
Reality Check
Current boundary
The point is not to pretend the work was clean. This is what the project taught, where it changed shape, or where the boundary still matters.
01
What this page should do
This page should explain why the project mattered without turning unfinished, private, or earlier work into a bigger claim than the public record supports.
02
Status
UYSP is currently represented as built and running. The useful parts of the story are kept visible, but the page should stay clear about what is current and what is history.
03
Boundary
The public version should stay specific, plain-spoken, and careful about what is still being built.
Value
What changed because it existed
This is the practical value of the work. Where a project is unfinished, shelved, or still changing, the value is tied to what it actually taught.
Compliance
Geographic + timing + opt-out enforcement
Messages only go to US/Canada contacts during business hours with automatic opt-out handling — compliance rules encoded directly into the automation.
Testing
Built-in A/B testing
Configurable variant assignment and sequence controls let teams test different outreach approaches and measure what works.
Performance tracking
End-to-end engagement visibility
Message delivery, link clicks, and meeting bookings tracked and fed back into lead state — operators see exactly what is working.
Delivery scope
Outreach engine + management portal in one engagement
Not just automations — a complete system spanning outreach workflows and application-grade management tooling for the client team.
Technical Layer
How the system is built
This is the implementation behind the work: the architecture choices, integrations, controls, and workflow decisions that made the project real enough to learn from.
Azure Logic Apps
Airtable
Clay
SimpleTexting
Switchy.io
Calendly
Slack
OpenAI / Claude
Client management portal
PostgreSQL + API layer
Build Story
How the thinking unfolded
This is the reasoning path behind the output, not only the finished artifact.
01
Built around what the client already uses
Instead of forcing a platform migration, the system was engineered around the client's existing tools (Airtable, Kajabi, Clay) with reliable automation connecting everything.
02
Compliance is logic, not a policy document
Geographic restrictions, business hours, and opt-out handling are encoded directly into the automation — unsafe messages are blocked by design, not by policy.
03
From automation to full management system
The engagement expanded beyond outreach automation into a complete client portal with campaign management, performance tracking, and team visibility.
Decision Logic
SMS Eligibility Formula
Where it matters, the project includes explicit rules and operational constraints rather than hand-wavy intent.
AND(
{Phone Valid},
OR(SEARCH("united states", LOWER({Location Country})), SEARCH("canada", LOWER({Location Country}))),
{HRQ Status} != "Archive",
NOT({Current Coaching Client}),
NOT({SMS Stop}),
NOT({Booked})
)
Evidence
What this project shows
This evidence is strongest when it is tied to specific work rather than broad claims.
Client Delivery
Delivered and operated a live production system for a fast-scaling coaching company — from design through ongoing operations.
Compliance Engineering
Geographic restrictions, timing rules, and opt-out handling encoded directly into the automation — compliance enforced by design.
Automation Architecture
Coordinated 46 workflows across lead intake, enrichment, outreach sequencing, compliance, and monitoring.
Full-Stack Product Engineering
Built a complete client portal with 73 API endpoints for campaign management, performance tracking, and operational visibility.
Continue
Want to go deeper?
Ask the Latif AI Guide about the architecture, the commercial logic, or the hard lessons behind this project.