Product led sales Q1 2026 goals #14192
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
simfish85
left a comment
simfish85
left a comment
There was a problem hiding this comment.
Quite a lot of these aren't measurable i.e. instead of
Explore creating ways...
it should be
Document a new approach for...
So I'd encourage you to re-read these and reframe them as something we can measure/know we have achieved.
Also you need to add revenue goals which are table stakes for TAMs:
- Hit quota targets (All TAMs)
- Hit the overall team revenue goal (Landon, Tyler, Simon)
Updated objectives to refine language and clarify tasks.
simfish85
left a comment
simfish85
left a comment
There was a problem hiding this comment.
Added some suggestions/comments where I don't understand what you're trying to achieve!
| - Create Use-case playbooks to document and guide on selling or advising specific use-cases for cross-sell (Jon+Ryan) | ||
| - Document and automate early signals and ranking accounts for prioritization (and checking accuracy at the end of the quarter) (Sachin) | ||
| - Create training program more formally for customers (Sachin+Ryan) | ||
| - Create a feature request gatherer process, especially to have a cohesive story and impact product planning (James) |
There was a problem hiding this comment.
Is this to improve the existing process or something automated? If it's automated based on signals or similar I'm concerned that it'll become a dumping ground and hard to make actionable come quarterly planning time.
There was a problem hiding this comment.
@simfish85 can't tell which item you highlighted here. was this in reference to the "signals" or the "feature requests" I can see how this would be a dumping ground for feature requests and we should avoid that. i think what this will come down to is formalizing a "voice of the customer" process so that concrete product narratives for use-cases are delivered from TAM -> Product.
For "early signals" this will likely just tap into "indicators" in Vitally with hopefully new indicators surfacing
There was a problem hiding this comment.
Oh yeah this is for the feature request one above - just wondering how it's different to what we have today.
Co-authored-by: Simon Fisher <simon@posthog.com>
Co-authored-by: Simon Fisher <simon@posthog.com>
Co-authored-by: Simon Fisher <simon@posthog.com>
Removed the BAU engaging other teams goal.
Changes
Please describe.
Add screenshots or screen recordings for visual / UI-focused changes.
Checklist
vercel.jsonArticle checklist