Product update

New in Vythos: Built for Your Whole Team

Each client's memory kept apart, the Playbook for every role, someone to look after each client, and AI suggestions that reach the right person.

Vythos started as one person's tool. The owner wrote the rules, the owner approved what Claude suggested, and everyone else's AI tools followed along.

That works until the agency has more than one account manager. Then the owner becomes the bottleneck for every client's rules, and the person who actually knows Northwind can't fix Northwind's.

This week's release is about that. Your team can now share the work of keeping the rules right, without everyone getting the keys to everything. And before any of that, one change that matters even if you work alone.

Each client's memory, kept apart

Until now, a question about Northwind searched everything you had, and the passages that read most like the question came back. Usually they were Northwind's. Sometimes they were Bramble's, because Bramble's brief used the same words.

Now everything in memory is filed under the client it belongs to, when something says whose it is:

  • A folder with the client's name, in Drive or in an upload
  • A line near the top of a document: Client: Northwind
  • The source itself: Notion's Client property, a Slack channel named for the client, Harvest's client, a Basecamp project
  • Who it's with: emails, meetings and call recordings with people at the client's email domain

A question or a draft about Northwind then reads what's filed under Northwind and what's filed under nobody. It never reads what's filed under another client.

Vythos is careful about the label. It never creates a client from something it read, a passing mention isn't enough, and anything two clients have a claim to is filed under neither.

Their email domains

An email has no folder, so Vythos goes by who it's with. Under About {client}, at the bottom, add the part of their addresses after the @: northwind.com. You can paste a whole address or their website. From then on their emails, meetings and calls are filed under them, including the ones already synced.

Something seems missing from an answer? Ask again without naming the client, and everything is searched as before.

The Playbook for every role

Everyone on your team now has the Playbook page. Each person sees the clients they work on and the kinds of rules shared with them, and only the buttons their access allows. A page someone can only read says, in one line, who changes it.

Someone to look after each client

On Members, open a person's access and pick the clients they look after. Usually that's the account manager. For those clients they can:

  • add, change and retire the client's rules
  • keep what's true about the client, under About {client}
  • see the client's AI activity
  • answer what teammates suggest for the client

Two things stay with whoever can edit them: Pricing & rates and Terms & commitments. A line that states money still needs the person who looks after pricing.

Until you choose someone, you look after every client, so nothing changes until you decide it should.

Suggestions that reach the right person

When someone corrects their AI tool, "Northwind never wants emojis", the tool can suggest it as a rule. Until now every suggestion waited for the workspace owner.

Now it goes to whoever could add it themselves: the people who look after that client, or whoever can edit that kind of rule. They can Add it, Edit it first, or Decline it with a reason.

The person who suggested it sees it waiting, can withdraw it, and then sees what became of it for two weeks: added, declined and why, or expired.

At 8am UK, anyone with new suggestions waiting gets one short email listing them. Only on days when there are some. It links to the Playbook; nothing is answered from the email, and you can turn it off in Your data.

Members can suggest from the start. Freelancers can once you raise one of their levels. And nothing a teammate's tool suggests reaches anyone's AI tools until someone who could add it says yes.

Also new

  • GitHub. Connect a repository from Sources and its README, docs and issues go into your memory.
  • Invites keep your choices. The access you set for each category when inviting someone is now what they get. Before, the role's defaults won.
  • Google Calendar says why. A sync that fails now tells you the reason, instead of just "1 failed".

What it doesn't do yet

Being straight about the edges:

  • Memory is filed only when something says whose it is. A note that only mentions a client stays unfiled, and is read for every question.
  • Each person's memory is still their own. Filing it by client doesn't share it with colleagues.
  • Choosing who looks after a client is the owner's job. Adding clients and their email domains stays with owners and leads.

The one thing

Open Members and choose who looks after your busiest client. That one change takes the most rule edits off your desk.

More from the blog

Guide

How to Write a Scope of Work Clients Sign

A scope of work that stops creep before it starts: deliverables, exclusions, milestones and change control, with a free generator.

· 4 min read

Guide

How to Write a Campaign Brief That Works

80% of marketers think their briefs are good; 10% of agencies agree. What a campaign brief needs, and a free generator and template.

· 4 min read

Guide

How to Price Your Agency's Services

Work out your floor rate, choose hourly, project or retainer pricing, and check your rates by region, with a free pricing generator.

· 4 min read