Approach

Every business is different, so we always start with a conversation.

How we work
About

We're a small London team of marketers, and we use AI to go faster.

About us
  • Cam BowenCam BowenCo-founder
  • Ben PowerBen PowerCo-founder
  • ElectraElectra
  • MahirMahir
  • NatashaNatasha
  • RahabaRahaba
  • ZobaerZobaer
Tool

Google Workspace

  • Our own workspace
  • Lead alerts in Chat
  • Read-only mailbox access
  • Docs and Sheets for reports

Where our own work happens. Mail, calendar, Docs, Sheets and Chat share one login, and a new website enquiry lands in a Chat space the moment it's saved.

  • 3alerts on every website lead: Chat, SMS and email
  • ~3 minfor a bot to answer a post in our Chat bus (8 Oct 2026)
  • ~405,000items on our shared drive before we cleared the code off it
  • 1build on it
Why we use it

Why we run on it

  • One login for the day

    Mail, calendar, Meet, Docs, Sheets and Chat sit under one domain and one set of permissions. Sharing a plan with a client is a link, not an attachment.

  • Lead alerts in Chat

    A website enquiry posts to a Leads space in Chat as soon as it's saved, next to an SMS and an email, so nobody has to check a sheet.

  • Agents write where we read

    Agents create and edit Docs and Sheets through a Google connection, so reports and plans land in the files the team already opens.

  • Meetings feed the CRM

    Gmail and Calendar sync onto each person's timeline in Twenty. Fireflies joins our Meet calls, and a bot turns the transcript into tasks.

  • Read-only by default

    Our mailbox connection is read-only and limited to named mailboxes. The Drive connection that searches and reads files is read-only too.

  • Drive for documents

    The shared drive holds documents, exports and call notes. Code lives in GitHub, because a sync client and git don't mix.

We run the agency on Google Workspace. Gmail and Calendar for mail and meetings, Docs and Sheets for plans and reports, a shared drive for documents, and Google Chat for the team. Sheets has its own page, because so many of our reports and so much of our data live there. Tasks sit in Twenty, and code stays in GitHub, out of Drive.

Where a new enquiry shows up

Our contact and landing-page forms post to an n8n workflow. It saves the lead to a Sheet and to our CRM, answers the form, and then raises the alert. Newsletter sign-ups get a Sheet row and a list subscription, and no alert.

Each new lead triggers:

  • A post in a Leads space in Google Chat.
  • An SMS to the two founders.
  • An email to our info inbox.

If part of the save fails, the form still goes through and a Chat post says which step failed. If your team lives in Slack instead, n8n can post the same alerts there.

Where the bots report

Our Grok Bot helpers post into Chat: meeting actions, site checks, release checks. One private space acts as the bus between the founders, the bots and our coding agents. A post wakes the bots at once, and a reply comes back in about three minutes (measured 8 October 2026). Chat is the live board. The record itself sits in the repo, the CRM or a pull request.

How our agents use Drive, Calendar and Gmail

  • Drive: agents can search and read files, and create or edit Docs and Sheets, so reports land where the team already reads.
  • Calendar: agents can read the founders' calendars to check availability and prepare for calls.
  • Gmail: a separate connection reads the two founders' mailboxes and nothing else. It's read-only and limited to a short list of named mailboxes.
  • Chat: history is copied to one machine for digests. Agents don't post to client spaces unless one of us asks them to.
About the tool

What Google Workspace is

Google Workspace is Google's business suite: Gmail, Calendar and Meet, Docs and Sheets, Drive and Chat, all under your own domain and one admin console. Plans are priced per user, so check Google's Workspace pricing page for what each tier includes.

Questions

Questions about Google Workspace

Straight answers on how we work, what it costs and what to expect. If yours isn't here, just ask.

Still have questions?

Talk to us
How do you plan and track client work?

We split each job into tasks, each with an owner and a date, on the task board in our CRM (Twenty). Code changes are tracked in GitHub as pull requests, and plans, notes and reports live in Google Docs and Sheets.

You don't need to log in to any of it. We keep you posted by email, on scheduled calls and in reports.

Read the full answer : How do you plan and track client work?
Can you send automation alerts into our Slack?

Yes. n8n can post an alert into a Slack channel: a new enquiry, a failed workflow, a form that didn't reach the CRM.

We keep alerts few and specific. Our own team gets them in Google Chat, by SMS and by email.

Read the full answer : Can you send automation alerts into our Slack?
Where next

Start with your numbers.

We'll tell you which tools you need and which connections are missing.

Next step

Bring your numbers.

We'll tell you if the spend makes sense.

  1. A 15-minute callYour goals, your challenges, and whether we're the right fit.
  2. A 1-hour discovery callWe dig into your numbers. Worth a hundred emails.
  3. A concrete planAds, a custom build or both, as a one-off project or ongoing.
15 minutes · No pitch deck · A straight answer