Reported operating use · Research and founder relations

ROS's reported founder outreach and trip-calendar workflow

The authors report outreach and a geographically grouped meeting calendar from prior notes and their startup database. Actual approvals and outcomes are unverified; separate travel-booking mistakes are kept outside this workflow.

Prepare founder outreach and a geographically grouped trip calendar

Rational Optimist Society authors Stephen McBride and Dan Steinhart

Authors' internal operating account, published 15 November 2026. The date alone does not establish exact rolling-48-hour freshness, and trip/implementation dates remain unverified.

A published third-party example, not a Nuvepro customer case or evidence of a partnership.

The workflow at a glance

ROS authors report founder outreach and a grouped trip calendar

Illustrative summary of the published account

Reported work components. Their arrangement does not imply a fixed execution order or simultaneous work.

  • Prior trip notes, startup database and Claude Code

    Find founders relevant to the trip cities

    The authors report using prior trip notes and their startup database to identify founders to meet.

  • Claude Code and founder replies

    Send outreach and handle follow-ups

    The account says the agent sent outreach, read replies and followed up when needed. It does not establish approval before every send.

  • Claude Code calendar preparation

    Group meetings by neighborhood

    The authors report a calendar grouping meetings geographically. Meeting confirmations, conflict checks and travel-buffer rules were not independently inspected.

  • Authors and human relationship judgement

    Retain decisions needing a human touch

    One author describes escalating some messages to him; criteria are unspecified. Authors retain relationship and visit judgement, not a demonstrated universal pre-send approval gate.

Components summarize an internal author report, not a fixed approval sequence or independently measured outcome. The November 15 publication is not an implementation date. Separate flights and hotel booking used Instinct; its wrong guest name and missed member rate are not demonstrated Claude scheduling failures. The authors disagree about primary-email access, and one author's secondary inbox and device are not a universal shared safeguard. Promotional comparisons and future predictions are excluded. See the source account and limitations below.

What the source reports

The authors report using prior trip notes and their startup database to find founders for a research trip. Claude Code sent outreach, read replies, followed up and built a calendar grouping meetings geographically. They reserve relationship judgment for people; pre-send approval is not established. Flight and hotel booking was a separate travel leg.

Reported technology: Claude Code for the reported outreach and calendar work. Scope and outcomes are source-reported.

What the enterprise environment would need

The following is a proposed project design for an enterprise doing similar work. Published details are marked; the remaining systems, data and scenarios would be agreed for your project.

Proposed practice environment

Review a synthetic outreach queue and geographically grouped calendar

Illustrative project design to scope with your enterprise.

  1. 1 · Set up the environment

    Fictional founder records and independent scheduling references

    Use synthetic trip notes, founder identities, permitted contact states, reply histories, meeting availability and city locations. Freeze independently authored invitation-eligibility, time-zone, availability, meeting-duration and geographic travel-buffer references. No real inbox, social account, calendar or booking system is connected.

  2. 2 · Preparation and agent contributions

    Agent drafts outreach and a calendar with explicit unknowns

    Prepare an unsent recipient-and-message queue and a geographically grouped calendar proposal. Link choices to the supplied notes, preserve identity and reply state, and mark unconfirmed meetings or unknown availability instead of inventing agreement.

  3. 3 · Independent checks

    Independent coordinator verifies recipients and scheduling constraints

    A verifier separate from the drafting agent checks identity, duplicate contacts, eligibility, reply state and message support against the frozen references. Independently reconcile time zones, overlapping meetings, availability, meeting duration and travel buffers using the supplied geographic reference; check missing replies, changed locations and impossible journeys.

  4. 4 · People decide acceptance

    Trip owner accepts the exact checked drafts and calendar

    The accountable trip owner accepts or rejects the exact independently checked recipient queue, unsent messages, calendar version and unresolved choices together. Relationship priorities remain a human decision; rehearsal acceptance authorizes no real outreach, calendar invitation, booking or payment.

Only within the accepted practice scope
Practice output

A reviewable evidence package

A versioned unsent outreach queue and proposed calendar, source-note links, independent eligibility/scheduling results and trip-owner disposition.

If a check fails → withhold acceptance.

An ineligible or duplicate recipient, unsupported message, stale reply state, unknown confirmation, time-zone conflict, impossible travel buffer or owner rejection withholds acceptance. Repair the draft queue or calendar, repeat independent recipient and scheduling checks, then return the exact revised package to the trip owner.

Failure or owner rejection returns to review

  1. Hold
  2. → 2 · Revise work
  3. → 3 · Rerun independent checks
  4. → 4 · Owner review

Operating boundary. Designed checks, not executed. Fictional or approved rehearsal records only; no real email, direct message, calendar write, reservation or payment. Trip and relationship owners must confirm eligibility, location references, buffers and acceptance rules.

Proposed, not an executed Nuvepro project or a description of the named company’s implementation. Owners agree the data, rules, responsibilities and acceptance criteria for their enterprise.
Synthetic trip brief, contact permissions and scheduling references
Proposed: use fictional founder records, prior-trip notes, permitted contact rules, reply histories, agreed cities, time zones and availability. A separate coordinator prepares expected eligibility, reply-state, calendar-conflict and geographic-grouping references. Keep real inboxes, social accounts and calendars disconnected.
Agent drafts an outreach queue and trip-calendar plan
Proposed: identify in-scope fictional contacts, draft unsent messages and follow-ups, and propose a geographically grouped calendar with source-linked availability and unresolved questions. Do not infer a confirmed meeting from an unanswered invitation or fill missing travel-time facts.
Independent coordinator checks contacts and calendar constraints
Proposed: a verifier separate from the drafting agent compares identities, contact eligibility, reply states, time zones, availability, duplicate invitations and travel constraints with the frozen independent references. Preserve unresolved relationship or scheduling decisions for the owner; no email or calendar write is permitted.
Research-trip owner accepts the exact checked plan
Proposed: the accountable trip owner accepts or rejects the exact unsent outreach queue, calendar plan and remaining exceptions after independent checks. Changed replies, permissions or dates invalidate the old plan and return through repair, independent rechecks and owner review. Live sending and booking require separate authority.

