Venia Products × FridayOS — Venture Onboarding

Venture Onboarding

Venia Products × FridayOS

Session 2 · May 7, 2026

Facilitators Fred Butson · Lucas Robinson

Team Eden Schweyer · Denise Moscare · Rebecca Zelaya · Darren Karunaratne

Verbatim opener (90 sec). "Welcome back, team. Good to see everyone again."

Quick pulse — 30 seconds, no more: "How'd the week go? Anyone get into the repo since last time?"

▶ Don't let this become a full progress report. You already know the answer from the data: nobody has moved. Take whatever they give you — one or two sentences — and pivot forward.

"Today is different from last session. Session 1 was about seeing what FridayOS is — the repo, the structure, how it works. Today is about activation. We're going to show you exactly where you are on the journey, Lucas is going to demonstrate a real capability live, and you're going to leave here with commitments tied to your adoption roadmap. Sixty minutes. Let's get into it."

▶ Tone: warm but direct. No dwelling. This slide is a bridge — move to Slide 2.

The Working Definition

AI-First Operations

AI is the default operating surface.

Your context, decisions, and goals live in a system your AI can read.

Every team member becomes a builder.

Contributing to infrastructure, not just using tools.

The business compounds.

Context captured today makes tomorrow's work smarter — for everyone.

Verbatim (3 min). "Before we get into the roadmap, I want to land a definition. Because the phrase 'AI-first operations' can sound like marketing. It isn't. It's a structural change in how a business runs."

"Pillar one — AI is the default operating surface. That means your context, your decisions, your goals all live in a system that your AI can actually read. Not in a Google Doc. Not in someone's head. Not in a Slack thread that disappears in two weeks. In a system that Friday — your AI operating partner — can access and use every single day."

"Adam described himself as 'the load-bearing context store' for this business. That line stuck with me — because it perfectly captures what happens when the context lives in a person instead of a system. One person gets sick, goes on vacation, gets pulled into another fire — and the team loses access to what they need. AI-first operations means the context lives in a system, not in a person."

"Pillar two — every team member becomes a builder. Not 'use AI more.' Not 'adopt another tool.' You are contributing to the infrastructure of the organization. Building things that serve your team permanently."

"Pillar three — the business compounds. In most tools, your work disappears into a void. You do the task, it's done, it's gone. In this system, every piece of context you capture — every knowledge article, every decision, every learning — makes the system smarter for everyone. Not just for you. For your teammates. For Friday. It compounds."

▶ This is the definition slide. Say it clearly, don't rush. Make eye contact on the Adam reference — the room knows that pain point. Don't apologize for naming it.

The Commitment

This venture is adopting an AI Operating System.

What this is NOT

Another layer of tools

Additive to your workload

What this IS

Replaces tools over time

From doing the work to steering it

STAGE 0

Environment Ready

STAGE 1

Daily Operations

STAGE 2

Context Builder

STAGE 3

Workflow Builder

STAGE 4

AI-First Operator

STAGE 5

Orchestrator

Verbatim (3 min). "Let's address something head-on. One of the signals we picked up — and I think several of you feel this even if you haven't said it — is the concern that this is another layer of tools. One more thing to learn on top of everything you're already managing."

"So let me be direct. On the left — what this is NOT. This is not additive. This is not a new tab you open alongside your other tabs. This is not a burden."

"On the right — what this IS. Over time, this is reductive. The tools you currently pay for monthly — many of them get replaced by things you build inside this system. Project management tools, communication tools, reporting tools. You're going from renting to owning. The total surface area of tools you operate in shrinks, not grows."

"And the path from where you are now to that point — that's the adoption roadmap. Six stages. Forty-seven milestones across those stages."

Walk the strip quickly — 10-15 seconds each. Don't go deep:

"Stage 0 — environment ready. GitHub, Claude Code, repo cloned. The basics. Stage 1 — daily operations. Start-day, inbox, session state. The daily habit. Stage 2 — context builder. Knowledge articles, notes, learnings. The compounding layer. Stage 3 — workflow builder. Custom skills, workflow capture. Stage 4 — AI-first operator. Production workflows, measurement, governance. Stage 5 — orchestrator. Multi-agent, cross-domain coordination."

"That's the full journey. The detail lives in HQ, which is exactly where we're going next."

▶ This is a combined slide to save time. The 6-stage strip is a teaser — the HQ demo is where it becomes real. Don't over-explain stages 3-5; the team is at Stage 0.

friday.adoption

Here’s what I’m going to show you.

01Your adoption dashboard — where Venia stands as a team right now
02Your personal roadmap — Stage 0 and Stage 1 milestones, gates, and next steps
03Inside a milestone — exactly what to do, no ambiguity
04Team progress + maturity — peer accountability, collective advancement

▶ SHOW THIS SLIDE FIRST. Read through the four items to frame what they're about to see. Then: "Let me pull up HQ and show you this live." Switch to screen share. Stay on screen share for the full demo (~12 min). Advance to the next slide when you're done.

SCREEN SHARE FACILITATION GUIDE

