Partnership-as-OS only works if people can operate it. This is the human layer: who we've worked with, how, and what we're doing to make every team member a builder.
Over 9+ months, we've worked with every layer of Made's organization. Each person has shaped the system differently.
Architectural counterpart since day one. Building Made's RAG, knowledge graph, harness layer, and agentic fleet in parallel. This isn't "BioCreative builds, Made uses" — it's two engineering teams on complementary systems with an explicit bridge.
80% design-first approach. Building Made's proposal generation system. BioCreative provides database access patterns and harness reference. Dustin directs the design.
Drove the ISCT campaign from planning to execution. Her needs shaped the Campaign Tracker: which metrics matter, how follow-ups surface, what a "warm" signal looks like in practice.
Shaped Made Minimal into something the commercial team uses daily. One of the first working through the Academy Starter Git — connecting GitHub to Claude Projects and asking the right questions.
First team member fully embedded from day one. Didn't inherit a legacy workflow — started with Made Minimal, automation, and AI messaging as default tools. Test case for how quickly a new rep becomes productive.
The outbound engine runs on these people. Each has a HeyReach sender account with territory-specific campaigns. They don't need to understand the backend. They see campaigns, follow-ups, and engagement signals in Made Minimal.
| Sender | Territory | Targets |
|---|---|---|
| Chathuranga | East C-Level | 245 (Discovery → Phase I) |
| Adam | East VP+Director | 225 (Discovery → Phase II) |
| Karen | West All Seniority | 272 (Preclinical → Phase II) |
| Simona | Active sender | Latest campaign stats |
Commercial development — proposals, pricing, partnership structures. Connected via Monday.com sync and Salesforce pipeline visibility.
5 Made academy_users registered. Designed to scale — new team members and GC Corp portfolio companies get the same structured onboarding.
A GitHub repository designed to be dropped into Claude Projects (or any AI IDE). The repo is the context. Your job is to chat with it.
From there, Claude guides you through: creating your own CLAUDE.md, filling in a SOUL document (voice, brand, working style), setting up a free Supabase database, connecting free API accounts (Brave Search, Firecrawl, Gemini), and building skills that combine these tools.
By the end: a working mini-project with backend, modular context, your SOUL document, image generation, and web research.
"LLMs like Claude are static. They don't get smarter on their own — they get more powerful based on the context you give them. We've contextually engineered a starter project for you. The whole kit is the context. Your job is to chat with it."
— Brian Elbert, May 11, 2026
The human layer that makes the tech layer work:
This isn't a contractor delivering artifacts and disappearing. It's a continuous engagement where Brian is embedded in Made's workflow — attending planning sessions, troubleshooting bugs live, building what the team needs in real time.
The endgame isn't "Brian builds systems and Made uses them." It's:
Every team member up-skilled as a contextual engineer within their segment, all reading from the same methodology and structure.
| Person | What "Builder" Means for Them |
|---|---|
| Greg | Generate outreach, adjust targeting, query the database — without filing a request |
| Lucy | Build segments, review enrichment quality, adjust strategy — with data, not intuition |
| Melody | Shape the UX, test features, build AI workflows with Claude Projects |
| Joe | Extend architecture, add data domains, build harnesses — with reference patterns |
| Dustin | Build the proposal generator using the same tools and DB patterns — independently |
The Academy + Starter Git pattern isn't specific to Made. New team members → same path. GC Corp portfolio companies → same Starter Git, different SOUL document, different database. The first deployment is Made. The pattern is universal.