Where it fits

Building is the easy part. Knowing where it pays is the work.

Most of the work isn't building. It's knowing where AI pays.

Why start there?

Because you've been pitched, but nobody has looked at your week.

Every owner has seen a demo. Few have been shown where it would earn its keep. That's our first question.

Which parts of a business do you look at?

All six departments, in any industry.

• Sales: enquiries that wait overnight, and promises that slip.
• Finance: late payers, approvals and a slow month end.
• Operations: suppliers, open orders and the morning inbox.
• HR: applications, new starters and the routines that keep a team steady.
• Customer service: client paperwork, and the same questions all day.
• Marketing: the client letter, and which channel really pays.

The same patterns turn up in accounting, insurance, wealth management, staffing, distribution, manufacturing and construction.

Where do you begin?

We follow the work, not the org chart.

We start with how work really moves. Who asks for what, where it waits, who chases it.

Then we trace a few chains end to end. An order to a delivery. A yes to a set-up client. A topic to a sent letter.

Each chain stalls somewhere. Usually a person is reading, checking or chasing by hand. That's where we look first.

We also look at you. Owners carry promises, decisions and routines in their heads. Some of it slips in a busy week.

What kind of work suits it?

Reading-heavy work that follows rules.

• reading a pile of mail and lifting out the few that need a person;
• checking a returned form for blanks, signatures and dates;
• comparing what arrived with what was ordered;
• noticing a promise or a routine, and remembering its date;
• drafting a first chase note for someone to approve;
• spotting a broken pattern and saying “worth a look”.

A good assistant could do each of these with enough hours. The hours are the problem, and that's where it pays.

And when doesn't it?

Some work is the wrong fit, and we'll say so.

• decisions that need judgment you'd never hand over;
• processes that already run well;
• a missing policy or a missing hire, dressed up as a software problem;
• volumes too small to justify building for;
• data too messy to read reliably yet.

We'll tell you when AI is the wrong answer. Sometimes the fix is a checklist, a clear owner or a tool you already pay for. Better to hear that from us than to pay for a build you don't need.

Will it act on its own?

No. What we build reads, drafts and warns.

A person approves before any message leaves. When something might be wrong, it says “worth a look” and stops. It never acts in your name.

What happens in the first conversation?

An hour with one of our co-founders, at no cost.

• No access. We don't ask to see your systems or your mail.
• Nothing to prepare. No documents needed.
• Your whole list. Bring the problem that brought you here, and every other one.
• Questions about your week. Where work waits, who chases, what lands on you after hours.
• Names at the end. The problems worth solving, in plain words. And the ones that aren't.

There's no pitch at the end. If nothing is worth building, you'll hear that. If something is, the next step is yours.

You use AI where it counts and ignore the rest. Your people spend their week on the work that needs them.