Description
Summary Description: I have a live revenue operations stack for a manufacturing client and I need an experienced integration developer to stabilize it and finish the last phase. This is not a greenfield build. Everything exists and runs. I need it to run reliably. The pipeline: A sales rep quote PDF arrives by email, Make.com parses it with GPT-4.1, and the extracted data flows into GoHighLevel (CRM), Monday.com (production and finance), and Supabase (database). A rep-facing portal built on Lovable reads from Supabase with row-level security so each firm sees only its own jobs. Scope of work, in this order: GoHighLevel sync audit and fix. Quote records are not populating consistently. Diagnose from run logs, correct field mapping, add a write-back of the Monday item ID to the CRM opportunity so downstream updates target the right record, and tighten the intake filter so non-quote PDFs do not create junk records. Monday.com consolidation and build-out. Merge several fragmented boards into one master board with saved views per role instead of separate boards. Migrate items cleanly, rebuild automations, deduplicate, and add an auto-calculated square footage column populated by the AI extraction step rather than typed by a person. Make.com hardening. Five scenarios exist. They break on bad records and Make disables them silently. Add error handling, filters ahead of lookups, and failure notifications. Export blueprints when done. Required experience: Make.com at an advanced level, including error handlers, iterators, data structures and API modules GoHighLevel workflows, custom fields, pipelines and webhooks Monday.com board architecture, automations, API and data migration Supabase, Postgres and row-level security Working with GPT-based document extraction inside an automation How I work: I built this system and I know it well. I will give you documentation, acceptance criteria for each phase, and direct answers. I expect diagnosis before prescription, evidence from logs rather than guesses, and a flag raised when something contradicts what I have described. No destructive operations without checking with me first. To apply, tell me: A Make.com scenario you stabilized and what was actually causing the failures Your experience syncing GoHighLevel and Monday.com in both directions Your availability over the next two weeks