Case study

Virtual BDR: codifying the BDR's job as composable blocks.

Built solo, 2023 to Present. The whole BDR workflow codified as composable blocks so the same blocks recompose per client instead of being rewritten.

Third instance of the invariant move, after SignalsAPI and KIMA.

Problem

The problem: someone still has to act on the signal.

SignalsAPI finds the signals: posts opening, roles staying open, the same company hiring again. Someone still has to act on them, reach out on LinkedIn, follow up, warm up, get meetings booked. That is a human BDR's job, and it is expensive and inconsistent.

Insight

The insight: codify the BDR's job, not a LinkedIn automation tool.

The conventional reading builds a tool that automates clicks on LinkedIn. The structural reading is different: the work to be codified is the BDR's whole workflow, prospecting, outreach, follow-up, nurture, modelled at an abstraction that survives a different client, persona and market. The blockquote is the difference in his own words.

SignalsAPI is finding signals, Virtual BDR is acting on signals. I have created LEGO pieces, construction bricks, modules for different LinkedIn activities and different email activities. And standardized the whole process of a business developer's work: not only the research, which is SignalsAPI's job, the research of leads, but the actual work of reaching out, following up, connecting and building relationships. I codified it. I created large pieces which are the same whoever works with it, and then I build the whole process out of those larger reusable blocks.

Architecture

The architecture: LEGO blocks, not a monolithic flow.

Schematic — shape only

The same move as SignalsAPI and KIMA, in a third shape: composable blocks underneath, the composition varies on top. Different clients plug in via different compositions of the same blocks. Multi-persona orchestration runs parallel campaigns across distinct buyer personas, each with its own messaging and cadence, kept in step by the shared blocks underneath. The abstraction makes the system client-independent, because the blocks do not change.

Both outbound channels are the same kind of block. The codified workflow covers prospecting, LinkedIn outreach, email sequences, follow-ups and nurturing, so a channel is a composition of existing blocks rather than a separate tool bolted on the side.

Proof

The proof: the third instance, and the pair with SignalsAPI.

The invariant move, applied three times. SignalsAPI found the invariant across 457+ job boards that change daily. KIMA found it across many CRMs and many agency processes. Virtual BDR finds it across every client's outreach motion: the chaos is per-client variation, the invariant is the set of reusable blocks underneath. Three systems, three domains, the same move. That repetition is the argument.

Together SignalsAPI and Virtual BDR are a complete outbound machine: one detects intent, the other converts it. The pair is the strongest commercial claim in the portfolio, because it demonstrates thinking in businesses, not features. No usage numbers are published here because none have been earned: no campaign counts, no meetings booked, no conversion rate, no client count.

Record

The line under the work.

Architect & Sole Developer.

Virtual BDR: codifying the BDR's job as composable blocks, built solo, 2023 to Present, as Architect & Sole Developer. Third instance of the invariant-under-the-chaos move, after SignalsAPI and KIMA. LinkedIn outreach and email sequences run from the same block library.

Talk it through.

Book twenty minutes

The rest of the work sits on the Work page. Prefer to write first? Mail goes directly to [email protected].