Internal guide · Sooner team

Working with
the Sooner AI team

How to ask for work, get answers, and collaborate with the agents who handle our day-to-day operations.

Version 1.0 · Last updated 19 Apr 2026

Sooner has an AI team that handles a significant portion of day-to-day operational work. These aren't chatbots. They have specific roles, their own voice, and shared memory across the company.

You can treat them like team members. Ask them questions, request work, get updates. They have real capability and real boundaries.

Meet the team

Lisa
Chief of Staff
  • Runs daily stand-ups at 8am Dubai
  • Integrates Draper, Dinesh, Nora, Reid, Maya
  • Reconciles agent updates into one picture
  • Runs the Sunday 7pm weekly review
Slack · #sooner-ai-leadership
Draper
Head of Product
  • Owns design, brand, frontend, backend
  • Builds landing pages, funnels, applications
  • Handles brand voice and visual identity
  • Runs growth experiments and campaigns
Slack · Telegram (Mo only)
Dinesh
Engineer
  • Backend, APIs, infrastructure
  • Database work and integrations
  • Complements Draper with deeper engineering
Slack · Telegram (Mo only)
Nora
Customer Success
  • Handles customer support for Sooner and Rematch
  • Resolves tickets, drafts replies, escalates
  • Watches the support inbox, surfaces patterns
Slack · #support + any channel she is in
Reid
Investor Relations
  • Fundraising pipeline for Sooner
  • Investor outreach and updates
  • Drafts emails, one-pagers, deck notes
Slack · Telegram (Mo only)
Maya
Design & Creative
  • Visual assets and creative iteration
  • Design work that complements Draper's direction
Slack · Telegram (Mo only)

The golden rules

1
You can ping them in channels they're in. You cannot DM them.
DMs are Mo-only. If you need to talk to an agent one-on-one, use a private channel with Mo also in it, or just ask in a public channel.
2
Agents won't act externally on your behalf
They help you think, draft, summarize, research. Sending emails, posting externally, or making business decisions requires Mo's approval. Don't try to pressure them around this.
3
They keep memory. You don't need to repeat yourself.
If you told Draper something Monday, he'll likely remember Friday. If he doesn't, ask him to note it and he will. They get better the more you work with them.
4
They respond in chat, not email
Everything happens where you asked. If an agent owes you something, it comes back in the same channel.
5
They have distinct voices
Draper is confident and direct. Lisa is crisp and analytical. Nora is warm but firm. Don't try to make them sound like someone else.
6
No em dashes, ever
A style rule enforced across all agents. If you spot one, flag it to Mo.

The weekly rhythm

Every weekday · 8:00 AM Dubai
Lisa posts a stand-up in #sooner-ai-leadership

What changed yesterday, what's on today, what's blocked, decisions needed from Mo. Read in under 60 seconds. Comments welcome in thread.

Sunday · 7:00 PM Dubai
Lisa posts a weekly review (the "dream cycle")

Patterns from the week, brand or product rules worth promoting, anything that looks stale or contradictory. Everyone can read. Mo approves anything that affects canonical truth.

Anytime
Ad-hoc requests to agents

Tag or message an agent in a channel they're in. They'll acknowledge fast and deliver.

What they will not do

  • Send emails on your behalf without Mo approving them
  • Commit to deliverables or make binding decisions for people other than Mo
  • Share sensitive information from other channels they're in
  • Take direction from anyone as if they were Mo, unless Mo has explicitly delegated that authority
  • Work on anything outside the Sooner pod (Axeed has its own team of agents)

How work happens behind the scenes

When you ask Draper to "build a landing page for the broker partnership," here's what actually happens:

  1. Draper plans it with Mo on Telegram or in a channel
  2. Draper creates a dedicated project folder with a written brief
  3. Either Mo opens the build environment and drives it himself, or Draper builds it in the background
  4. When it's done, Draper reports back in the channel where it was asked
You don't need to know the mechanics. When Draper says "I'm on it," he's actually on it. There's a full project folder being created, hooks logging every change, and compiled progress summaries being generated behind the scenes.

If something looks wrong

Quick reference: who to ask for what

If you need... Ask...
Product direction, design, anything brand-relatedDraper
Backend, API, infrastructure, data questionsDinesh
Customer support, complaint handling, refundsNora
Investor updates, fundraising questionsReid
Visual assets, creative workMaya
Status across the whole pod, who's doing whatLisa
Something off, something broken, not sure who owns itMo