Full-Stack Developer Needed — WordPress/Elementor + Pipedrive API Integration

Hi there, I looked through your post carefully. This is not a forms project. It's an authentication, matching, and state management problem wearing a planning portal's clothes. The hard part is not collecting data. It's making sure client ABC who logs in sees their specific event, updates fields in their exact Pipedrive deal without creating duplicates, can return a week later and pick up where they left off, and none of that breaks when a deal ID changes or someone enters bad data. I've built WordPress portals like this before, including one for Lousch Creations LLC (a $7,000 custom BuddyBoss portal where different user types accessed gated content and saw only their own data) and another for Universal Metro (a $5,275 site with restricted workflows and role-based access). The pattern is the same: authenticate the user, match them to the correct backend record, read and write data cleanly, handle errors without exposing the system, and log everything so you can troubleshoot when something feels off. For your system, here's how I'd build it: 1. Client authentication layer using WordPress user accounts tied to Pipedrive deal or person IDs. Each client gets a unique login. On login, the system fetches their deal ID from Pipedrive and loads their event data into the form. 2. Form state saved to WordPress custom post types as a local cache. When a client submits or updates a form, data writes to Pipedrive via REST API and simultaneously saves locally. That way if the API call fails, you have a record and can retry without losing their work. 3. Pipedrive API integration with proper error handling. I'll authenticate using API tokens, map your custom fields, write updates to existing deals without creating duplicates (using deal ID matching), validate all inputs before submission, and log every transaction. 4. Return-user flow so clients can log back in, see their saved progress, and update answers. The system checks Pipedrive for the latest data on page load and reconciles any differences. 5. Security and validation at every layer. No exposed API keys, sanitized inputs, rate limiting on API calls, and role-based access so clients only see their own data. I've worked with CRM APIs before (HubSpot, Salesforce, Zoho), and while I haven't touched Pipedrive's API specifically, the structure is consistent across platforms. I'll need a day to read their documentation and test in a sandbox, but the logic you need is standard: authenticate, query by identifier, update fields, handle errors. A few questions so I can scope this properly: What user data do you already have in Pipedrive that we can use to match clients to their deals (email, deal ID, custom field)? How many types of planning forms are you starting with, and roughly how many fields per form? Do clients need to upload files (photos, contracts, etc.) or is this purely text and dropdown data? Should clients be able to see a summary of all their submitted information in one place, or just edit individual forms? Do you have a staging or test Pipedrive account I can use during development? In terms of pricing, this feels like a $7,000 to $9,000 build depending on form complexity and how many edge cases we need to handle. I can work hourly at $85/hr or structure it as milestones once we define scope. If this direction feels right, send over API documentation access or a Pipedrive sandbox login and I'll map out a detailed build plan with timeline. Trust, Tai