Discovery interviews

Ask the people doing the work how it really runs.

Short voice or chat interviews with the people behind the AI work we find. Short, on their terms, and what comes out is a written spec a company agent can be built from.

How it works

A conversation, not a form.

The interviewer asks, listens and follows up, the way a good analyst would. People can talk, type, or both.

  • Voice or chat, on a laptop or a phone — whichever suits the person
  • A visible agenda, so they always know where they are and what's left
  • Screen sharing, so the interviewer can see the work rather than imagine it
  • Pause any time and pick it up later; it ends only when they say so

Example interview

Why interviews follow detection

The logs show that AI is used. The person knows how the work runs.

Detection reads metadata, so it can tell you a job happens every weekday at nine and touches Xero and Outlook. It can't tell you what a good result looks like, or the exceptions only the person knows. That's what the interview is for.

01 · Detection

Finds the job.

Which tool, which systems, how often, on whose account. Enough to know a job is worth a closer look.

02 · Interview

Captures how it's done.

The steps, the judgement calls, the edge cases, and what "done" means to the person who does it every day.

03 · Spec

Becomes the agent's first draft.

Trigger, steps, tools, data and owner, written down. The company agent is built from it and tested against real cases.

The agenda

Four parts, in the order the work happens.

A requirements interview always follows the same shape, so the spec at the end is complete and comparable across teams.

01Intro

What you want built

The job in the person's own words, and what a good result looks like.

Captures → the goal and the owner
02Walkthrough

How it works today

Step by step, as it's done now — often with the screen shared.

Captures → the steps and the tools
03Detail

The details we need

Thresholds, exceptions, who gets told what, and when it shouldn't run.

Captures → the rules and the data
04Close

Wrapping up

A play-back of what was heard, and any systems still to connect.

Captures → the trigger and sign-off

What comes out

A written spec, ready to build from.

Every interview ends in the same five fields. The spec becomes the company agent's first draft, and stays attached to it as the record of what it's meant to do.

  • Trigger — when it runs
  • Steps — what it does, in order
  • Tools and data — which systems it touches, and how
  • Owner — who approves it and who it answers to

Trust

People know what they're taking part in.

An interview works because the person is open about how they work. That depends on being straight with them.

Before

Told before they start.

Everyone sees what the interview is for and who can read it before a single question is asked.

During

Read by owners and admins.

Interviews are visible to the workspace's owners and admins, so the company-wide picture holds together.

After

Never quoted to others.

The interviewer never repeats one person's answers to another. What someone says shapes the agent, not gossip.

FAQ

About interviews.

How long does an interview take?+

Short — most cover a single job. People can pause and come back to it, and it only ends when they end it.

Does everyone in the team get interviewed?+

No. We interview the people behind the jobs worth turning into company agents — the ones discovery surfaces, or the ones you choose.

Can people type instead of talk?+

Yes. Every interview takes voice or text, and people can switch between them as they go.

What happens to the interview afterwards?+

It becomes the written spec the agent is built from, and stays with the agent as the record of what it's meant to do. Owners and admins can read it.

Keep reading

Before and after the interview.

Book a demo

See the AI work already happening in your company.

Read-only access, nothing to install, first findings in days.