Follow-up Boss Automation and Integrations Expert Needed

Summary I'm a mortgage company sales manager building a performance-based lead pool routing system in Follow Up Boss. My account is migrated to Automations 2.0 (drag-and-drop canvas). I need an expert to build a multi-flow automation system that routes internet leads through three pools (Shark Tank, Piranha, Guppy) based on lead age and activity, with protection windows and stale-lead recycling. The full build specification is documented below. This is not exploratory work — the logic is defined, decisions are made, edge cases are mapped. I need someone who can execute cleanly in the 2.0 canvas. REQUIRED EXPERIENCE You must have: - Demonstrated experience building in Follow Up Boss Automations 2.0 specifically (not just 1.0). 2.0 went into full release October 2025. If your FUB experience is pre-2025, that's not what I need. - Examples or screenshots of multi-flow automation systems you've built in FUB (redact client info) - Experience with branching logic, multi-trigger automations, custom field updates, and Run Automation chaining - Comfortable with conditional waits and exit conditions Bonus: - Mortgage or real estate industry experience - Experience integrating FUB with dialers, AI call scoring, or LOS systems In your proposal, please include: 1. One specific multi-flow FUB 2.0 build you've completed (description, not necessarily screenshots) 2. Your answer to this technical question: In Automations 2.0, how would you implement a "wait 30 days, but exit early if a custom date/time field hasn't been updated in the last 30 days" pattern? Walk me through your approach. 3. Your fixed quote with estimated hours Proposals that don't address all three will be ignored. BUILD SCOPE 5 automation flows, ~12-15 automation objects total, plus supporting custom fields and tags. System Overview: Internet leads enter Shark Tank pond, age through Piranha and Guppy pools by time (if uncontacted), and recycle by inactivity (if stale). Protected leads are exempt from recycling. Contacted leads exit aging but continue to recycle. Definitions: - Meaningful activity: logged call over 30 seconds, outbound text/email by an LO (not automation), inbound text/call/email from lead, or stage change past "New" - Contacted: first occurrence of meaningful activity → triggers Status:Contacted tag - Protection: manually applied tags (PROTECTED_14D, PROTECTED_30D, PROTECTED_90D) that block recycling in all pools Custom Fields to Create: - LastTouch (date/time) - Protection_Expires (date) - OriginalLeadDate (date) - AICallScore_Monthly (number) Tags to Create (exact strings, case-sensitive): ACTIVE_SHARK, ACTIVE_PIRANHA, ACTIVE_GUPPY, PROTECTED_14D, PROTECTED_30D, PROTECTED_90D, STALE_24H, STALE_7D, RECYCLED_TO_PIRANHA, RECYCLED_TO_GUPPY, HOT_PREAPPROVAL, BUYING_30D, BUYING_60D, BUYING_90D, Status:Contacted, Protection_Lost_Inactivity Flow 1 — Lead Entry + Aging Conveyor: Trigger on New Inquiry from internet Lead Flow sources. Reassign to Shark Tank, tag ACTIVE_SHARK, set LastTouch and OriginalLeadDate, run Shark Tank cadence stub. Wait 7 days, branch on (stage New AND no Status:Contacted AND no PROTECTED_*) → demote to Piranha. Wait 23 days, same branch → demote to Guppy. Flow 2 — Meaningful Activity Heartbeat: Multi-trigger on all meaningful activity events. Action: update LastTouch to current timestamp. Foundation automation. Flow 3 — Stale Recycling (3 sub-automations): 3a Shark Tank: trigger ACTIVE_SHARK added, wait 48hrs, recycle to Piranha if stale and unprotected. 3b Piranha: same pattern, 7-day wait, recycle to Guppy. 3c Guppy: same pattern, 14-day wait, strip LO assignment. Flow 4 — Contact Stops Aging: Multi-trigger on first meaningful activity. Add Status:Contacted, exit Flow 1's aging path. Must NOT cancel Flow 3 recycling. Flow 5 — Protection Lifecycle (3 sub-automations): 5a 14-day: simple wait + tag removal. 5b 30-day: wait 30 days OR exit early if LastTouch is over 30 days old. If exit fires, add Protection_Lost_Inactivity. 5c 90-day: three sequential 30-day windows with inner activity checks. Hard cap at 90 days. Cadence Stub Automations: Three empty placeholder automations (one per pool) for a separate cadence vendor to fill in later. Flow 1 references them via Run Automation steps. DELIVERABLES 1. All 5 flows built in my live Follow Up Boss account (admin access granted for engagement duration) 2. All automations left INACTIVE at handoff — I activate them in QA sequence 3. Build documentation: written record of every object created, flags/limitations encountered, decisions on edge cases 4. QA support: walk me through testing on a test lead source with 5 fake leads 5. Production cutover support: rename test ponds/sources to production names, activate flows in correct order BUILD PROCESS - Build against test ponds (TEST_SharkTank, TEST_Piranha, TEST_Guppy) and test lead source (TEST_Source) first. I'll create these before you start. - All automations remain INACTIVE during build - Build order: custom fields → tags → cadence stubs → Flow 2 → Flow 5 → Flow 3 → Flow 4 → Flow 1 - Flag 2.0 capability limitations you encounter (especially: wait-with-exit-condition support, unassigned reassignment support, canceling another automation on a contact) - Screenshot each completed automation for the build doc NOT IN SCOPE - Cadence content (emails, texts, scripts) — separate vendor - Performance-tier access enforcement — manual sales manager process - Speed-to-lead automation (FUB's First Response Time report handles this) - Integrations to dialers, LOS, or BI tools COMMUNICATION - Slack or Loom updates daily during build - One 30-min kickoff call to align - Available on Zoom for QA walkthrough at handoff - Pacific time zone preferred WHAT I'LL FILTER OUT - Generic FUB consultants with no 2.0 specifics - Proposals that don't answer the technical question above - "I'll figure out 2.0 as I go" — find a different project - Pricing without estimated hours