docs: add design-partner intake and outreach ops

[hudsonaikins]

Summary

• add a public design-partner request issue template to the repo
• add standard outreach message templates and a first evaluator session template
• wire the public intake path into the growth docs and root navigation

Linear

• create INT-281 for the first 3 live outreach loops
• create INT-282 for the first live weekly adoption review

Testing

• git diff --check

Greptile Summary

This PR wires the public design-partner intake path into the repo by adding a GitHub issue template (design_partner_request.yml), three new growth ops docs (design-partner-intake.md updates, outreach-message-templates.md, evaluator-session-template.md), and updating root navigation in README.md, docs/DOCS_INDEX.md, and docs/growth/README.md. All benchmark references in the new template and message templates point to files that exist in the repo, and install commands match the README exactly.

Confidence Score: 5/5

Documentation-only PR with no code changes; safe to merge.

All changes are Markdown and YAML documentation files. The sole finding is a P2 style suggestion (using /tree/ instead of /blob/ in a contact link URL). No logic, security, or data-integrity issues were identified.

No files require special attention.

Important Files Changed

Filename	Overview
.github/ISSUE_TEMPLATE/config.yml	Adds a "Design-partner intake" contact link; uses /tree/main/ path for a file URL (should be /blob/main/).
.github/ISSUE_TEMPLATE/design_partner_request.yml	New issue template with well-structured fields for company, role, decision, revenue shape, benchmark pair, install status, inputs, and success criterion — all consistent with benchmarks present in the repo.
docs/growth/outreach-message-templates.md	New outreach message templates covering cold intro, follow-up, install push, calibration ask, and design-partner commitment; install commands match README exactly.
docs/growth/evaluator-session-template.md	New session template with clear flow for confirm decision → confirm revenue shape → run comparison → test trust → decide next step; well structured.
docs/growth/design-partner-intake.md	Updated intake doc wiring the GitHub issue template as the inbound entry point; content is clear and consistent with the new issue template.
README.md	Adds links to Outreach Message Templates and Evaluator Session Template in the Documentation section; all targets exist.
docs/DOCS_INDEX.md	Mirrors README.md additions — adds links for the two new growth docs; all links resolve correctly.
docs/growth/README.md	Expands the ordered Start Here list to include Design-Partner Intake (step 6), Outreach Message Templates (step 7), and Evaluator Session Template (step 8); sequencing is logical.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Public Evaluator] -->|opens issue| B[GitHub Issue Template\ndesign_partner_request.yml]
    A -->|reads config.yml contact link| C[design-partner-intake.md]
    B --> D{Qualification Check}
    C --> D
    D -->|qualified| E[Outreach Message Templates\nCold/Warm Intro]
    E --> F[Install Push\ncurl or brew]
    F --> G[Evaluator Session Template\nFirst Live Call]
    G --> H{Next Step Decision}
    H -->|not a fit| I[Stop]
    H -->|interested| J[Calibration Ask]
    H -->|committed| K[Design-Partner Loop\nINT-281 / INT-282]
    J --> K

Loading

Prompt To Fix All With AI

This is a comment left during a code review.
Path: .github/ISSUE_TEMPLATE/config.yml
Line: 7

Comment:
**Use `/blob/` not `/tree/` for file links**

The URL uses `/tree/main/` to link directly to a file. GitHub treats this as a tree (directory) path and redirects it, which works but may cause a brief redirect. For direct file links, `/blob/main/` is the canonical form and avoids the redirect.

```suggestion
    url: https://github.com/IntelIP/ProfitCtl/blob/main/docs/growth/design-partner-intake.md
```

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "docs: add design-partner intake and outr..." | Re-trigger Greptile}

Greptile also left 1 inline comment on this PR.

[greptile-apps]

Use /blob/ not /tree/ for file links

The URL uses /tree/main/ to link directly to a file. GitHub treats this as a tree (directory) path and redirects it, which works but may cause a brief redirect. For direct file links, /blob/main/ is the canonical form and avoids the redirect.

Suggested change

	url: https://github.com/IntelIP/ProfitCtl/tree/main/docs/growth/design-partner-intake.md
	url: https://github.com/IntelIP/ProfitCtl/blob/main/docs/growth/design-partner-intake.md

Prompt To Fix With AI

This is a comment left during a code review.
Path: .github/ISSUE_TEMPLATE/config.yml
Line: 7

Comment:
**Use `/blob/` not `/tree/` for file links**

The URL uses `/tree/main/` to link directly to a file. GitHub treats this as a tree (directory) path and redirects it, which works but may cause a brief redirect. For direct file links, `/blob/main/` is the canonical form and avoids the redirect.

```suggestion
    url: https://github.com/IntelIP/ProfitCtl/blob/main/docs/growth/design-partner-intake.md
```

How can I resolve this? If you propose a fix, please make it concise.