How do you get your first pilot customer?

What is a pilot, and how is it different from a design partner or a beta?

A pilot is a short, time-boxed test where one company uses your product on one real problem so they can decide whether to buy it. It has a start date, an end date, a goal everyone agreed on, and a decision at the end.

A design partner is different. A design partner helps you shape the product over a few months by giving feedback, often for free or at a discount. A beta is different again. A beta is an early version you open to many users to find bugs and see how people use it.

People mix these up all the time, and that is how founders end up running a free "pilot" for six months that never turns into a sale. Know which one you are running before you start.

Big companies usually want proof before they agree to a pilot. Start with smaller design partners, collect results and a case study, then take that proof to larger buyers.

• Main goal

  Pilot:

  A buying decision

  Design partner:

  Shape the product together

  Beta:

  Find bugs and see real use

• Who it is for

  Pilot:

  One company, one use case

  Design partner:

  A small group of close-fit companies

  Beta:

  Many users at once

• Length

  Pilot:

  Short and fixed, often about a month

  Design partner:

  A few months, sometimes longer

  Beta:

  Until the product is stable

• Paid?

  Pilot:

  Usually paid, at least a small fee

  Design partner:

  Free or discounted, then they pay

  Beta:

  Usually free

• What success looks like

  Pilot:

  They sign the paid contract

  Design partner:

  They help build it, then become a customer

  Beta:

  Fewer bugs, clear usage data

• Ends with

  Pilot:

  Yes, no, or a clear next step

  Design partner:

  A paid contract and a reference

  Beta:

  A public launch

Who should you pitch for your first pilot, and how do you ask?

Pitch companies that feel the problem today and have someone who can approve spending money on it. A happy user with no budget can love your product and still never be able to buy it.

Before you ask anyone, write down the one use case you want to prove. Keep it small. A pilot that tries to prove everything proves nothing.

Then look for warm paths in. Investors, advisors, past coworkers and early customers can all make introductions. Cold outreach works too, and it also tells you fast whether the pain is real.

Make sure you are ready to sell to businesses at all. Early on, Nomiki Petrolla, Theanna's founder, was pushed to sell to companies before Theanna was ready. She says she lost a lot of time. She went back to selling to founders one by one, and her first business customer later came to her.

The pitch itself is the same story you tell any customer: the problem, who has it and what changes. The only difference is the ending. You ask to run a pilot with a set number of people.

When you ask, be direct. Name the problem, the one result you want to show, how long it takes, and that it is paid. For example: "We would like to run a 30-day paid pilot to cut your weekly report time. If we hit the goal, you move to the regular plan at the price we agree on today."

• The champion: the person who wants your product and will use it.
• The buyer: the person who controls the budget and signs. They should join the kickoff and the final review, even briefly.
• The blockers: security, IT, legal or procurement. Find out who they are on day one, not after the pilot works.

Paid pilot vs free pilot: which should you run?

Run a paid pilot whenever you can. Investors and founders who write about this agree on the main reason: when a company pays, it puts real people and time on the pilot, and it is much more likely to make a decision at the end.

Pear VC's guide on pilots says pilots should never be free, because a buyer who will not pay for a pilot is unlikely to buy the product after it. Brighteye Ventures puts it this way: free pilots invite drift, paid pilots invite decisions.

Theanna learned this with its own product. It once had a free version, and Nomiki shut it down within 45 days because it watered down the value. Free takes a lot of your energy, and people who pay nothing put in less than people who pay.

There is one fair exception. If you are very early and still figuring out what to build, a free or discounted design partner deal can make sense. Design partners often get the product free or at a discount, but agree up front on what they will pay once it works. Even then, set a clear scope, an end date and what happens next.

How do you price a pilot?

Price a pilot as a smaller, discounted version of the real contract, and agree on the full price before the pilot starts. The pilot fee matters less than getting the paid contract terms written down up front.

Pear VC suggests a monthly pilot price that covers the work it takes you to deliver, roughly matches a monthly slice of the expected yearly contract, and includes a 20 to 50 percent discount.

One more trick from Pear VC: credit the pilot fee toward the yearly contract if the customer signs within a set window, such as one month after the pilot ends. That gives them a real reason to decide quickly.

How do I book and run a pilot that turns into a paid contract?

1. 01

   Pick one use case and one metric

   Choose the smallest proof that would make the buyer say yes. Pick one number that shows it, like hours saved, leads booked or errors cut. Write down where that number is today so you have a starting point.

2. 02

   Find out what decision the pilot unlocks

   Ask who decides if it worked, who signs the budget, and who could block the deal. If the customer cannot name the decision the pilot leads to, it is not a pilot yet. Always ask if there is someone else you should bring in.

3. 03

   Set the length and the end date

   Agree on a fixed window and put the final review on the calendar now. Short is better. A deadline that keeps sliding is the most common way pilots die.

4. 04

   Write the success criteria and the price down

   List two or three results the pilot must hit, what each side will do, and the price the customer pays if the results are met. Put it in a short agreement, order form or purchase order, not only an email thread.

5. 05

   Start the paperwork on day one

   Begin security review, legal and procurement at the same time as the pilot, not after it. Many pilots that work still stall here because these steps started too late.

6. 06

   Measure every week and check in at the halfway point

   Send a short weekly update with the metric, the starting number and what changed. At the halfway mark, check that the champion is active, the data is flowing and the buyer is still paying attention.

7. 07

   Hold the final review and ask for the contract

   Go through the success criteria one by one. If they were met, the meeting is about signing the price you already agreed on, not a new negotiation. If they were not met, decide together to stop or run one short, clearly scoped extension.

How long should a pilot be?

Most pilots should be short, with a fixed end date. Pear VC suggests aiming for one month and never going past three. The longer the window, the easier it is for the deadline to slip.

Long pilots rarely fail because the product is bad. They fail because nobody feels any urgency. Brighteye Ventures goes further and suggests keeping the proof as small as possible, even a few days of proof-of-value for a narrow use case, rather than weeks of open-ended testing.

Design partner programs are the exception. They often run for several months because the goal is to build the product together, not to make one buying decision.

If you do run a longer pilot, the customer has to see real results along the way. A longer pilot can raise your odds of a sale, but only if every week shows them value.

What should you measure during a pilot, and what goes in the agreement?

Measure one business result the buyer cares about, plus a few signs that people are using the product. "The tool connects to our data" is not a success criterion. Money saved, revenue gained, time saved or risk avoided are.

Check the numbers every week against where they started. A weekly update keeps the champion engaged, gives the buyer proof they can forward, and shows problems early while there is still time to fix them. The table at the end of this section lists what to track.

Before kickoff, put these in a short pilot agreement:

• The one use case in scope, and what is out of scope.
• Start date, end date and the date of the final review.
• Two or three success criteria, each with a number and where the data comes from.
• What your team does and what the customer's team does.
• Named owner on each side, plus the buyer who signs.
• Pilot fee and how it is billed.
• The paid price and plan that start if the criteria are met.
• What happens if they are not met: stop, or one short, scoped extension.

• Your one success metric

  What it tells you:

  Whether the pilot worked

  Example:

  Report time down from four hours to ninety minutes

• Starting number

  What it tells you:

  What "better" means

  Example:

  Measured the week before kickoff

• Activation

  What it tells you:

  Whether the team got set up

  Example:

  All named users logged in during week one

• Usage depth

  What it tells you:

  Whether they rely on it

  Example:

  Used in the weekly workflow, not once

• Time to value

  What it tells you:

  How fast they saw a result

  Example:

  First useful result in the first week or two