Page 1 of 1

Custom Hubspot Implementation (Revops)

1. Customer Journey & Onboarding

What are the exact steps from signup to first successful GPU usage?

Sign up → ? → payment details added → spin up instance → active user(?)

Where do users currently get blocked due to lack of GPU supply?

When should sales step in during the journey?

2. Event Triggers (Core Logic)

Which specific events (product/usage/sales/marketing/etc) should trigger actions?

Are there key conditions or thresholds tied to these triggers?

3. GPU Demand Capture

How should users express interest in specific GPUs besides requesting a quote from the platform?

What should happen after a user expresses interest?

And what type of notifications would you like to send

Can one user request multiple GPU types at once (e.g. A100 + H100), or is it always 1 request per user?

Should users be able to unsubscribe from these notifications?

Should users be able to unsubscribe from these notifications?
A
B

4. GPU Supply Availability

What is the source of truth for GPU availability?

Is it a specific data point? Is this found in postgres?

What defines “available” vs “not available”?

Should availability trigger notifications instantly or in batches?

5. Automation Scope

Which processes should remain manual (for now), and why?

Notifications and quotes will be automated - is there anything you want to keep doing manually?

Should communication be centralized into Hubspot or should emails/notifications partly be sent via product/backend/sendgrid

If split, please specify what you envision

6. Slack Channel Automation

What exact trigger should create a Slack channel?

Is it when a quote is requested?

Should the creation of a slack channel be fully automated or require approval/pre-qualification?

7. Sales Process

When should a deal be created in HubSpot?

What should happen in Hubspot when demand > supply (e.g. email waitlist, notify sales, etc.)

What defines a “won deal”?

Is a won deal directly tied to revenue, or not tied to revenue because of supply constraints?

8. Churn & Customer Success

How do you define churn for non-committed users?

What signals indicate a potential upcoming churn?

What actions have you taken to prevent churn after it was flagged?

What were the results of those efforts?

What are the most common reasons for churn?

Is there any onboarding or support for high-value accounts?

9. Data Model (what we're missing)

What new entities need to be tracked (e.g. GPU requests)?

Would you like to introduce new things to Hubspot to track (like GPU requests, matches, availability), or does this already exist somewhere?

What relationships are required between them?

Should availability trigger notifications instantly or in batches?

10. KPIs & reporting

What are the primary marketing and sales KPIs to track?

What metrics should the product/engineering team be informed about?

What metrics define success (e.g. signups, waitlist, revenue, Slack channels created)

How do you calculate ARR

11. Additional Data Sources

Are there any other data sources besides PostHog and Postgres?

Are there data sources used by the team that are not currently integrated but should be?

12. Segmentation & Tiering

How does tiering impact if and when you engage with users? Should different tiers follow different journeys or automation paths?

We might want to treat high-value users differently
→ e.g. faster routing, different nurture, priority handling, make it possible/impossible to talk to sales/open slack channel

13. Qualification and Disqualification Logic

We know what makes a qualified company, but instead, what makes a user or company disqualified for sales engagement today?

What are common reasons prospects are not a good fit after a conversation?

Should disqualified users be nurtured or re-engaged later?

14. Identify & Account Structure

Can a single user belong to multiple organizations or accounts?

How should users and companies be linked across systems (PostHog, Postgres, HubSpot)?

How do you want to match the same user/company across PostHog, Postgres, HubSpot
(e.g. email, user ID, company ID - what’s leading?) - Very important to get this right

What should be the primary entity for sales and reporting (user vs company)?

15. Historical Data

Do you want historical product data to be migrated into the new structure, or only apply changes moving forward?

Not just product data - all relevant historical data (requests, users, activity, etc.)

How far back does historical data need to be usable/reportable?

Any final notes