contact sales form updates

[camerondeleone]

Proposing the following changes, open to ideas.

Add:

• Explicit product selector with:
  • PostHog self-serve (usage based pricing)
  • PostHog Teams add on ($450/month + usage)
  • PostHog Enterprise (starts at $20K/yr)
  • (or ideally these map to the exact options on the plans page but those are still confusing to me and I don't think map well to how sales talks about the product)
• Which data warehouse do you use?
  • Snowflake
  • BigQuery
  • Redshift
  • Azure
  • Other (describe below)
  • None

Remove:

• name fields (ask for email + company only). I don’t think we get much asking for either way it since:
  • anyone findable will be able to look this up from clearbit et al
  • anyone we qualify will give it to us anyway. And it’s fine to say ‘hi there’ in initial emails etc
  • Or we could consider validation on work email only? People do use burner emails for this but tend to be slightly less serious when doing so. Don't feel so strongly on this.
• Why are you reaching out (multi select) -> This is basically useless in terms of qualifying and we can collect it over email or on a call.

Change:

• Anything else you want to know should be changed explicitly to "what do you want to talk about on the call?" and be required
• "Do you need any of the following" can change to only two options (multi select, or ideally two checkboxes):
  • Legal/security review
  • BAA for HIPAA

[minekansu]

name fields (ask for email + company only). I don’t think we get much asking for either way it since:

last name is a requirement in salesforce to create a lead or a contact (and there is no way to change this requirement) so I prefer keeping these fields to keep our data clean unless we think they cause real friction

[minekansu]

Explicit product selector with: PostHog self-serve (usage based pricing) PostHog Teams add on ($450/month + usage) PostHog Enterprise (starts at $20K/yr) (or ideally these map to the exact options on the plans page but those are still confusing to me and I don't think map well to how sales talks about the product)

Do we intentionally want to keep Teams as a plan instead of an add on in our conversations?

Plans, products, and addons are now explicitly separate on our website so it makes sense to keep the fields parallel in contact sales form. We can do the following:

1. modify existing product question to include Teams Add On so it reads like this:

Which products are you interested in?

• Product Analytics
• Session Replay
• A/B Testing
• Feature Flags
• Web Analytics
• Surveys
• Data Warehouse
• CDP
• Add on: Teams
• Add on: Group Analytics
• Add on: Data Pipelines

2. Add plan question

Which plan are you interested in?

• Totally Free (Usage capped at free tier limits)
• Ridiculously Cheap (self serve, with usage-based pricing)
• Enterprise Mode ($20K/yr minimum spend)

[simfish85]

With these Teams/Enterprise and product selectors what are we trying to achieve? What routing decisions would we make based on seeing these?

(I want to keep it as simple as possible whilst giving us enough to make the hands-on/self-serve call)

[camerondeleone]

Thinking this through again I agree simple is best. I do not think we get good data from long selectors. So listing every single possible configuration/product is a bad idea imo. I think it should be:

• Analytics
• A/B Testing (Feature Flags)
• Session Replay
• Other (CDP, Data Warehouse, Surveys)

I'm also pretty strongly against the Totally Free / Ridiculously Cheap / Enterprise Mode language (wish it would disappear from the website, but I get why it doesn't) so definitely do not want to use this in the form (do others disagree?). Don't like it because I can't point to the pricing page during a call and say "these are the plans" because the things that are actually there don't map to the options I've given them on the call (which are self-serve/usage-based or Enterprise, which starts at $20K). And the distinction between Plan and Add on also required explaining, so let's just avoid where possible.

[minekansu]

perfect taking out plan question + addon options then 👍 I am hesitant to combine unrelated products under Other as it won't be super useful data for lead qualification or for analysis, maybe there is a ui solution to the long list issue

[camerondeleone]

perfect taking out plan question + addon options then 👍 I am hesitant to combine unrelated products under Other as it won't be super useful data for lead qualification or for analysis, maybe there is a ui solution to the long list issue

I hear you. I put them together because they aren't really commercially viable right now (beta, very low $, not a separate product), so from a commercial point they are actually somewhat disqualifying if checked in isolation.