WebLife × FridayOS — Venture Onboarding

Venture Onboarding · Session 1

WebLife × FridayOS

Today we start using it together.

Hosted by Fred Butson · Lucas Robinson

Team Adam Burdeshaw · Thushan Fernando · Bihani Madushika · Dr. Yashoda Velananda · Upeksha Liyanage · Saduka Sachintha · Hafiz Mudasir · Sasindee Wijeratne · Shenali Edirisinghe

Where We Are Today

Last session was the introduction.
Today we start using it together.

Adam is operating in WebLife's CompanyOS already. Saduka has experience too. Most of you haven't been onboarded yet — and that's exactly what this week is for.

Today's job: show you what operating in FridayOS actually looks like, point you at the onboarding resource, and walk out with a real commitment.

No pressure to be fully set up by the end of this call. Setup happens this week, supported by the group. Nobody is left behind.

Verbatim (90 sec). "Quick reset on where we are. Adam is operating in WebLife's CompanyOS — he's been ahead of the curve. Saduka has some experience too. Most of you haven't been onboarded yet. That's expected. That's why we're here this week."

"Today's job is three things — show you what operating in FridayOS actually looks like, by example. Point you at the onboarding resource so you know where to go this week. And end with each of you having a real commitment for the week ahead."

"You don't need to be fully set up by the end of this call. Setup is something we'll do this week, with the group helping each other. The principle is — nobody is left behind. If you hit a wall, we work through it together."

▶ Acknowledge the reality openly — pretending otherwise breeds anxiety. Most of the room is mid-onboarding; that's the truth.

Two Places, Two Purposes

FridayOS is where we build.
HQ is where we operate as a team.

FridayOS — build

CLI-based. Claude Code, Codex, whichever LLM. Context lives here. Feeding it context is the proactive habit — the more it has, the more it can connect.

HQ — operate together

Commitments are logged here. We access each other here. We build momentum, get unblocked, and share what's working — here.

Complementary, not interchangeable. Building extraordinary things downstream depends on the context you feed Friday upstream.

Verbatim (90 sec). Repeat this often through the session — it's the spine.

"Two places, two purposes. FridayOS is where we build. CLI-based — Claude Code, Codex, whichever LLM you use. The context lives here. The proactive habit you're building this week is feeding it context. The more it has, the more it can connect — and the less you have to re-explain yourself every time."

"HQ is where we operate as a team. Commitments are logged here. We see each other's work here. When you're stuck, that's where you message the group. When you find something cool, that's where you share it. It's the team layer."

"They're complementary, not interchangeable. Today reinforces both. Building extraordinary things downstream depends on the context you feed Friday upstream."

▶ Come back to this slide whenever someone confuses the two. Repetition is how it sticks.

friday.overview

friday.foundations

60-second calibration —
so we're all using the same vocabulary.

A single place where your team's goals, projects, meetings, and decisions live.
An AI partner (Friday) that reads the context and helps your team operate — not just chat.
A platform your team can build inside of — not just use.

The Directive

Get the context out of any one head —
into a place the team can use it.

Recent surveys surfaced something the whole team felt — a single person becomes the bottleneck for too many decisions and contexts. That's the natural ceiling of human cognitive load on a team this size.

AI carries that load now. The point of everything we're about to do is to get the context out of any one head and into a place where the whole team can see it, build on it, and plan with it.

So when we ask you to capture context this week — that's why. Every piece you feed Friday makes the team's collective intelligence compound.

Verbatim (2 min). This is the "why" — don't rush. "I want to surface something that came up in the recent team surveys, because it's the reason we're doing this with urgency. One person on a team this size naturally becomes the bottleneck for too many decisions and contexts."

"That's not anyone's fault. It's the ceiling of what one person can hold. AI carries that load now. The point of everything we're about to do — every piece of context you capture, every team message you send in FridayOS, every decision you drop in — is to get the context out of any one person's head and into a place where the whole team can see it, build on it, and plan with it."

"This is why we're doing this together as a team, all at once. If only one person captures context, FridayOS knows about one person's work. If everyone does, Friday becomes the team's shared brain. That's the goal we're working toward."

▶ Don't put a spotlight on Adam by name. The team knows who carries a lot. Frame it as the organizing problem, not anyone's failure.

Where We're Headed

What ultimately needs to be true for WebLife.

Context

It lives where the team can use it.

Decisions, learnings, blockers — captured in FridayOS as you go. Not stuck in someone's head. Not buried in Slack threads. Friday reads across all of it.

Visibility

Everyone sees how others' work affects theirs.

When you go to plan, you see what's happening across the team. Friday connects threads you didn't explicitly link — and your planning gets sharper because of it.

Unblocking

No one person is the choke point.

Decisions move forward without routing through one person every time. Friday holds the context. People build with clarity. Cognitive load is shared.

Verbatim (90 sec). "This isn't a week-by-week roadmap. We're not telling you 'in week three you do X.' This is the direction — what ultimately needs to be true for WebLife once we're operating well together."

"Context lives where the team can use it. Decisions, learnings, blockers — captured as you go, in FridayOS. Friday reads across all of it. Stops being stuck in heads and Slack threads."

"Everyone can see how others' work affects theirs. When you go to plan, you can see what's happening across the team. Friday connects threads you didn't explicitly link. Planning gets sharper."

