Winning the work — Sofia's first email to a won deal¶
Let's follow a real journey. Sofia Lind runs operations at a growing company called Marren. She's heard about Studio OS and wants it for her own business. One evening she sends a short, slightly vague email to your studio:
"Hi — we've been hearing a lot about what you're building. We'd love to bring Studio OS into Marren and get your help rolling it out. Can we talk?"
Here's what happens next — and, just as importantly, what you see while it happens. You are the operator. Your AI team does the work; you make the calls.
1. The email is understood, not just received¶
Sofia's message lands in your shared inbox. Studio OS reads it immediately and asks one question: is this about work we're already delivering, or is it something new? It's new — a fresh inquiry from someone you've never heard from — so it goes to Kairi, who owns new relationships.
On your screen: nothing interrupts you. A quiet line appears in the live activity feed on the side of the dashboard — "New email · handed to Kairi" — the way you'd notice a colleague pick up a ringing phone across the room. No decision is being asked of you yet.
What Kairi is thinking: "This person doesn't exist in our records yet, but the message is a genuine inquiry about what we offer. First I'll create a proper lead so there's a record to build on. It reads promising — a real company, a real intent — so I'll mark it qualified. Now, can I write a proposal? Not really: she hasn't told me team size, timeline, or budget. Rather than guess, I'll draft a short, warm reply asking the two or three things I actually need — and I'll flag it for the operator to review."
2. A decision arrives — cleanly¶
A moment later, your attention is requested — once, and clearly. A notification appears, and on your dashboard a card slides into the queue of things that need you:
┌──────────────────────────────────────────────────────────────┐
│ Kairi · Reply to Sofia Lind (Marren) ● today │
│ ─────────────────────────────────────────────────────────── │
│ Why: New inquiry about adopting Studio OS. The brief is too │
│ thin to quote, so I'm asking for team size, timeline, and │
│ current tools before drafting a proposal. │
│ │
│ Draft: │
│ "Hi Sofia — lovely to hear from you. To shape the right │
│ rollout, could you tell me: how many people would use it, │
│ when you'd want to start, and what you use today for email │
│ and accounting? …" │
│ ─────────────────────────────────────────────────────────── │
│ [ Edit ] [ Reject ] [ Approve ⏎ ] │
└──────────────────────────────────────────────────────────────┘
This card is the heart of Studio OS. In one glance you get the reasoning ("why am I being shown this?"), the exact words that will go out, and three choices: send it as-is, tweak it first, or reject it. Rejecting asks you why — and Kairi remembers, so the next draft is better.
Your move: you read it in five seconds, change one phrase to sound more like you, and approve.
3. It sends — and you can breathe¶
The moment you approve, the email goes out to Sofia, in the same thread, looking exactly like it came from you. The card animates from needs you to sent, and the live feed notes it.
The important part is what you didn't have to do: you didn't open your email client, didn't find the thread, didn't write from scratch, didn't worry about tone. You reviewed a decision and made it. That's the whole rhythm of Studio OS — glance, understand, decide — and it repeats for every meaningful thing the company does.
4. Sofia replies — and the deal turns real¶
A day later, Sofia writes back:
"Team of about 12. We'd like to start next month, and budget's approved — let's do it."
Studio OS reads her reply, recognises it as part of the same conversation, and hands it back to Kairi.
What Kairi is thinking: "She's answered everything and given a clear go-ahead. Team size, timeline, budget — all there, and an explicit 'let's do it.' This deal is won. I'll record the details and move her from a prospect to an active client."
On your screen: on the pipeline board, Sofia's card slides from Qualified into Active. This is the good moment — the "we won" moment — and Studio OS makes it a real, visible event rather than a quiet database change.
5. Winning becomes doing¶
A won deal is a promise to deliver something. So Studio OS marks the moment where a relationship becomes delivery work: it confirms the win with you, opens a project for Marren, and hands it to Madis, your project manager, with a clear brief — "This deal is won. Kick off the Studio OS rollout for Marren: scope it, set a plan, decide the first step."
On your screen: a project appears — "Marren — Studio OS rollout" — with its own page, and the feed shows the baton passing from Kairi to Madis. Sofia is no longer just someone in your pipeline; she's a project underway. From here on, when Sofia writes about the work, Madis picks it up — the whole conversation stays with the person who owns the delivery.
What just happened¶
In two short exchanges and two clicks from you, a cold email became:
- a qualified lead, with a full record,
- a reviewed, sent reply,
- a won deal,
- and a live project with an owner and a brief.
Everything in between — reading, understanding, drafting, following up, recording, handing off — your AI team did on its own, and every step is on a timeline you can read back. You were the operator, not the operator and the assistant and the typist.
Next, we follow the project itself: how Madis runs the Marren rollout — the actual tasks, how the communication flows (including with your own teammates), and how the project moves from kickoff to done.