Beat 1 — Adoption dashboard (~3 min). Open the adoption page for Venia Products. Show the venture-level summary: maturity level, stage distribution bar. "This is where Venia stands as a team. Right now, every member is at Stage 0. Three of forty-seven milestones completed. Six percent. That's not a problem — that's a starting point. The important thing is you can see it."

Beat 2 — "My Roadmap" view (~3 min). Walk through Stage 0 and Stage 1 milestones specifically. Point out which ones are gates (required to advance). "Each milestone is a concrete action. Not vague. Not 'get comfortable with the tool.' It's — did you do this specific thing? Yes or no."

Beat 3 — Expand a milestone (~2 min). Show the "How to do this" panel — the FridayOS command, the instructions. "Every milestone tells you exactly what to do. There's no ambiguity. You don't need to figure out the next step — the roadmap shows it to you."

Beat 4 — Team Progress + Maturity (~4 min). Show where each member stands. "This is where peer accountability comes in. Your teammates can see where you are. Not to judge — to help." Then show the venture maturity level. "The venture has a maturity level — not just individual progress. When fifty percent of the team reaches Stage 1 with at least one at Stage 2, the venture moves to Level 2: AI-Ready. The venture advances together. One person sprinting ahead while three stall doesn't move the level. This isn't surveillance — it's shared accountability."

▶ Name each person's position: "Rebecca, you're here — Stage 0, 3 milestones done. Eden, here. Darren. Denise." Make it personal.

▶ Address Eden directly on steward view: "Eden, as the OS steward — this is your view. When someone's stuck, you'll see it here before they have to tell you."

▶ Pause for questions after each beat. This is conversational with 4 people — not a webinar.

▶ When done: stop screen share, return to deck, advance to next slide. Transition: "That's the roadmap — where you are and where you're going. Now let me share what we heard from the team after Session 1."

What We Heard

After Session 1, we asked. Here’s what came back.

Rebecca’s Signal

Fully set up. Practicing 3+ days/week.

Building a configurator. Blocker: time. That's real — and what Lucas is about to show you actually saves time.

The Context Bottleneck

Adam: “I'm the load-bearing context store.”

A structural problem, not a personal one. Every one of you carries context that nobody else can access.

The Gap

1 of 4 team members responded to the survey.

We're missing where three of you are. If we don't know, we can't help. Surveys due end of this week.

Verbatim (3 min). "After Session 1, we sent out surveys. I want to share what we got back — honestly."

"Rebecca — you responded. And what you told us was valuable. You're set up, you're practicing multiple days a week, you're building a configurator. Your blocker is time. That's real, and we're going to address it."

"Adam — he's not in this session, but his response is relevant to all of you — described himself as the load-bearing context store. Everything about the catalog, the vendor relationships, the product configuration — lives in his head. When he's not available, that context is not available. That's not sustainable. And it's not unique to Adam — every one of you carries context that nobody else can access."

"Now here's the part I have to name. Three of four of you didn't respond to the survey. I'm not shaming anyone. But I'm naming it because if we don't know where you are, we can't help you get to where you need to be. The survey takes ten minutes. I need those completed by end of this week."

Transition — make it clean:

"Two themes came through: time, and the context bottleneck. Lucas is going to show you exactly how knowledge capture addresses both of those — right now, live, in your repo. Lucas, show them."

▶ This is the handoff to Lucas. Be direct about the survey gap — don't soften it into irrelevance, but don't make it punitive either. The data is the data. Then transition cleanly.

friday.knowledge

Here’s what Lucas is going to show you.

01Capture real context — actual Venia business knowledge, not fake data
02See the artifact — where it lives, how Friday indexes it
03Before vs. after — generic answer → Venia-specific answer
04Tie back — this is Stage 2 on your roadmap: Context Builder

▶ SHOW THIS SLIDE FIRST. Read through the four items so they know what's coming. Then hand off: "Lucas, show them." Lucas takes screen share. Stay on his screen share for the full demo (~15 min). When Lucas finishes, Fred takes back screen share, returns to deck, and advances to the next slide.

SCREEN SHARE FACILITATION GUIDE (Lucas drives)

Beat 1 — Frame it (1 min). "We're going to capture a piece of business context that currently lives in someone's head. Not a demo with fake data — this is actual Venia business context going into your system right now."

Beat 2 — Capture something real (4-5 min). Create a knowledge article or use /note with genuine Venia e-commerce context — a product configuration rule, a vendor relationship detail, a pricing logic constraint. Something concrete and recognizable to the room.

Beat 3 — Show the artifact (2 min). Show the file in the repo. Walk the structure — metadata, content, how Friday indexes it. "This is a file in your repo. It belongs to Venia. It's version-controlled. It's searchable. And Friday can read it."

Beat 4 — THE MONEY SHOT (4-5 min). Ask Friday a question that requires the captured context. Show the before (generic, surface-level answer) and the after (Venia-specific, contextually rich answer). This is the "oh, that's what this does" moment. Make it land.

Beat 5 — Second pattern (if time, 2-3 min). Show /learning-capture as an alternative entry point. "There are multiple ways to get context into the system. Knowledge articles for reference material. Learnings for things you discover in the course of work. Both feed Friday."

