Description
Summary I am building Leadpie (leadpie.nl), a B2B sales tool (Dutch market) that sends physical gifts to prospects and stalled deals, and measures the impact through each customer's own HubSpot account. Every customer connects their own HubSpot portal via OAuth, and every one of them has organized it differently: different pipelines, different stage names, different ways of logging meetings and calls, sometimes different custom properties. That's the actual problem we need solved. Our dashboard shows metrics like: Sent / Response / Meeting / Closed-won as a funnel (with conversion rate per step) Meeting rate Pipeline value and closed-won value (in the portal's home currency) ROI multiplier Number of gifts sent Every one of these needs to map correctly to HubSpot data regardless of how a given customer's portal is set up. We already have a foundation: a per-org pipeline cache that flattens stage metadata (closed/open/probability flags) instead of relying on stage names, and an attribution model that anchors on the send date and only counts deals/meetings that happen after it. What we don't have solved is a robust, general way to detect "was there a meaningful meeting" and "did the deal close" after a gift was sent, across portals where meetings and calls get logged inconsistently (or not at all). I have made a start with this project using Claude Code but I would like to have someone briefly go through it and make it scalable. I am not looking for someone who just wires up the HubSpot API and calls it done. I need someone who has actually run into this kind of cross-portal variability before and can talk through, concretely, how they'd handle it. Ideas I want to explore with you: * A short onboarding questionnaire or first-run detection flow when a customer connects their HubSpot, so we know upfront which pipeline(s) to use, how their team logs meetings/calls, and which properties actually hold the data we need * A fallback strategy for portals where meetings/calls aren't logged reliably * How to keep this maintainable as we onboard more customers, rather than special-casing each one What I need from you: * Solid experience with the HubSpot API (OAuth apps, not legacy private apps), specifically deals, pipelines, engagements/meetings/calls, and associations * Experience integrating HubSpot into a multi-tenant SaaS product where you couldn't assume a fixed portal structure * Stack: Next.js/TypeScript, Prisma/Postgres, HubSpot OAuth already implemented and working for one portal structure; this project is about making it robust across arbitrary structures. Website: leadpie.nl