![[Their company]](logo.svg){kind=logo}
[Their company] OS · the projectNew since 2026-11-27: [The project outline]
Before we meet
Before we meet, here is why we asked for the call, how we'd like to run it, and what we'd like to learn from you.
Why we're meeting
[What we know of them, from the Gold Sheet's initial read, in two or three lines.]
The call
Who we are
[The method in four layers, in their market's words: the foundation, the skills and tools, the agents, the operating system.]
When we meet
Where this goes from here
New since 2026-11-27: [The project outline]
On our call, we'll find out whether there's an opportunity to work together. If there is, this page fills in as we go: the scope, the timeline and the goals, shaped with you, and a proposal to review if we get there. Everything we work through along the way feeds the build, so if we go ahead, your system stands up quickly.
After our first call
After our second call
[The route we chose together]
[Why this route, in their words]
| The Foundation | [Medium] |
|---|---|
| Outbound | [Small] |
| Marketing | added after the first three months |
The build-along and the Academy come with every size.
Our proposal
[What we'd build together over the first three months]
| The Foundation | [Medium] |
|---|---|
| Outbound | [Small] |
| Marketing | added after the first three months |
The build-along and the Academy come with every size.
When you're ready, tell us on our thread and we'll open the signing. Accepting here records your intent; the SOW is what you sign.
Agreeing the details
| 2026-11-27 | [What changed] [Why, and who asked] |
|---|
The project
[What we're building, from the SOW]
| [Month 1][Dates] | [What it delivers] |
|---|---|
| [Month 2][Dates] | [What it delivers] |
| [Month 3][Dates] | [What it delivers] |
| Your side | Our side | |
|---|---|---|
| [The decider] | [Their name] | Brian Elbert |
| [Day to day] | [Their name] | [Our lead] |
Prepared by BioCreative Strategies for [Their company] · 2026-11-06
BioCreative builds each company its own AI operating system on one standard: the foundation first, your context and a well-structured database, then the skills and tools, the agents and the screens, and the system that runs them. This page shows that system for [Their company]: your market, your buyers, your words.
LLMs are the new processor. As they improve, a system built this way improves with them, without being rebuilt. On its own, the model knows nothing about your business. It works on your knowledge, not its own. Each piece of work gets the model that fits it: a yes or a no, a small model; sort and tag, a fast model; write and reason, a stronger model.
Our standardized method lays the foundation first, your context and your data, and from it we grow your AI operating system to your needs, each layer built on the one below.
We've built the BioCreative OS many times over. We drop it in as your foundation, then customize it with your team.
Yours from day one
Before anything is written to a buyer, every account in the market is found, given one id, and read. We get there three ways, usually all three at once.
Three ways in
[the lists, registries and directories our agents sweep for their market (from the inputs view)]
[what they already hold: their CRM and lists (from the Gold Sheet's tech)]
[the bought or public lists that fill the gaps]
Our early read
Research estimates.
[what is counted, and its source]
How we'd segment it
[what defines it and why it matters to [Their company], from the research]
The personas inside them
[who they are]
How we'd target
Every account gets a fit score and its signals. The score says who is worth reaching; the signals say when. Then the buyer is found, verified and matched to a persona.
The structured lists say who is out there. The unstructured record says what is moving: deals, launches, hires, departures, a competitor's move. We found these sources for your market and read them every week.
Who else is on the field
Sources we found, and why each matters
What we found early
[two sentences, every number sourced]
One item, followed into the system
[a real public item from their market]
[its source]
The Stakeholder Registry ties it to each account it names, each on its one id.
[how the Market Desk classifies it, once]
[the signal it puts on which accounts]
[the reason it gives a buyer to hear from [Their company]]A person approves before anything is sent.
[the research run and its date; which figures are estimates]
What you already hold comes in beside what we find, read-only, matched to the same ids, so outreach never lands on an account already in a deal, already a customer, or owned by a colleague's relationship.
Read through each system's API. Never written back without a yes.
Code picks the argument. The model writes. A person sends.
Specimen messages
[one line on the account, from its own site, with [merge fields]]
[the persona's pain, from the matrix]
[[Their company]'s value for it]
[one question]
[Sender], [Their company]
[a connection note under 300 characters]
[one line on the account, from its own site, with [merge fields]]
[the persona's pain, from the matrix]
[[Their company]'s value for it]
[one question]
[Sender], [Their company]
Built properly
On dedicated domains, never your corporate one; the inboxes warmed; every reply comes back into the system.
From your own people's profiles, standardized messaging at a conservative pace, well within the platform's limits. A person clicks send.
The system speaks your market's language. Every agent reads these definitions.
Fast to start. Then constant collaboration and improvement.
This page is the starting point, not the scope. We stand the system up quickly, then build it out with your team on a loop, in the order your priorities call for.
Switched on first
Layered on as the scope grows
The loop
Through the five views that follow you'll see the depth and the organization that goes into building it.
Every list, registry and feed, how we'd get it, and where it lands.
Open → 2The [Their company] OS and Brain, raw to ready, their context underneath.
Open → 3The agents by team, with their skills and tools.
Open → 4From every account in the market to a signed deal, and round again.
Open → 5Defining the scope of our partnership: the ways we could start.
Open →Every source we'd recommend, checked 2026-11-06: what it gives, how we'd get it, what it costs where a price is published, and which box on the OS map it lands in.
Lands in Raw (lane 1), then the ID system gives every account and buyer one id, then the ladder climbs it.
| Source | What it gives | How we get it | Cost | Lands in |
|---|---|---|---|---|
| [a list or registry] | [what it gives] | [API, bulk file, scraper agent] | FREE or PAID [the published price] | ID system · ladder |
Lands in lane 2 as read-only copies, matched to the same ids, so outreach never lands on an account already in a deal or already a customer.
| System | What it gives | How we get it | Cost | Lands in |
|---|---|---|---|---|
| [their CRM] | Contacts, companies, deals, activity | [its API] | THEIRS | System landing · deal context |
Lands in lane 3. The Stakeholder Registry links each item to its account (by id, then name or a learned alias); the Market Desk's gate reads only what matters, classifies it, tags it and counts it by week.
| Source | What it gives | How we get it | Cost | Lands in |
|---|---|---|---|---|
| [a trade feed] | [what it gives] | RSS, or a scraper agent | FREE | Registry · Market Desk |
Computed in Step 2 on each account (ladder L4), held in Resolved, and read by the Campaign Manager and the messaging agent.
| Signal | Why it matters | Fed by |
|---|---|---|
| [a signal] | [why it predicts a deal] | [which sources] |
Lands in lane 4, goes straight to the touch ledger, and every later campaign reads it.
| Source | What it gives | How | Lands in |
|---|---|---|---|
| HeyReach | Connects, accepts, replies, per sender | Hourly sync | Touch ledger · campaign tasks |
| EmailBison | Sent, opened, replied, bounced | Hourly sync | Touch ledger · blocklist on bounce |
| Calendar · website | Meetings booked; visits and forms | Calendar and site analytics | Touch ledger · pipeline |
The [Their company] OS works from the bottom up. Every input lands in Raw, gets one id, climbs a ladder of enrichment, rests in one database, and becomes work a person approves.
The things specific to [Their company]. It decides how an agent is built, how a skill or tool is registered, and who may use what. Their own server, database, repository and context. Everything it holds goes into the [Their company] Brain.
Their words, written once: [five of their terms]
[their account types, segments, regions, buyer personas, deal stages]
Every agent with its job card: Registry, Ladder, Market Desk, Campaign Manager, the messaging agent
The runbooks each agent follows: find prospects, enrich an account, fill a campaign, write the brief
What the agents act through: [their CRM and data tools, Clay, email finding, HeyReach, EmailBison, Claude. Keys in a vault]
One sign-in on [Their company]'s accounts: [the roles, each seeing their own tabs]
Context → data → skills and tools → agents → fleet. Propose, then a person confirms; the build loop; the boundaries
Any agent asks the Brain through one door; the next move is proposed to a person
Sits on top of everything [Their company]: what the OS holds, the context, every account and buyer, every deal and touch.
Joined on one id, never copied. Any agent calls it through one door. What it can't answer goes on a gap list.
The language, taxonomy, registries and build rules, read in place
Their story, buyers and segments: the foundation (bottom band)
Every list, registry and feed: what came in, when, from where
Which agent, rung and gate moved each account or buyer
Accounts ↔ buyers ↔ partners ↔ deals ↔ competitors
Deals, moves and trends by week, from the Market Desk. Market facts, never contact details
What each brief, draft and approval read, and what came back from it
Agent runs, findings and lessons, each run traced
Below: the pyramid on [Their company]'s database. Context is the foundation (bottom band); well-structured SQL sits on it; skills, tools and agents move data through the two steps; Resolved holds it; Ready on the right is where it lands for people.
names accounts and buyers
Every account and every buyer gets one record and one id, whatever list it came from.
A person approves each mint batch
[what the ladder reads for an account, from the website and the registries. Free rungs run at once; paid rungs wait for a yes]
The sales team sets the target status
Gates: in the market · already in a deal · already a customer · do-not-contact · not already reached → ready
A person reviews every new buyer record
in the market · id, ladder level, type, fit score, target status
role, persona, email, LinkedIn
their own records, read-only
Read through each system's API. Never written back without a yes.
Their records sit beside ours, matched on the same id.
So outreach never lands on an account already in a deal, already a customer, or owned by a colleague's relationship.
"The CRM disagrees" is a proposal; the sales team confirms
one read view per account, keyed by the id
segment × account type × buyer persona × channel, compiled from the spine
market records: context, linked to accounts
Links each record to an account by id, then exact name or a learned alias. A miss waits in a queue.
A person confirms what it is unsure of
The sales team sets the bar
Tags flow downstream: a signal on the account, a reason to write on the buyer, a competitor on the map.
The sales team reads the brief before it goes out
deals, news, filings and changes, by account
signals per account; terms and competitor moves by week
who touched what we put out
A reply goes to the sales team; the workflow stops there
Touches skip the climb: every later campaign reads them as "already reached", per channel and sender.
every touch per buyer × channel × sender
one screen the sales team opens each morning
every account in the market, by segment and fit score
one account in depth: its people, signals and sources
who goes in each campaign, which sender, which sequence; fills from the ready buyers
messaging agent drafts from the matrix; EmailBison and HeyReach; a person approves every send
accepts and replies, drafted on a click
from first reply to signed
who moved, who bought, what changed
a signal on a target account → a task for the sales team
the plan before each call; the plan per deal
prospect pages, proposals, the paper
ids and merges, the agents on screen, role-based tabs
Where any page, rule or screen disagrees with it, the context wins.
Ids first, then exact name or a learned alias. Never a similarity score.
[the outreach rules for their market]
Every agent in the [Their company] OS, drawn the way a company draws its people. The OS sits on top, with the services every team shares. The four teams run left to right, the way the work flows: the data system brings everything in on one id, intelligence reads and ranks it, marketing reaches the buyers, and sales management carries the deal to signed.
One operating system for [Their company], on its own server, database and repository.
one word, one meaning: their words, written once
[their account types, segments, regions, buyer personas, deal stages]
what may be said, who approves what, nothing sends on its own
look → plan → approve → build → write back
context → data → skills and tools → agents → the fleet
every agent placed on the lifecycle, from the first record to the signed deal
who sees what, and who starts what
what each piece is for, held to [Their company]'s goals
[where they go across the web for every account: the lists, directories and registries. What they find comes back staged, for the Registry agent]
Brings in and tracks the news feeds: [their trade press and trackers]
Brings in the live APIs and outside tools: [the public APIs and paid data for their market, and the systems they plug in]
One id per account and per buyer. Matches on a registry number, a domain or a learned alias; proposes a mint when nothing matches.
Matches every news item, filing and website change back to its account, and learns the aliases.
Climbs every account: sized and typed, website read, scored for fit, buyers found and reachable.
The cold read on everything that comes in: what matters is summarized once, tagged to their terms and counted by week into trends. Every team downstream reads its tags.
The weekly intelligence report: who moved, who bought, what changed.
Plans each campaign: who goes in, which sender, which sequence; fills it from the ready buyers.
One message per buyer from the matrix and a sourced fact pack; checked before a person sees it. Never sends.
Email and LinkedIn in and out every hour; every reply handed to a person.
Posts for the company and its leaders: ideas, drafts, a calendar, review, analytics. Social listening scores who engages.
SEO through the blog, GEO (how AI answers mention them), and Google Ads with a landing page per term.
LinkedIn, Facebook and Instagram ads aimed at the accounts on the target list.
The events in their market, who exhibits and attends, matched to accounts.
Branded images, video and voice for every channel. Reviewed in one queue.
The newsletter from the weekly brief; guides, case studies and webinars. Any other channel can be added the same way.
Reads the Market Desk's trends and the engagement on target accounts, and turns a signal into a task for the sales team.
Holds the stages and their rules, moves deals across when the gates are met, and sends the weekly pipeline review.
A plan before every call: who is in the room, the objective, the questions; a brief after it, from the transcript.
One living plan per deal: who decides and how they lean, where it stands, the red flags, the next move.
The long play for an account and the research behind it.
On demand at each stage: the NDA, a prospect page, the proposal, the agreement. People review every one.
Where the outputs land. Three parts, top to bottom: the lifecycle (every account's status and every buyer's line, phase by phase, team by team), the deal pipeline opened out stage by stage (the sheets, the sales aids and the paper at each one), and the channels beneath it all.
From every account in the market to a signed deal, a customer, and round again. Every account holds one status and every buyer moves along one line; the two lines are tracked side by side. The four teams work it left to right, and a person decides at every gate.
Phases 4 to 6 above, opened out. The probability is set by the stage, not guessed. The sheets, the sales aids and the paper sit under the stage they belong to; they don't move the deal by themselves. The gates are what must be true before a deal moves on.
The channels move each account from the target list to warm to a first meeting. Some keep working through the pipeline and after the signature. Each bar spans the statuses the channel works across.
[what it is, in one sentence]
We build; [Their company]'s people work alongside us and take pieces into their own work.
We show what's built and how; your team builds it.