QuarterSmart

Our approach

Train your team. Automate the rest.

How we pick the new AI worth your time, set it up safely in accounts you own, and train your team until it's part of the day.

Being early only pays if people use it.

So every engagement has two halves, in this order. Training comes first because an automation is only as good as the people who check it.

First, train your team.

We train people on the new tool inside their own work, with their own examples, until it's part of the day.

  • Live Rollout Sessions built around each role.
  • Only on tools your team can actually use.
  • A prompt and workflow sheet everyone keeps.
  • A one-page guide to how you use each tool.

You work with our founder, Hyrum Hurst, directly. He is also CTO of Learning Journey AI, an AI education company, where keeping current on applied AI is part of the job. More about Hyrum

Then, automate the rest.

Then we take the repetitive work that's left and automate it, with agents and workflows your team can see and check.

  • Agents and automations in n8n, Claude or the tools you already use.
  • The steps your team already follows, written as procedures an agent can run.
  • A test period before anything runs on its own.
  • Documentation and a handover your team can operate.

Build is scoped after a Head Start or for members, once we know how your business runs. How Build works

Start with the first half.

Book a free 20-minute call

From announcement to in use.

Four steps, every week. The first two happen in public, in Signals. The last two happen in your accounts.

  1. 01

    Detect

    every day

    We watch model releases, product changelogs, early-access programs and credible reporting across the AI market.

    That means official blogs, changelogs and release notes from OpenAI, Anthropic, Google, Microsoft and Meta; the changelogs of common business tools such as Google Workspace, Microsoft 365, HubSpot, Slack, Zoom, QuickBooks, Canva and Notion; credible tech press; and public posts from the companies' own staff.

    We only cover information that's already public, and a person writes every Signal. How we source Signals

  2. 02

    Decode

    same business day for members

    Each Signal answers two questions in plain English. Does this matter to a business like yours? What should you do this week?

    Every Signal carries a status label for how sure we are: reported, confirmed, available, early access, quiet update or event. What the labels mean

    What to do Act now Prepare Wait Ignore

    Reported items stay labeled unconfirmed until the company confirms or denies them. We keep score in public on the Signals Log, misses included.

  3. 03

    Deploy

    from the day it's available to you

    When it's worth it, we set it up in your accounts, connect it to the tools you already use, test it with a few people, then train the team.

    Day one means the first day a tool is available to your account. We prepare beforehand wherever the vendor has published enough detail.

    Day One Setup
  4. 04

    Stay current

    every week

    Members get Signals filtered to their own tools, the same business day for anything that touches their stack, with setup time held for launch weeks. When a tool changes, we adjust your setup.

    Once a quarter we sit down with you for a Stack Review: what you pay for, what the team actually uses, and what to change next.

    First Quarter membership

Ask what's worth switching on this week.

Book a free 20-minute call

Principles

What we hold to.

  • We say "wait" more than "go."

    Most launches don't deserve your time. Wait and Ignore are common verdicts in Signals, and we'll tell you when a popular tool isn't right for you.

    In practice: we only recommend a tool once it passes the six questions below.

  • Your accounts, your data.

    We set tools up inside accounts you own, with the least access they need. If something shouldn't go near client or patient data, we say so before we set it up.

    In practice: you hold the logins, and you can remove our access at any time.

  • Plain English.

    If we can't explain why a launch matters to your business in two sentences, it doesn't go out.

    In practice: every tool we set up comes with a one-page guide to how you use it.

Six questions before anything gets a go.

A new tool has to pass all six before we recommend setting it up. Plenty of launches fail one. That's usually a wait.

Where we can, we try a tool ourselves before we recommend it.

  1. Does it do a job your team does every week?

    If we can't name the job and the person who does it, the answer is no.

  2. Can you use it now?

    It has to be available to your account, on the plan you have or one you'd actually pay for.

  3. Does it fit the tools you already use?

    Email, calendar, docs, CRM. A tool that can't connect to them rarely becomes part of the day.

  4. Is it safe for your data?

    Who can see what, where the data goes, and whether it needs to touch client data at all.

  5. Is it worth the cost and the learning time?

    The price per seat plus the hours to learn it, weighed against the time it gives back.

  6. Can you leave?

    You should be able to export your work and switch it off without losing anything.

Bring the tool you're weighing.

Book a free 20-minute call

Security basics

The rules for every setup.

Whatever the tool, these four apply from the first day.

  1. Least access.

    Every tool gets the smallest set of permissions it needs to do its job. If it only needs your calendar, it doesn't get your inbox.

  2. You own the accounts.

    Tools are set up in accounts your business owns and pays for. We work with the access you give us, and you can remove it at any time.

  3. A small, supervised test first.

    Every setup starts with 1 to 3 people before the whole team uses it. We fix what the test turns up, then roll it out.

  4. Nothing sends without your rules.

    You decide what an assistant must never send without a person approving it. During the test, a person approves every outgoing message.

Client and patient data. If something shouldn't go near it, we say so before we set it up. We don't connect a tool to protected health information unless the tool supports a business associate agreement (BAA) and you have one in place.

Start with what you already pay for.

The fastest wins are often in software you already have. Tell us what you use and what's eating your team's week. We'll tell you what's worth doing now and what can wait.

Not ready to talk? Read this week's Signals first.