We’re looking for an experienced HubSpot + Stripe specialist to help us finish and validate our Stripe → HubSpot subscription tracking so we can reliably report revenue on deals. Context - We use Stripe for billing (SaaS, self-serve + sales-led deals). - We use HubSpot as our CRM. - A custom “Stripe Subscription” object already exists in HubSpot. - There is partial/legacy server-side sync code that currently writes Stripe fields (plan amount, plan name, subscription status, MRR, etc.) onto the **contact** record, not the custom subscription object. - HubSpot’s native Stripe subscription sync is available but not fully configured/turned on. - We want to avoid breaking existing data, but we’re fine to clean up / backfill if needed. What we need help with 1. Best-practice architecture & plan - Review our current HubSpot + Stripe setup (custom object, existing sync, fields, mappings). - Recommend the cleanest, most maintainable way to: - Keep Stripe as the source of truth. - Map key subscription properties into the **custom subscription object** (MRR, plan name, plan amount, status, billing interval, start date, cancellation date/reason, etc.). - Handle historical backfill and ongoing updates. 2. Implement or fix the Stripe → HubSpot sync - Configure and/or adjust: - HubSpot’s native Stripe subscription sync, or - Our existing custom sync (Node/TypeScript backend) if that’s the better path. - Ensure: - Each Stripe subscription is represented correctly as a subscription object in HubSpot. - Subscriptions are associated with the right contacts and companies. - Historical subscriptions are backfilled as much as is practical. 3. Deal & revenue workflows - Design and implement HubSpot workflows that: - Create or update deals based on subscription events (new subscription, upgrade/downgrade, cancellation, etc.). - Set deal amount (MRR and/or ARR) from the subscription object. - Keep deals in sync when subscription amounts or statuses change. - Set us up so we can: - Attribute revenue to channels/campaigns using existing HubSpot tracking fields (original source, latest source, UTM data). - Calculate basic metrics like LTV and churn in HubSpot (or at least have the fields necessary to do so). 4. Documentation & handoff - Document: - Field mappings (Stripe → HubSpot). - How the sync works. - How the workflows are structured. - Provide guidance on edge cases: - Upgrades/downgrades on the same subscription ID. - Multiple subscriptions per customer. - Self-serve vs. sales-led/custom plans. Nice-to-have experience - Prior projects **specifically** syncing Stripe subscriptions into HubSpot custom objects. - Familiarity with: - HubSpot custom objects & workflows - Revenue attribution and reporting in HubSpot - Stripe’s customer/subscription/invoice models - Basic comfort reading or suggesting changes to backend code (Node/TypeScript) is a plus. What to include in your proposal - Brief description of your relevant HubSpot + Stripe experience. - 1–2 examples of similar projects you’ve done (especially involving HubSpot custom objects + Stripe). - Your recommended high-level approach given the description above. - Estimated hours and rate, plus availability over the next 2–4 weeks.