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
AI by company size · Medium, 20 to 200 people

Where to start with AI when you have 20 to 200 people

  1. Would it terrify you to know your competitor's sales calls were summarised, scored and in the CRM before the rep had put the kettle on?
  2. Would it terrify you to know your competitor's monthly report wrote itself, and their team spent that week on the work instead?
  3. Would it terrify you to know your staff are already using AI at work, with no shared rules, and your competitor has written theirs down?

What companies your size are already doing

Among firms that reported barriers, the ONS found a lack of expertise was one of the most common, and about 18% of firms with 100 to 249 staff said it had held them back from using AI (ONS, 20 July 2026). That's why rules and ownership come first.

Source: Office for National Statistics, "Artificial intelligence in UK businesses: 2023 to 2026", 20 July 2026.
  1. Effort Days

    Every sales call summarised into the CRM

    The call's recorded and transcribed, and a summary, the actions and the next step land on the right record.

    Stays human The follow-up message. A person writes it.

    ProofFirefliesTwenty Our Meeting Intel bot does this for us: it reads each meeting, writes notes and tasks, and doesn't send anything.

  2. Effort Weeks

    Reporting that writes itself

    The numbers get pulled together and a first draft of the commentary is written. Then a person adds the "so what".

    Stays human A person decides what the numbers mean and what to do next.

    ProofOngoing reportingMeasurement treated as the product

  3. Effort Days

    Shared AI rules for the whole team

    One short written rulebook: which tools are approved, what data never goes in and who checks what. It's loaded into the tools themselves, so it gets followed instead of filed away.

    Stays human Agreeing the rules, and owning the exceptions.

    ProofHow we run one rule set across two AI tools

  4. Effort Days to weeks

    Automations replacing admin busywork

    n8n and AI handle data entry, sorting and handoffs: a form comes in, a record's created, a task is set and the right person gets an alert.

    Stays human Anything that needs judgement goes to a person. So do errors, instead of disappearing.

    ProofOur own forms-to-CRM flowTwenty and n8n

Show 4 more
  1. Effort Days

    First-draft proposals from the call

    After a discovery call, a proposal outline is drafted from the transcript and your past work, ready for a person to rewrite.

    Stays human Scope, price and promises.

    ProofFireflies

  2. Effort Weeks

    "Ask our docs" for your own team

    One searchable place where your staff can ask how a process works and get an answer with a link to the source.

    Stays human Keeping the docs accurate. Every page has an owner.

    ProofOur own stack docs, searchable, with an Ask AI index

  3. Effort Days

    Launch checks before every campaign

    Before any money's spent, your tracking, consent settings and forms are checked, and anything broken gets listed.

    Stays human Signing off the launch.

    ProofTracking that proves a purchase

  4. Effort Days to weeks

    Lead triage to the right owner

    New leads are read, tagged by type and urgency, and routed to the right person with a short brief.

    Stays human The relationship. Anything unusual goes to a person first.

    Proofn8nSeparating audiences so each gets the right journey

First step this month

Write your one page of rules before you buy anything. List the tools people already use, what data must never go into them, and who checks what. Then pick one job you repeat (usually getting call notes into the CRM) and make it work for one team before you roll it out. If your tracking and CRM data are messy, fix that first, because AI on bad data gives you confident wrong answers.

Not yet

  • Don't roll out an AI tool across the company until you've got rules and an owner.
  • Don't build agents that act on their own (sending, spending, publishing) until your repeated jobs run well with a person checking.
  • Don't judge success by how many people logged in. Measure the one job: time saved, errors, how fast you reply.
Three questions for anyone who offers to help, us included
  1. Which of our systems will this connect to, and what can it change without asking a person?
  2. How will we know when it's wrong, and who gets told?
  3. When you leave, what do we keep: the rules, the workflows, the logins, the documentation?

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