"No one person is the choke point. Decisions move forward without routing through one person every time. People build with clarity. The team operates faster because cognitive load is shared."

"And ClickUp doesn't have to go away. We're adding a context layer above the work, not retiring everything you use today. If/when ClickUp doesn't earn its keep anymore, we'll know."

▶ Don't promise a date. Promise a direction. The team paces itself toward this.

friday.live-walkthrough

Lucas walks us through.

Folder structure orientation — what lives where, why it's organized this way.
Sending a message inside FridayOS — live demo. Where it lives. What the recipient sees.
Interacting with others' messages — replying, referencing, picking up a thread.
Capturing context — a real decision, learning, or blocker. Watch Friday absorb it.
How Friday connects the dots — the moment two pieces of context link up. This is why we capture.

Hand-off to Lucas. "Lucas designed a lot of how this works — the repo, the folder structure. He's going to walk you through some high-impact get-started moves from his own setup. Lucas, take it away."

Note for Lucas to say once, early: "I'm using Zed. The onboarding instructions reference VS Code. Claude Code Desktop also works. Pick whichever — they're all pointing at the same thing. This is just what I happen to use."

Demo target (30–40 min): the five things on this slide. Land at least one "oh — that's what this does" moment. The "Friday connects two pieces of context" moment was pre-picked in the huddle — that's the highest-leverage beat.

Adam available for any WebLife-specific question — no presenting pressure on him. Lucas can pull him in if needed.

▶ This slide is a divider, not a script. Lucas drives content. Watch the room — if someone looks lost, slow down.

Open Floor

Where are you stuck?
How peer help works.

The onboarding resource is in HQ → Resources. If you haven't been through it yet, that's where you go. The full setup guide lives there.

If you hit a wall after this call — message the group in HQ. Don't DM me first. The group is your first stop. People in this room have done this and can help.

Visible struggle is visible learning. Somebody seeing your question will be glad you asked.

Open the floor (15–20 min). "Where are you stuck? What didn't make sense?"

"For anyone not yet set up — the onboarding guide is in HQ → Resources. That's the standard. If you can't find it, raise it now and we'll point you at the right place."

"Here's how peer help works going forward: if you hit a wall after this call, message the group in HQ. Not me first. The group. People in this room have already done this and can help. Visible struggle is visible learning — and somebody seeing your question will be glad you asked."

"Watch the room. If someone is quiet and looks lost — name it gently. 'How are you feeling about this so far?' — better than letting them leave silently confused."

▶ Don't move on until everyone has a path. Session ends when everyone knows their next step.

Real Progress This Week

Each person picks one.
Logged in HQ.

01 Get fully set up + run my first start-of-day in Friday. Where everyone should land if they're not set up yet.

02 Get fully set up + send a substantive team message via FridayOS. Not a "hello." Real context, to a real teammate.

03 Capture three real pieces of context from this week into Friday. A decision, a learning, a blocker — whatever's true.

04 Bring one decision I'm wrestling with into Friday. Let it think with you. See what it surfaces.

Verbatim (10–15 min — this is the close, don't rush). "Last thing. I want each of you walking out with a real commitment for the week. Real progress, not box-ticking."

"If you're not set up yet — commitment #1 is the obvious one. Get fully set up and run your first start-of-day in Friday. That's where everyone should land if you're not there yet."

"If you're set up — raise the bar. Send a substantive team message. Capture three pieces of context this week. Bring a real decision into Friday and let it think with you. Pick the one that lines up with what's actually in front of you."

"Open the room now. Go around — each person names their commitment. Each person individually. Don't let one person answer for two."

"Wherever you are, log your commitment in HQ before you leave this call. Not afterward. Now. That's the standard. HQ is where we operate as a team — commitments live there."

▶ Highest-leverage 15 minutes of the session. Commitments named publicly + logged in HQ are commitments that stick. Skipping = the session didn't land.

▶ Fred (or designate) captures each person's commitments live in HQ during the meeting — not afterward.

weblife.standard

weblife.the-standard

We are building.
That's the standard.

FridayOS is where you build. HQ is where we operate as a team. Two places, two purposes.
The proactive habit in FridayOS is feeding context. The more it has, the more it can connect — the less you have to re-explain.
Stuck? Message the group in HQ. Peers help peers. Visible struggle is visible learning.
Found something cool? Share it in HQ. A feature, a release, a way of working. Inspire each other.
Momentum is visible by design. People build — others see them building — others get inspired and build. That's the loop.

The cultural close (3 min). Said out loud, slowly.

"Two final things before we end."

"One. Two places, two purposes. FridayOS is where you build — in the CLI, with whatever LLM you use. HQ is where we operate as a team — commitments, access to each other, momentum. Hold those distinct in your head."

"Two. The standard we're setting today. If you're stuck, message the group in HQ. If you find something cool, share it in HQ. If you're building something, others should be able to see it. Momentum is visible by design. People build, others see them building, others get inspired and build. That's the loop we're starting."

"We are not checking boxes because Fred or Lucas said to. We are building. That's the standard."

Close-out. "Calendar invite for next session is going out. If you hit a wall this week — remember, the group in HQ first. See you next week."

▶ This is the moment that sticks. Don't read it — mean it. Eye contact. Slow.