docs: package design-partner growth assets#37
Merged
Conversation
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
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.
Summary
Linear
Testing
Greptile Summary
This PR packages three new growth assets: a
benchmark-outreach-pack.mdthat maps each benchmark pair to a single evaluator question and lead metric, updated links in the rootREADME.mdanddocs/DOCS_INDEX.mdsurfacing the new doc, and a clarification indesign-partner-target-list-template.mddirecting users to keep named target accounts in a private system (Linear/internal sheet) now that the repo is public. All referenced benchmark scenario files and report files exist in the repository.Confidence Score: 5/5
Safe to merge — documentation-only changes with no functional code impact.
All five changed files are Markdown docs. All referenced benchmark scenario YML files and report files exist in the repository, all internal links resolve correctly, and the privacy guidance added to the target list template is appropriate for a newly public repo. No P0 or P1 findings.
No files require special attention.
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A[Identify Evaluator] --> B[Choose One Benchmark Pair] B --> C1[Pack 1: Open-Core Packaging\nlead metric: recurring margin] B --> C2[Pack 2: Pilot vs Steady State\nlead metric: operating margin] B --> C3[Pack 3: Covenant Safety\nlead metric: covenant status] C1 --> D[Send one report or one command] C2 --> D C3 --> D D --> E[State lead metric first] E --> F{Evaluator finds it useful?} F -- Yes --> G[Offer to run their own scenario\nvia profitctl compare] F -- No --> H[Revisit benchmark pair choice] G --> I[Design-Partner Pipeline\ntracked privately in Linear]Reviews (1): Last reviewed commit: "docs: package design-partner growth asse..." | Re-trigger Greptile