What is our sales stack

We bias toward a few durable channels that match a GitHub-first, static-site company. Tooling can grow later; lying about it in the handbook cannot.

Default (always on)

• The site: landing pages, Neuro OS demos, docs—what buyers verify before and after calls.
• Email + calendar: proposals, security questions, scheduling.
• Contact and partner routes: explicit next steps for serious inbound.
• GitHub: issues or discussions when work must be tracked with engineering or public OSS context.

Optional (when volume demands it)

• Lightweight CRM or pipeline sheet: only if the team will actually maintain it weekly.
• Note-taking / AI-assisted meeting notes: choose one workflow and stick to it.
• Recorded calls: with consent and a retention policy—if it helps onboarding and handoffs.

Known gaps (honest)

• Formal pipeline analytics and forecasting.
• Dedicated outbound prospecting machinery.
• Deep integrations between “conversation” and “deploy” unless we invest in them deliberately.