Pipedrive CRM Overhaul: Label Inheritance, Lead Source Tracking & Sales Status Setup

Pipedrive CRM Overhaul: Label Inheritance, Lead Source Tracking & Sales Status Setup About the Project Envision Horizons is a growing agency using Pipedrive as our primary CRM. We need an experienced Pipedrive specialist to help us overhaul our backend data structure so we can accurately track lead source for marketing and account/deal status for sales, without our reps doing manual double-entry. This is a multi-workstream project. We have a detailed requirements document ready to share and are looking for someone who can audit our current setup, propose a clean architecture, build it, and deploy to production. --- Scope of Work (Dependent On Your Audit) 1. Label Inheritance (Cross-Entity Field Sync) Organization-level labels ("Target 100," "Current Customer," "Past Customer") need to automatically propagate to any linked Deals, Contacts (People), and Leads when they are created — and stay in sync if the org label changes. Native Pipedrive automations cannot do this, so a Zapier and/or API-based solution is required. - Create mirrored Boolean custom fields on Organizations, Deals, People, and Leads - Build Zapier automations to copy org field values on new record creation - Build cascade automation when org status changes - Run one-time bulk sync to apply tags to all existing records 2. Lead Source Tracking We need a standardized Lead Source field (dropdown) on Leads and Deals, wired up to all our entry points: - Website / inbound forms - Outbound / cold outreach - Referrals - Events / trade shows - Paid ads Contractor will audit all pipeline entry points and ensure Lead Source is captured at the point of entry, not retroactively. 3. Sales Status Tracking Add a Deal Status custom field (separate from pipeline stage) with a defined picklist, plus automations to set status on key stage transitions. Deliverables - Audit doc of current Pipedrive setup before any changes - All custom fields created and configured across entity types - Zapier automations built and tested - Bulk backfill of existing records - Full documentation of everything built (field definitions, automation flows) - Training brief for sales team Requirements - 3+ years hands-on Pipedrive configuration (Pipedrive certification a plus) - Proven Zapier experience with multi-step, conditional logic - Familiarity with Pipedrive API (for bulk sync) - Strong documentation habits — we need to own and maintain what you build - Please share examples of similar Pipedrive builds in your proposal To Apply In your proposal, please address: 1. How you would handle cross-entity label inheritance (labels vs. custom fields, Zapier vs. API) 2. Whether you'd use Zapier, Make, or a custom script, and why 3. Estimated hours broken down by phase 4. Any relevant experience / examples of a similar Pipedrive project Project Structure We'd like to run this in phases: - Phase 1: Audit & design (flat fee) - Phase 2: Build & test (milestone) - Phase 3: Production deployment + bulk sync (milestone) - Phase 4: Documentation & handoff Budget is open to the right person. Quality and documentation matter more than speed. Thank you!