Automation Revamp for Tech Support Platform
Budget: $30 – $250 USD
Title
Build & Fix Make.com + Twilio + AI Automation System (Revenue-Critical – Must Provide Proof)
Description
We are AGeekOnDemand (AGOD), a multi-city tech support company operating in Orlando, Boston, and Phoenix.
We are rebuilding our automation infrastructure and need a senior-level automation engineer who can execute quickly, validate work, and eliminate silent failures.
This is not a beginner role.
Core Problem
Our current system has fragmented automation across Make.com scenarios, unreliable webhook handling, SMS and call routing inconsistencies, no deterministic lead tracking, and lack of validation, logging, and monitoring.
We are moving to a deterministic, production-grade system where no automation runs without state validation, all actions are logged, and failures are immediately visible.
Current Stack
Make.com for automation
Twilio for SMS and voice (replacing OpenPhone)
Bland.ai for AI voice calls
Setmore for scheduling
Square for payments and webhooks
Google Sheets as the system of record
Scope of Work
Audit and fix existing Make.com scenarios. Identify broken or inefficient flows, reduce unnecessary operations, and eliminate duplicate triggers and race conditions.
Implement a canonical lead state system in Google Sheets. Every lead must have a unique ID. All actions must reference that state. No outbound action is allowed without validation.
Ensure webhook and API reliability. Webhooks must trigger correctly, return expected payloads, and handle retries or safe failures.
Fix and standardize SMS and call routing through Twilio, including inbound SMS, outbound SMS, and AI call triggers via Bland.ai.
Implement monitoring and logging. All flows must have error logging, execution logs, and failure alerts. If something breaks, it must be immediately visible.
Optimize costs by reducing Make.com operations usage where possible and identifying wasteful automation patterns.
Definition of Done
Work is not complete until it is validated in production, logs or screenshots are provided showing successful execution, failure scenarios are tested, and no regressions are introduced. This follows our internal workflow requirements
Required Proof Before Hiring
Provide an example of a Make.com system you built. Explain how you handle webhook reliability, prevent duplicate triggers, and log failures. A Loom walkthrough is preferred.
No proof means no response.
Rules
No vague estimates. No unfinished work labeled as complete. No undocumented changes. No surprise invoices.
All work must be tied to defined tasks, documented, and verifiable.
Engagement Structure
Start with a small paid test task of two to four hours. If successful, continue with ongoing weekly work.
We prioritize speed, accuracy, and reliability over theory.
Ideal Candidate
Strong experience with Make.com and complex scenarios. Deep understanding of webhook-based systems. Experience with Twilio APIs. Experience implementing logging and monitoring. Thinks in systems, not scripts.
Bonus
Experience with AI voice tools such as Bland.ai. Experience building lead pipelines or CRM systems. Experience reducing automation costs.
To Apply
Start your proposal with AGOD SYSTEMS.
Then answer the following. What is the number one reason automations fail silently. How would you prevent duplicate SMS sends. Show an example of a system you built.
Build & Fix Make.com + Twilio + AI Automation System (Revenue-Critical – Must Provide Proof)
Description
We are AGeekOnDemand (AGOD), a multi-city tech support company operating in Orlando, Boston, and Phoenix.
We are rebuilding our automation infrastructure and need a senior-level automation engineer who can execute quickly, validate work, and eliminate silent failures.
This is not a beginner role.
Core Problem
Our current system has fragmented automation across Make.com scenarios, unreliable webhook handling, SMS and call routing inconsistencies, no deterministic lead tracking, and lack of validation, logging, and monitoring.
We are moving to a deterministic, production-grade system where no automation runs without state validation, all actions are logged, and failures are immediately visible.
Current Stack
Make.com for automation
Twilio for SMS and voice (replacing OpenPhone)
Bland.ai for AI voice calls
Setmore for scheduling
Square for payments and webhooks
Google Sheets as the system of record
Scope of Work
Audit and fix existing Make.com scenarios. Identify broken or inefficient flows, reduce unnecessary operations, and eliminate duplicate triggers and race conditions.
Implement a canonical lead state system in Google Sheets. Every lead must have a unique ID. All actions must reference that state. No outbound action is allowed without validation.
Ensure webhook and API reliability. Webhooks must trigger correctly, return expected payloads, and handle retries or safe failures.
Fix and standardize SMS and call routing through Twilio, including inbound SMS, outbound SMS, and AI call triggers via Bland.ai.
Implement monitoring and logging. All flows must have error logging, execution logs, and failure alerts. If something breaks, it must be immediately visible.
Optimize costs by reducing Make.com operations usage where possible and identifying wasteful automation patterns.
Definition of Done
Work is not complete until it is validated in production, logs or screenshots are provided showing successful execution, failure scenarios are tested, and no regressions are introduced. This follows our internal workflow requirements
Required Proof Before Hiring
Provide an example of a Make.com system you built. Explain how you handle webhook reliability, prevent duplicate triggers, and log failures. A Loom walkthrough is preferred.
No proof means no response.
Rules
No vague estimates. No unfinished work labeled as complete. No undocumented changes. No surprise invoices.
All work must be tied to defined tasks, documented, and verifiable.
Engagement Structure
Start with a small paid test task of two to four hours. If successful, continue with ongoing weekly work.
We prioritize speed, accuracy, and reliability over theory.
Ideal Candidate
Strong experience with Make.com and complex scenarios. Deep understanding of webhook-based systems. Experience with Twilio APIs. Experience implementing logging and monitoring. Thinks in systems, not scripts.
Bonus
Experience with AI voice tools such as Bland.ai. Experience building lead pipelines or CRM systems. Experience reducing automation costs.
To Apply
Start your proposal with AGOD SYSTEMS.
Then answer the following. What is the number one reason automations fail silently. How would you prevent duplicate SMS sends. Show an example of a system you built.