A proposed simulation

An illustrative practice design derived from this work, not an executed assessment.

Rehearse a founder outreach queue and geographically grouped research-trip calendar using fictional contacts, replies and scheduling references.

Review gate: In the proposed rehearsal, the trip owner accepts only the exact unsent outreach queue and calendar version that passed independent eligibility, identity, reply-state, time-zone, availability and geographic checks. Acceptance grants no real sending, calendar, booking or payment authority.

Challenge the result: A changed reply creates an unavailable slot or a repeated invite targets a contact without permission. Hold acceptance, repair the affected queue and calendar, rerun independent checks and return the exact revision to the trip owner.

What needs checking

  • Source boundary: this is an internal author report, not an external customer delivery or FDE engagement. Human relationship judgment does not establish approval before every message or a shared technical permission gate.
  • Proposed: test missing availability, time-zone conflicts, an unconfirmed reply, repeated invitations, withdrawn contact permission and geographically incompatible meeting slots against independently prepared references. Designed, not executed.
  • Proposed: change a founder's reply or availability after review. Invalidate the outreach/calendar version, repair the affected plan, repeat independent eligibility and scheduling checks and return the exact revision to the owner. Designed, not executed.

Review environment fidelity, human capability and agent performance separately. The enterprise’s accountable owners decide acceptance of the shared workflow and any operating use.

How an enterprise could build similar work

A proposed build order for an enterprise doing similar work, written by Nuvepro from the published account and our interpretation of the environment and checks above. It is not how Rational Optimist Society authors Stephen McBride and Dan Steinhart built or operates this work.

  1. Synthetic trip brief, contact permissions and scheduling referencesProposed: use fictional founder records, prior-trip notes, permitted contact rules, reply histories, agreed cities, time zones and availability. A separate coordinator prepares expected eligibility, reply-state, calendar-conflict and geographic-grouping references. Keep real inboxes, social accounts and calendars disconnected.
  2. Agent drafts an outreach queue and trip-calendar planProposed: identify in-scope fictional contacts, draft unsent messages and follow-ups, and propose a geographically grouped calendar with source-linked availability and unresolved questions. Do not infer a confirmed meeting from an unanswered invitation or fill missing travel-time facts.
  3. Independent coordinator checks contacts and calendar constraintsProposed: a verifier separate from the drafting agent compares identities, contact eligibility, reply states, time zones, availability, duplicate invitations and travel constraints with the frozen independent references. Preserve unresolved relationship or scheduling decisions for the owner; no email or calendar write is permitted.
  4. Research-trip owner accepts the exact checked planProposed: the accountable trip owner accepts or rejects the exact unsent outreach queue, calendar plan and remaining exceptions after independent checks. Changed replies, permissions or dates invalidate the old plan and return through repair, independent rechecks and owner review. Live sending and booking require separate authority.

Your systems, data, rules and accountable owners decide the real project. Agree acceptance criteria, escalation owners and operating responsibility with the people accountable for the work before anything runs on live records. Treat the first run as a rehearsal on test records: compare the draft output with an independently prepared answer, and record what the people reviewing it change.

Questions about this example

Are the booking mistakes calendar failures?
The wrong guest name and missed member rate concern the separate Instinct travel leg. They do not establish failures in the reported founder outreach or meeting calendar.
Who accepts the proposed rehearsal?
In the proposed rehearsal, the trip owner accepts only the exact unsent outreach queue and calendar version that passed independent eligibility, identity, reply-state, time-zone, availability and geographic checks. Acceptance grants no real sending, calendar, booking or payment authority.
Were the proposed checks executed?
No. The separate design uses synthetic or approved rehearsal records and independently prepared references. It authorizes no real accounts, messages, calendar actions, bookings or payments.

Shape this around your enterprise

Bring a similar workflow and the people responsible for it. Together, define the records and systems to use, the result your team will build or configure, and how its owners will check it. Nuvepro scopes the simulation, environment and preparation. Agree any existing-agent evaluation, implementation assistance and production responsibilities separately.

Sources and limitations

Curation review: . This is the date this source example was reviewed, separate from source publication dates.

  • The authors' runtime logs, recipient records and calendar artifacts were not inspected. Outreach volumes, time saved and effectiveness remain author claims and are not reproduced as measured impact.
  • The authors disagree about primary-email access: one describes it, while the other uses a secondary inbox and separate device. One author's precautions are not a verified shared safeguard.
  • Wrong guest-name and missed member-rate errors belong to the separate Instinct booking account, not proven failures of this outreach/calendar workflow. Promotional product comparisons and broad future claims are excluded.
  • The 15 November date is a seven-day-overlap source, not a verified implementation launch or exact 48-hour match. Proposed checks are designed, not executed. No real contact, calendar write, booking, payment or Nuvepro customer/partner status is authorized.
  1. The Rational Optimist's guide to AI agentsSource publication: 2026-11-15

More sales and marketing examples

All 20 sales and marketing examples

Explore more enterprise work