The short answer.

A new function, such as a first marketing team, a first people function or a first customer success team, has no habits to change, so you write its way of working with AI into it from the first day. List the five pieces of work the function will repeat, write a first workflow for each from general good practice adapted to your business, decide what a person decides in each, and name who owns the function until the first hire arrives. The first hire then inherits a working function and improves it, instead of inventing one alone.

A new function has no habits to change.

Building AI into a new function is easier than building it into an established one, because a new function has no old way of working to unpick. Whatever you write down first becomes the way the work is done.

The risk in a new function is the opposite one. Without a written way of working, the first hire builds the function from their last employer’s habits and their own tricks with ChatGPT, Claude, Copilot or Gemini. You get a function that works the way one person works, with AI use undirected from the start. Writing the workflows first gives the function a disciplined shape before anyone fills it.

List the five pieces of work it will repeat.

Every new function repeats a small number of pieces of work, and five is enough to start. Write each with a clear start and a clear result. Here is a first list for three common new functions.

  • A first marketing team.A profile of the customer you sell to, a description of the offer, a monthly content plan, a draft of each campaign email, and a review of what the last campaign produced.
  • A first people function.A job description and interview pack for each opening, an onboarding plan for each new starter, answers to staff questions about company policy, the annual review pack, and a record of each person’s leave.
  • A first customer success team.A welcome plan for each new customer, a brief before each account review, a renewal brief, a weekly list of accounts that need attention, and a summary of feature requests for the product team.

Pick the five that the function cannot run without. Leave out work that happens once a year until the five are in use. Start with your teams: the first five workflows each one should practise gives a first set for each common team.

What if nobody here has done this work before?

When nobody in your company has done the work before, you start each workflow from general good practice and adapt it to your business. The method for writing a customer profile, an onboarding plan or a renewal brief is well known. What your company adds is its own context: who your customers are, what you sell, the words you use and the decisions only you can make. A workflow carries both.

You can begin from a free workflow template in the Workflows Directory. Templates are samples and a starting point, made to be customized. Where your company has no method of its own yet, we build the function’s workflows with you from general methods adapted to the business: Reusable AI workflows, adapted to your business shows how.

Decide what a person decides in each.

In every workflow of a new function, a person decides and the workflow prepares. Write the decision into each workflow by name before the workflow is used. In a first marketing team, the workflow drafts the campaign email and the head of the business approves what goes out. In a first people function, the workflow prepares the interview pack and the hiring manager decides who is hired. In a first customer success team, the workflow prepares the renewal brief and the account owner decides what to offer.

Anything that sends, pays or changes a record waits for a person to approve it. A workflow can be designed to pull from the systems the company already runs, such as your CRM or your accounting system, and push data back with a person approving each change.

Let the first hire improve them.

Until the first hire arrives, one named person owns the new function and runs its workflows. In most companies of under 200 people that is the founder, the chief operating officer or the head of the team the function grows out of. Who should own AI in a company your size? covers that choice.

When the first hire starts, hand over the function, its five workflows and the record of what the interim owner changed. The first hire becomes the owner of each workflow and improves it with what they know about the work. Their expertise goes into the workflows, where the next hire finds it, instead of staying in their head. How to deploy AI workflows to a whole team, and keep them working covers the handover and the owner’s routine after it.

A one-page new function sheet to copy.

Copy these headings into a document and fill them in before the function’s first day.

  1. What the function is for.One sentence: the result this function produces for the company.
  2. The five pieces of work.The work it repeats, each with what it starts from and what it produces.
  3. The first workflow for each.The method it starts from, the company context it needs and the assistant it runs in.
  4. Who decides.For each piece of work, the person, by role, who approves the result.
  5. Who owns it until the first hire.One name, and the date the function is handed over.

Illustrative example.

Take a 90-person software company creating its first customer success team. What the function is for: every customer uses the product well enough to renew. The five pieces of work are the welcome plan, the brief before each account review, the renewal brief, the weekly list of accounts that need attention and the summary of feature requests. Each workflow starts from general customer success practice and the company’s own product notes and customer records. The account owner decides what is said to each customer, the head of product decides what happens to each feature request, and the finance lead decides renewal terms. The chief operating officer owns the function until the first customer success manager starts, then hands over all five workflows. The handoff from sales to customer success when a contract is signed goes on the company plan as the next piece of work.

What is different in a company of under 200 people.

Most advice on new functions assumes a large company that hires a leader first and gives that leader a team and a budget. A company of under 200 people starts a function differently.

  • The function starts as part of someone’s job.Before the first hire, a founder or an operations leader does the work alongside everything else. Written workflows keep it manageable.
  • The first hire is often the whole function.One person, not a department. That person needs a working method on day one, not a blank page.
  • The company context is close at hand.The people who know your customers and your offer are in the same building. Write what they know into the workflows.
  • You already pay for the assistant.The new function runs in the ChatGPT, Claude, Copilot or Gemini your company already uses. No new platform comes first.

Starting a function this way also suits a company moving into new work. New business lines: what carries over, what needs building shows what to bring from your current teams and what to build.

Where to go next.

A new function is one more team on your company’s plan. How organizations plan their use of AI sets out the three steps: plan it, develop the workflows, deploy them. We have a plan. How do we build the first AI workflow? takes one workflow from plan to use. FullyPowered Planner is where the plan lives: add the new function as a team, set out its roles and the work between it and your other teams, and choose what to build first.