Beat 6 — Tie back (30 sec). "Everything I just showed you — that's Stage 2 on your adoption roadmap. Context Builder."

Talking points for Lucas (natural beats, not scripted):

"What I'm about to do takes about three minutes. The context it captures serves your team permanently."

"Notice what just happened — Friday answered that question using knowledge that didn't exist five minutes ago. That's the compounding effect."

"Rebecca — you're already doing this with the configurator. Same pattern, applied to business knowledge."

▶ Fred: monitor the room during Lucas's demo. Pull quiet members in at natural pauses: "Darren, can you think of something from your product line worth capturing like this?" "Eden — as steward, how would you prioritize what gets captured first?"

▶ If the before/after comparison doesn't land cleanly, Lucas narrates explicitly: "Without the knowledge article, Friday gives you a generic answer. With it — it knows your specific situation."

▶ When Lucas is done: Fred takes back screen, returns to deck, advances to next slide.

Your Context

What lives in your head that should live in the system?

Name one piece of business context from YOUR role that only you (or Adam) know.

What happens when someone needs that context and you’re not available?

If Friday had that context — what would change?

Verbatim (7 min). "Lucas just showed you the mechanism. Now I want to connect it to your reality. Three prompts on the screen. We're going around the room."

Rebecca: "Rebecca — you're already building. What context did you give Friday for the configurator work? And what's the next piece you'd capture?"

Eden: "Eden — as steward, you see across the whole venture. What's the first piece of Venia context you'd want captured? What do people ask about repeatedly that shouldn't require a person to answer?"

Darren: "Darren — what do people always come to you about? Product specs, vendor details, pricing logic — what's the thing where you're the only source?"

Denise: "Denise — same question. What context do you carry that the team depends on? What happens when you're on vacation and someone needs it?"

▶ Go around in order. Each person answers at least prompt 1. Don't let Eden answer on behalf of others.

▶ Capture answers — these seed the team's capture priorities for the week. Note them for the post-session recap.

▶ If someone says "I don't know" or gives a vague answer, ground it: "Think about the last time someone Slacked you a question about your product line. What was the question? That's the context." Make it concrete.

"Good. What you just named — that's your capture list. Those are the first knowledge articles that should go into the Venia repo this week. Now let's make that official."

▶ Transition to Slide 9. The discussion should naturally flow into commitments.

Commitments

Every commitment maps to a milestone on your roadmap.

01 Complete setup if not done — GitHub, Claude Code, repo, identity. Stage 0-1 · Non-negotiable.

02 Run /start-day every workday this week. Stage 1 · The single biggest behavior change.

03 Capture one piece of real business context this week. Stage 2 · You just named what those would be.

04 Complete HQ survey if outstanding. Non-negotiable · Ten minutes. Due end of this week.

05 Stretch: capture 3 knowledge articles by next session. Stage 2 · If you're already building, this is your target.

Verbatim (10 min — highest-leverage section of the session). "This is the part where we turn everything we just discussed into something trackable."

"Every commitment you make here maps to a specific milestone on your adoption roadmap. When you complete it, your progress moves. Your teammates see it. The venture's maturity advances."

"Here's the menu."

"If you haven't completed setup — that's commitment one. Non-negotiable. GitHub account, Claude Code installed, repo cloned, identity configured. Stage 0. If that's not done, nothing else works."

"For everyone — run /start-day every workday this week. That's Stage 1. It takes fifteen minutes. You start your day in Friday, you see your inbox, you see what's happening across the venture. That's the answer to the time concern. You're not adding fifteen minutes to your day — you're replacing the fifteen minutes you currently spend piecing together context from five different places."

"Stage 2 — capture one piece of real business context this week. You just named what those would be. A knowledge article. A decision. A piece of product context that currently lives in your head. One. This week. And complete your HQ survey if you haven't. Ten minutes."

"Stretch — capture three knowledge articles by next session. If you're Rebecca and you're already building, this is your target."

Go around the room. Each person picks 1–3:

"Let's go around. Each of you — tell me which of these you're committing to. I'm logging them in HQ right now, and they'll show up on your roadmap."

▶ Log commitments in HQ live as they're spoken. Don't batch it for after the meeting — the act of logging in real time reinforces that the system is alive.

▶ If Darren's overdue commitment surfaces, acknowledge without pressure: "Darren, that commitment from Session 1 is still showing as in-progress. Want to update the target, or is that rolling into this week's commitments?" Don't chase — let him own it.

▶ If someone tries to commit to nothing or gives a vague "I'll try to get to it" — redirect firmly but warmly: "Pick one specific thing. It can be the smallest thing on the list. But it has to be specific and it has to happen this week."

"One more thing. Surveys — if you haven't completed yours, that's due by end of this week. Not optional. We need the data to support you properly."

▶ This is the highest-leverage 10 minutes of the session. Don't rush and don't skip. Commitments that don't get named publicly don't happen.

▶ Fred captures each person's commitments in the Venia HQ during the meeting — not afterward.