Customers as capital: pilots, prepayment and design partners

As of 2026-10-10, this is general information, not legal or financial advice. Contracts, tax treatment and data rules depend on where the parties are and what they agree. Ask a lawyer and an accountant licensed where you operate.

A first customer can do three jobs at once. They can tell you whether the product solves a real problem, they can give you a place to learn in public, and they can put money into the company before any investor does. That third job is what “customers as capital” means: using what early customers pay, or promise to pay, to fund the work.

It is also the easiest route to misread. A customer who pays for a pilot has not necessarily agreed to buy the product, and a design partner who helps you shape a feature has not necessarily agreed to leave you the rights to it. Most of the trouble comes from unspoken assumptions that nobody wrote down. This article describes three common arrangements and lists what to settle in writing before any of them starts.

Three arrangements

The terms are not fixed, and many companies use the words differently. That is the reason to define them in your own paperwork rather than assume the customer shares your meaning.

Why a pilot is a test, not a sale

The GOV.UK Service Manual, which describes how public-sector teams build services, treats the alpha phase as the time to try out different solutions to problems learned about earlier, spending the time building prototypes and testing ideas. It says a crucial part of alpha is identifying your riskiest assumptions and testing them. Founders can borrow that framing for a pilot: the pilot exists to test a specific assumption, such as that a team will use the tool weekly or that a manual process can be replaced. If you cannot name the assumption, you do not yet know what the pilot is for.

A useful test is to finish this sentence before the pilot starts: “At the end, I will know whether ___ is true, and I will know it because I saw ___.” The blanks are what you write into the agreement as success criteria.

What to write down before a pilot

These items are a starting list for a conversation with counsel. Each one prevents a particular kind of disagreement.

1. The parties and the people. Which legal entities sign, and who on each side is responsible for running the pilot?
2. The scope. What the customer may use, which teams or users, and what is excluded.
3. The purpose and the success criteria. The assumption being tested and the evidence that would count as a pass or a fail.
4. The dates. A start date, an end date, and what happens at the end: ends, extends or converts.
5. The conversion terms. If the pilot succeeds, is there a price already agreed, an option to buy, or nothing? An unwritten expectation that the pilot will simply continue is not a term.
6. The price during the pilot. Whether it is paid, and what the payment covers. Write what the money is for: access, support, custom work or all three.
7. The data. What information the customer will put into the product, where it is stored and who may see it. If personal data covered by the European Union’s General Data Protection Regulation is involved, Article 28 says processing by a processor shall be governed by a contract or other legal act under Union or Member State law, and that the contract sets out the subject matter and duration of the processing and the nature and purpose of the processing. Ask counsel whether you are acting as a processor and what the contract must contain.
8. The intellectual property. Who owns the product, who owns what the customer builds with it, and what the customer may say about it. A written agreement matters here: U.S. copyright law says a transfer of copyright ownership is not valid unless an instrument of conveyance, or a note or memorandum of the transfer, is in writing and signed. If the customer pays for custom work, ask whether the agreement transfers ownership, licenses it or leaves it with you.
9. The feedback. Whether you may use what the customer tells you to improve the product, and whether the customer expects credit or exclusivity for ideas.
10. Confidentiality. What each side must keep private, and for how long.
11. Naming and publicity. Whether you may mention the customer, and how.
12. Exclusivity. Any promise not to work with competitors. Treat this with care and take it to counsel, because it limits your future customers.
13. Support and responsibility. What you will provide during the pilot, what you will not, and how each side limits its liability.
14. Ending early. How either side may stop, and what happens to data and access when they do.

Prepayment: money that comes with a promise

When a customer pays ahead of delivery, you hold their money and a duty to deliver. Questions to bring to an accountant and counsel:

• What exactly was bought? Access to a working product, a defined feature, or a general commitment to build? Say so in the order form.
• What if you cannot deliver? Is the payment returned, in full or in part, and under what conditions?
• How is the money recorded? Ask an accountant who knows your jurisdiction how a payment received before delivery is recorded, and when it counts as income.
• Does the prepayment change the price or term of a later renewal? Write the answer down.
• Is there a limit on how much of the business depends on one customer? A large prepayment is attractive, and it creates a dependency that is worth naming to yourself.

Design partners: shaping the product with a buyer

A design partner can show you what serious buyers need. The same closeness can bend the product toward one organization. Some questions help keep the balance:

• Would other customers want what this partner asks for, and how will you check?
• Who decides what is built, and how are disagreements resolved?
• Does the partner receive early access, a better price or a role in the roadmap, and for how long?
• Does the partner’s logo or name appear in your materials, and is that agreed in writing?
• What happens to the partner’s special arrangements when you set a standard price?

The customer interview guide can help you separate what one partner wants from what the wider market needs, and the article on founder-led sales to your first ten customers shows how a first buyer is usually found.

Larger customers, longer paths

If your first customer is a large organization, expect more steps: procurement review, security questions, legal review and sometimes a requirement for particular insurance or terms. These steps add time and sometimes cost. Answer questions about your product truthfully and in your own words, and do not describe protections you do not have. A short note of what you do and do not do is better than an inflated claim that a later audit will test.

When customers are the wrong capital

A customer-funded path is not always the right one, and this article does not suggest that it is. Some products need work before any customer can use them. Some customers pay slowly. Some arrangements, such as a heavy custom build, can turn a product company into a service business without anyone choosing it. If that concerns you, the article on matching a funding route to a stage sets customer money beside the other routes, and the earn your first customers playbook covers the selling itself.

What this article cannot tell you

It cannot say whether customers will pay for your product, how much they would pay, or whether a pilot will lead to a sale. The three sources cited are a government design manual, the text of one European Union regulation and one section of the U.S. Copyright Act; none of them measures pilots, prepayments or design partnerships, and none of them describes the commercial terms that customers and vendors usually agree. The article gives no price, no discount and no typical length for a pilot. It does not cover revenue accounting rules, tax, consumer protection, procurement law or the rules of any particular country, and it names no customer. A real agreement depends on the parties, the product and the place, and a lawyer who has read it is the right person to say what it means.

In the data

These figures describe U.S. businesses in general, not WE’s results. Each one names its source.

Show the data as a table

Median years between funding rounds

Between rounds	Median gap
Seed to Series A	2.0 years
Series A to Series B	2.1 years
Series B to Series C	2.4 years

Venture-backed companies on one equity platform; most companies never raise a priced round.

Source: Carta, State of Private Markets: Q1 2026 , 2026-05-29

Retrieved 2026-10-15. Single figures quoted from the report as printed; no dataset is re-hosted.

Sources

1. How the alpha phase works, GOV.UK Service Manual, Government Digital Service . Accessed October 10, 2026.
2. Regulation (EU) 2016/679, General Data Protection Regulation, Article 28, EUR-Lex, Publications Office of the European Union . Accessed October 10, 2026.
3. 17 U.S. Code section 204, Execution of transfers of copyright ownership, Legal Information Institute, Cornell Law School . Accessed October 10, 2026.

Spotted an error? Read how we handle corrections in our editorial policy.