The short answer.

A startup should plan its use of AI as soon as two people do the same work. At five people the plan is one paragraph: the AI you use, and the three pieces of work you all do the same way with it. The plan is worth a full page when you form your first team of three, hire your first person who was not there at the start, or find two people doing the same piece of work two different ways.

A startup’s plan follows the same method as any company’s. How organizations plan their use of AI sets out the three steps: plan it, develop the workflows, deploy them. This piece covers when a startup should begin, and how small the plan can stay.

Everyone already uses AI. Do we need a plan?

Yes, a ten-person startup where everyone uses AI needs a plan, and the plan is short. Experimenting was the right way to start: each early hire found what ChatGPT, Claude, Copilot or Gemini does well for their own work. The cost shows up when two people do the same job, each prompts the assistant their own way, and the customer gets two different answers.

A plan does three things experimenting cannot.

  • It makes shared work come out the same way.When two people write proposals, run customer calls or close the month, one written workflow gives both of them the same steps, the same checks and the same output.
  • It keeps what the founders know.The founder who wrote the first ten proposals knows what a good one contains. A workflow written from that founder’s method lets the next person start where the founder finished.
  • It points the seats you pay for at named work.A plan says which work each seat is for, so the spend is directed and not left to habit.

What happens when a company uses AI without a plan? follows undirected use as a company grows.

Three moments that call for a page.

A startup’s AI plan grows from one paragraph to one page at the first of three moments, whichever comes first.

  1. Your first team of three.Three people who share one kind of work, such as sales or customer support, are a team. A team needs its own short list: the work it repeats, the first workflow it runs, and the one person who owns that workflow.
  2. Your first hire who was not there at the start.A new hire has none of the founders’ shared memory. The plan is how that person learns which work runs through a workflow, where the workflow lives and who decides.
  3. Your first piece of work done differently by two people.Two people writing customer onboarding emails in two styles, or qualifying leads against two sets of questions. The difference is the signal. Pick the better method, write it down as a workflow, and give it one owner.

Write the page at the first moment, not the third.

What does a plan look like when there are no teams yet?

A startup with no teams plans by the work itself. Each person holds several roles, so the plan lists the pieces of work the company repeats and names who runs each one, whatever their title. Roles are named for the work: sales calls, customer onboarding, monthly close. A founder often holds four or five of them.

When the company forms its first team, those named roles move into it with their workflows attached. The sales calls role goes to the sales team, its workflow with it, and nothing is rewritten. Start with your teams gives a first set of workflows for each common team, ready for the team you form next.

Two plans to copy: the paragraph and the page.

Copy the version that fits your size. The one-paragraph plan suits the first handful of people. The one-page plan takes over at the first of the three moments.

The one-paragraph plan.

  • The AI we use.The assistant the company has approved, on the company’s own account.
  • What may go into it.One sentence on customer and company information.
  • Three pieces of work we do the same way.Each named, with the person who owns its workflow.
  • Who keeps this paragraph current.One name.

The one-page plan.

  • Where we are going.One sentence: what the company will be able to do with AI by the end of the year.
  • The AI we use and what may go into it.Carried over from the paragraph.
  • Our teams, or our roles if there are no teams yet.Each with one lead.
  • The work each team repeats.Three to five pieces of work per team.
  • The first workflow for each team.What it starts from, what it produces and who decides.
  • One owner per workflow.By name.
  • The handoff that gets stuck.The one place work passes between people and slows down.
  • What comes next.The next workflow, and the next team.
  • The review.Who reads the page each month.

One startup at twelve people.

Illustrative example.

Take a 12-person software company that sells scheduling tools to small clinics. At five people its plan was one paragraph: the company used Claude on a shared business account, no patient information went into it, and three pieces of work ran the same way for everyone: preparing a sales call, writing release notes and answering a support question from the help pages. The chief operating officer kept the paragraph current.

At twelve people all three moments had arrived: three people in support, a new account executive who never heard the founders explain a demo, and two people writing onboarding emails for new clinics in two different ways. The company wrote its first page. Where it is going: every clinic gets the same onboarding, whoever runs it. Its first teams are sales, support and product. Sales starts with the call preparation workflow it already had, now owned by the head of sales. Support starts with the help-page answer workflow, owned by the support lead, who decides any reply about billing. The onboarding emails become one workflow, built from the better of the two methods and owned by the customer success manager. The handoff that gets stuck is from sales to onboarding when a clinic signs, so that is next. The chief operating officer reads the page on the first Monday of each month.

A startup writes its way of working for the first time.

A startup’s advantage in planning AI is that its way of working has not been written down yet. An established company has to change old habits. A startup writes each piece of work for the first time, so it writes it with AI in it.

  • No procedure to unpick.The first written method for a sales call can be a workflow from day one, with the assistant preparing and a person deciding.
  • Every new hire starts with the workflows.The tenth person learns the job the way the workflow sets it out, so the company’s standard holds as it grows.
  • The founders are still in the room.The people who know the work best write the first version of each workflow.

Most published advice on planning AI is written for large enterprises, with steering committees and a year of pilots. A startup needs none of that. The plan is a paragraph, then a page, owned by a founder or the chief operating officer. Who should own AI in a company your size? covers who takes it on as the company grows, and Does a small company need an AI policy? covers the line about what may go into the assistant. Startups and new ventures shows the workflows a young company builds first.

Where the startup’s plan lives.

A startup’s one-paragraph plan lives in any shared document. FullyPowered Planner is where the one-page plan lives once several people edit it: you set out your teams, their roles and the work between them, and choose what to build first. Colleagues add their own teams as the company forms them. The Workflows Directory holds free workflow templates to start from, and we build any workflow your company needs. That is how you get 10X the ROI of your existing AI from your first hires on.

Write the paragraph now. Write the page when the first team, the first new hire or the first difference arrives.