FlowsBook a callSign inCreate free accountSign up
AI employees and automation

How to hire an AI employee, from picking the job to its first run

How to hire an AI employee in a few minutes: pick the job, answer its questions, check what it will do, watch the first run, and know when to change it first.

Part of the guide AI employees

By the xMap team · · 5 min read

Here is how to hire an ai employee in practice: choose one repeating job, pick a ready-made AI employee that does it, answer the two or three questions it asks (usually where and what), read what it will do, and press Hire. It takes its first look straight away and then keeps working on its timetable. If the job is not quite right, open it in the editor before it starts, change it, and deploy it yourself.

This guide is for anyone setting up their first AI employee, or their tenth, and wanting it to work from day one. It goes through choosing the job, the hiring window step by step, a made-up example, the checks to do in the first week, and the mistakes that make a new hire disappoint.

Start with the job, not the tool

Hiring a person starts with a job description. Hiring an AI employee does too, only shorter. Write one sentence with four parts: what it looks for, where, how often, and who gets the result. "New dental clinics in Lisbon, every Monday, to the sales lead" is a job. "Help us grow" is not.

Good first jobs share a few traits. Someone already does them by hand. They repeat on a rhythm. A good result is easy to recognise. And a weak week costs little. Lead lists, competitor openings, road closures near sites and weekly market notes all fit.

Three ways to hire

  • From a template. The Templates page lists ready-made AI employees by industry and use case. Each card has a Hire button.
  • From your website. Give your company's website when you start, and xMap reads it and proposes a few AI employees that fit your business, each tried on live data first.
  • From a two-minute interview. Answer five short questions (your business, website, city, main goal and how you want results) and xMap proposes a small team.

All three end in the same hiring window, so the steps below apply to each.

The hiring window, step by step

  1. Answer its questions. Most AI employees ask where to look and what kind of place to look for. If xMap already knows your city or the kind of place you work with, it fills them in and says so. Change anything that is wrong.
  2. Say it your way, if you like. A box at the top takes a sentence such as "Toronto and Ottawa, Mondays at 9, to Slack". It fills in the answers and the timetable from it.
  3. Read What it will do. It lists the steps in order, when it works, where results go, and roughly what a run costs. Apps you have not connected yet are left out and named, and results come by email instead.
  4. Press Hire. It takes a first look straight away, then starts working on its timetable. Its card appears on the Flows page, marked as new.
  5. Or press Change it first. This makes the flow with your answers and opens it in the editor without starting it, so you can adjust blocks before you deploy.

A worked example

This example is made up. Joon-ho manages sales for a coffee equipment supplier in Seoul. He wants to hear about cafes that open in the districts his team covers, before competitors visit them.

He opens Templates, filters by Restaurants and cafes, and picks an AI employee that finds new places each morning and sends only the ones it has not sent before. The window asks two things: the city (Seoul, filled in from his time zone) and the kind of place (he picks Coffee shop). He types "weekdays at 8, to me" in the box. What it will do now reads: every weekday at 08:00, search Seoul for coffee shops, keep only new ones, rank them, email Joon-ho. He presses Hire.

A minute or two later its first look has finished and he can open the cafes it found. The next morning the first email arrives. At the end of the week he notices it includes chains he never sells to, so he replies in its Team inbox thread: "leave out chains". It changes itself and tells him what it changed.

The first week: what to check

  • Is it finding the right things? Open three or four results. If they are off, the kind of place or the area needs adjusting.
  • Is it finding too much or too little? Too much usually means a filter is missing (a minimum rating, independents only). Too little often means the area is small or the kind is too narrow.
  • Is it reaching the right person? Check the email address or channel. A list that lands in the wrong inbox is wasted.
  • How much does it do alone? If it writes to people outside your company, consider setting it to ask you before anything goes out.
  • Does its budget fit? Each AI employee can have a monthly budget, with a warning before it runs out.

Mistakes to avoid

  • Hiring five at once on day one. Start with one or two, get them right, then add more. A quiet inbox with useful results beats a busy one you stop reading.
  • Accepting the example city. Templates are written with a sample city. Check the place before pressing Hire.
  • Skipping What it will do. It is the job description. Thirty seconds reading it saves a week of wrong emails.
  • Editing without a test. After changing it in the editor, run a test first. A test run never sends anything.

What a hired AI employee is made of

Behind the card, every AI employee is a flow of blocks. Joon-ho's is a Schedule, an Area of interest, Nearby places, Only new, xMap LLM to rank, and Email. Knowing this helps when you want to change it: you can see exactly which step to touch. The template he used is New places every morning, only new; for a sales team, Morning call list with decision makers and call notes adds who to call.

Once it is working, its notes arrive in the Team inbox, its weekly report card shows what it found, and you can rename it so the team knows which one is which. For the bigger picture of roles and jobs, see the AI employees guide.

Questions

Do I need to know how to build flows to hire one?

No. Hiring from a template only asks a few questions. The editor is there if you want to change it, but you do not need it to start.

What happens if an app it uses is not connected?

That step is left out and named in the window, and results come by email. Connect the app later and switch the step back on.

Can I fire an AI employee?

Yes. Pause it with one click, or archive it. Its runs and results are kept, and you can bring it back.

How long until the first result?

Its first look runs when you press Hire, usually within a minute or two. After that it works on the timetable you set.

Templates that do this

Read next

More on ai employees and automation · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.