Yungsten Tech · Rounds

A biweekly with the C-suite. A wiki. Four agents.

Ninety minutes with the C-suite, every other week. A quiet wiki. Four agents, built with you over the first quarter. The operating load that usually waits for the next hire.

What Rounds is

A cadence, a wiki, and a few standing orders.

Rounds is what clinical teams call the ritual where the senior group walks through cases. We borrowed the name. The retainer has the same shape: a small, repeated session where the operating posture gets tended.

The work between sessions is quieter. A wiki that tends itself. Claude on the right laptops, configured the way we set it up for our own team. A small set of agents — the running directives a hospital would call standing orders.

Five pillars

What you actually get for the retainer.

The wiki feeds the agents. The agents feed Rounds. Rounds feeds the seminar. The seminar feeds the wiki.

  1. 01

    Wiki & centralization

    A private wiki in Obsidian. Claude tends it quietly between sessions. By month two it’s the place where decisions, sources, and people get recorded once.

  2. 02

    Claude rollout

    C-suite and operators on Claude Pro/Max with the right MCPs, configured the way we run it for our own team.

  3. 03

    Rounds — biweekly

    Ninety minutes with the C-suite, every other week. We arrive with what the agents surfaced, what the wiki absorbed, and what the next two weeks could carry.

  4. 04

    Agents

    A small set of running directives, built with you over the first quarter and iterated after. The first weeks are discovery — what signal matters, where it lives, who reads the output.

  5. 05

    Continuous training

    A monthly seminar for the broader team. Updated each month because the tooling moves each month.

What an agent looks like, concretely

Four running directives.

Each is a build. Discovery first, then ship.

KOL meeting prep brief

Before any KOL, advisor, or external expert call, a two-pager: publications, recent talks, prior interactions on record, talking points hypothesized from their last decade.

Discovery
How you currently prep, what shows up missing in the meetings, where prior interactions live. Often the data is scattered across email, calendar, and one person's head.
Build & first ship
First version in three to five weeks. Most of the work is in the source plumbing, not the writing.

Weekly literature & competitor digest

A Friday brief on the journals, preprints, and competitor pipelines that move the conversation for the program in front of you. When programs diverge enough that one brief becomes noise, we run separate briefs.

Discovery
Per program: which journals, which competitors, which mechanisms, which thresholds. Two weeks of close work with whoever currently does this informally.
Build & first ship
A first version in three to four weeks. Iteration thereafter is part of Rounds.

Partner, investor & 1:1 prep brief

Before any partner alliance meeting, joint steering committee, investor 1:1, or external 1:1, a quiet brief on what was discussed last, what has changed since, and what they care about — pulled from the meeting record, not a CRM you do not have time to maintain.

Discovery
Where the meeting record actually lives. For most clinical-stage teams the answer is “in three places, none of them complete.” That is half the design problem.
Build & first ship
First version in four to six weeks. The interesting work is in keeping the source-of-truth clean as it accrues.

Board pack drafter

Turns the running notes, meeting transcripts, and threads of a given month into a structured first draft of the next board update. The raw material assembled; the synthesis stays with the team.

Discovery
What your board cares about, the recurring rubric, what gets cut every quarter and why. We assemble the source material, not the judgement.
Build & first ship
First draft in four to six weeks. The first two cycles are heavy on review; by cycle three the shape settles.

Cadence

The first ninety days, in order.

A working rhythm by the end of the quarter.

  1. Days 1–30

    Mostly listening. The wiki begins to take shape. Claude is on the team’s laptops. No agent ships in the first month.

  2. Days 31–60

    First agent moves from discovery into build. Rounds is the standing biweekly. The monthly seminar opens.

  3. Days 61–90

    First agent in flight. First quarterly review — what stuck, what did not, what to scope next.

  4. From there

    Rolling. Two new agent scopes per quarter; one retired. The second year does not have to look like the first.

Retainer

Pricing.

Monthly retainer, scoped to cadence, room size, and which agents you want first. The range sits in the leave-behind.

The hire that competes for this budget is usually a strong chief of staff or senior EA, or the next analyst, writer, or comms slot. A year of Rounds fits inside that line. It can sit alongside the hire, or instead of it, depending on the year.