---
name: bprm-technical
description: "BPRM tech stack, data model, Slack conventions, and vocabulary — everything needed to work on the Business Partner Relationship Manager without re-explaining from scratch"
metadata: 
  node_type: memory
  type: project
  originSessionId: a7c21f3f-80cb-4099-9fc9-4faecc86bcc5
---

**Tool name:** BPRM (Business Partner Relationship Manager)

## Tech Stack
- **Database:** Google Sheets — ID `15G8kZ64p_61y5NmLm23uP0G2A6lGODHe2isL4OamS0A`
- **Interface:** Slack — channel `#bprm-log`
- **Automation:** Make.com (free tier, ~1,000 ops/month)
- **Intelligence:** Claude API — model `claude-sonnet-4-20250514`

## Slack Commands
| Command | Purpose |
|---|---|
| `Update [partner-id]:` | Log an interaction |
| `New partner:` | Intake a new business partner |
| `Summary [partner-id]` | Generate partner one-pager |
| `Brief [partner-id]` | Pre-meeting brief on demand |
| `Quick [partner-id]:` | Minimal log with follow-up nudge |

Bot responses always start with 🤖 — prevents Make.com automation loops.

## Conventions
- Partner IDs: lowercase hyphenated slugs — e.g. `greenstate-cu`, `metro-health`
- Project IDs: `dcs_[name]` or `bs_[name]`

## Sheet Structure

**Tab 1 — Partners:**
`partner_id, partner_name, sector, status, website, notes_general, origin_type, origin_notes, relationship_vibe, last_interaction_date, created_date`

**Tab 4 — Interactions:**
`interaction_id, partner_id, project_id, date, type, logged_by, summary, sentiment, follow_up_needed, follow_up_notes, source`

## Controlled Vocabulary
- **Relationship vibe:** Thriving · Steady · Cooling · Needs Attention
- **Sentiment:** Positive · Neutral · Negative · Uncertain
- **Five economic sectors:** Financial · BizTech · Engineering · Human Services · Bioscience

## See also
[[project-apex-portfolio]] for the BPRM explainer HTML file (BPRM Master v2.html in /BPRM folder)