{"id":21470,"date":"2026-10-27T17:20:00","date_gmt":"2026-10-27T16:20:00","guid":{"rendered":"https:\/\/www.lukaswojcik.com\/blog\/?p=21470"},"modified":"2026-10-26T10:00:08","modified_gmt":"2026-10-26T09:00:08","slug":"the-first-ten-paying-saas-customers-demo-paid-pilot-or-free-entry","status":"publish","type":"post","link":"https:\/\/www.lukaswojcik.com\/blog\/en\/saas-internet-earning\/the-first-ten-paying-saas-customers-demo-paid-pilot-or-free-entry\/","title":{"rendered":"The first ten paying SaaS customers: demo, paid pilot or free entry?"},"content":{"rendered":"

Ten initial payments answer a different question from a thousand registrations: which workflow matters enough to receive a budget? A small customer group allows direct conversations and tightly scoped experiments. The right entry depends on whether value appears immediately or requires setup and trust.<\/p>\n

\"Qualified
Four separately recorded measures; a paid pilot may receive payment before the first useful result.<\/figcaption><\/figure>\n

Three entry points, three kinds of evidence<\/h2>\n

A demo, meaning a product demonstration, fits a business-to-business (B2B) workflow that needs explanation. A presentation with realistic sample data and a clear next step matters more than a generic tour. An informal presentation without a decision date provides weak evidence.<\/p>\n

A paid pilot limits duration, data scope and success criteria. A four-week test could cover one export workflow and a fixed setup fee. Custom development receives a separate budget so that the pilot does not disguise a service business as a product.<\/p>\n

Free entry fits an immediately useful core feature. Activation means solving a real problem, such as completing an export; a registration alone does not qualify. Trials also need clear expiry and billing rules. Stripe documents several trial configurations. [2<\/a>]<\/p>\n

A shared funnel instead of incomparable success counts<\/h2>\n

A funnel tracks how many interested people move from one step to the next. Comparable measures are suitable contacts, the first useful result in the product, the first payment and repeat use after four weeks. A suitable contact has the chosen problem and could become a customer. Attending a demo is only a sales step; activation still requires a problem actually solved. A signed pilot agreement is not proof of use either. Contacts from the same period and channel form a separately measured group, also called a cohort. In a paid pilot, the first payment may precede activation.<\/p>\n

Founder time belongs in the cost. Ten hours of conversations, setup and follow-up constitute acquisition spending even without an advertising invoice. Paul Graham describes personal work with early customers as a useful part of launching. That does not mean the same time commitment remains affordable with many more customers. [1<\/a>]<\/p>\n

Worked example: ten customers require a mechanism<\/h2>\n

This simplified example covers free entry and uses one currency. Every input is assumed: 2,000 suitable visits at a 5% signup rate produce 100 registrations. Half reach the first useful result, leaving 50. If 20% of that group pays, the calculation gives ten paying customers. Marketing spending of 400 currency units plus ten sales hours at 40 totals 800. Dividing by ten gives a customer acquisition cost, or CAC, of 80 per customer.<\/p>\n

A net price of 29 minus variable monthly costs of nine leaves 20 per customer each month to cover other costs. This is the contribution margin. With no cancellations, also called churn, and no additional costs, four monthly contributions recover the initial acquisition cost of 80. Halving payment conversion increases CAC to 160 and payback to eight months. The calculator exposes this dependency; actual sales remain whole numbers and fluctuate.<\/p>\n

A two-week experiment with a stopping rule<\/h2>\n

Week one gathers conversations about one problem, the existing substitute and the budget owner. Week two tests one entry route with a fixed offer. Predetermined limits prevent endless unpaid assistance: maximum setup effort, a minimum number of suitable contacts and a review date.<\/p>\n

Success requires paid use and identifiable value. Few first useful results may indicate product or setup difficulties. Useful results without payment may reflect price, the target audience or a free tier that already meets the need. Conversations must test these explanations. Additional traffic does not automatically solve either problem. Further development should remove the specific obstacle observed, such as a setup step that is often abandoned.<\/p>\n

\n

Related tools<\/h2>\n