Merged
Conversation
Added a draft positioning statement for discussion if needed. Updated product positioning to reflect current product names and better clarity. Updated team.
| **PostHog Open Source** is positioned to service hobbyists and very small non-enterprise teams who may want to retain control of their data. | ||
|
|
||
| **Enterprise PostHog** is positioned to solve product analytics problems for larger teams and enterprises. | ||
| **PostHog Free** is positioned to service small non-enterprise teams who need to retain control of their data. |
Contributor
There was a problem hiding this comment.
We're about to rejig these - PostHog Open source and PostHog free are now in practice merged.
- We're currently updating the docs to reflect this change.
- This means they're now used to service 1-3 users in teams that range in size from hobbyists through to small deployments in enterprises. The goal is no matter which size of company and how much scale you have, that you can go into production with our open source product.
Contributor
Author
There was a problem hiding this comment.
Ah, wasn't aware this was so close to merging.
Will we keep the two distinct, or do we plan to merge them into a single product. The simplest offering/naming would seem to be: Open-Source, Scale and Cloud.
Would be good to understand this so I can update the pricing and features copy when needed too.
Contributor
There was a problem hiding this comment.
I didn't think it'd be so fast either, but Team Deployments and Infrastructure is very good :)
They'll definitely like one product, with different config options in the way it gets deployed I imagine.
| **PostHog Free** is positioned to service small non-enterprise teams who need to retain control of their data. | ||
|
|
||
| **PostHog Cloud** is positioned to service clients who need less control. | ||
| **PostHog Scale** is positioned to service large teams and enterprises who need to retain control of their data. |
Contributor
There was a problem hiding this comment.
As per the comment above, PostHog Scale is designed to service teams rather than individuals in scale ups or enterprises that need to collaborate on building a more successful product, without losing control of their data.
| **PostHog Scale** is positioned to service large teams and enterprises who need to retain control of their data. | ||
|
|
||
| **PostHog Self Hosted** is positioned to service clients who need more control. | ||
| **PostHog Cloud** is positioned to service teams of any size who need less control. |
Contributor
There was a problem hiding this comment.
Should we make this more positive?
Generally, PostHog cloud works well with teams that value simplicity - they are less budget conscious or with lower event volumes, who don't need to retain control of their data.
jamesefhawkins
requested changes
Jun 22, 2021
Contributor
jamesefhawkins
left a comment
jamesefhawkins
left a comment
There was a problem hiding this comment.
Decent start, but worth rejigging the Scale / Free positioning in light of (exciting) changes we've just made to the product :)
Update based on comments
corywatilo
added a commit
that referenced
this pull request
Jun 28, 2021
* Automatically update newest blog post on homepage * fixing blog snippet color scheme on homepage * Blog images and updated process (#1514) * add image for Writing for developers post, fix casing in title * product people post image * updated instructions for creating a blog post with an image Co-authored-by: Cory Watilo <[email protected]> * add postimage to Series B post (#1513) Co-authored-by: Cory Watilo <[email protected]> * added james h readme (#1511) * added james h readme * fixed indenting on list * Update contents/handbook/company/team/james-hawkins.md Co-authored-by: Neil Kakkar <[email protected]> * Update Positioning Sections (#1501) * Update Positioning Sections Added a draft positioning statement for discussion if needed. Updated product positioning to reflect current product names and better clarity. Updated team. * Update index.md Update based on comments * Update index.md * Update share-options.md * Clickhouse -> ClickHouse (#1512) Co-authored-by: Cory Watilo <[email protected]> * Update link to compensation from benefits in handbook (#1517) Link wasn't directing to intended route. * Blog post image for customer-support-at-posthog.md (#1520) * [ImgBot] Optimize images (#1522) *Total -- 6,496.52kb -> 5,532.33kb (14.84%) /contents/images/team/Phil.png -- 54.38kb -> 12.19kb (77.59%) /contents/images/plugins/plugin-configuration.png -- 535.72kb -> 260.66kb (51.35%) /contents/images/plugins/geoip-plugin-example.png -- 324.60kb -> 179.65kb (44.66%) /contents/images/plugins/s3-plugin-example.png -- 214.89kb -> 121.64kb (43.4%) /contents/images/plugins/plugin-editor-location.png -- 415.22kb -> 245.34kb (40.91%) /contents/images/plugins/install-plugin-location.png -- 412.97kb -> 252.19kb (38.93%) /contents/images/blog/array/1-26-0.png -- 813.18kb -> 762.76kb (6.2%) /src/components/LandingPage/images/pipes.png -- 12.32kb -> 11.91kb (3.31%) /contents/images/blog/writing-for-developers/writing-for-developers.png -- 477.84kb -> 466.30kb (2.42%) /contents/images/blog/customer-support-at-posthog.jpg -- 3,224.55kb -> 3,208.87kb (0.49%) /src/components/Careers/Transparency/images/feedback.svg -- 5.19kb -> 5.19kb (0.17%) /src/components/Careers/Transparency/images/board-meetings.svg -- 5.65kb -> 5.64kb (0.1%) Signed-off-by: ImgBotApp <[email protected]> Co-authored-by: ImgBotApp <[email protected]> * Update Plugin Docs redirects (#1497) * Changes for feature pages. * Update links on FAQ page (#1529) * Update link to upgrading page from FAQ page * Update link to investors page from FAQ page * HTML (in string) now passable for title and description. Co-authored-by: Cory Watilo <[email protected]> Co-authored-by: Cory Watilo <[email protected]> Co-authored-by: James Hawkins <[email protected]> Co-authored-by: Neil Kakkar <[email protected]> Co-authored-by: Joe Martin <[email protected]> Co-authored-by: Charles Cook <[email protected]> Co-authored-by: Marco Chen <[email protected]> Co-authored-by: Mohammed Shehu <[email protected]> Co-authored-by: imgbot[bot] <31301654+imgbot[bot]@users.noreply.github.com> Co-authored-by: ImgBotApp <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Updates to the positioning section of the handbook. Positioning statement is definitely open to feedback and can be tweaked; will form basis of a messaging framework I'll document next week.
Positioning statements won't be outwardly facing in marketing collateral, obviously. It's mainly for creating alignment and stating vision at a PRM level.
Changes
Added a draft positioning statement for discussion if needed.
Updated product positioning to reflect current product names and better clarity.
Updated team.
Checklist