By Touchbase Technologies · Published

How to get your first 100 SaaS customers: a measurable working plan

Your first 100 SaaS customers are a goal, not a predictable output from a particular number of emails. To work toward that goal, define who benefits, learn how they handle the problem today and help a small group complete a real task with your product. Then use observed results to decide where to spend the next week.

This plan is for a founder with a usable product who needs a repeatable way to learn and acquire customers. It includes an original fictional example, a small measurement sheet and clear decision points. It does not promise a timetable, a conversion rate or a fixed amount of outreach. Reviewed November 13, 2026.

A founder listens to an architecture customer while discussing document versions and a real product task

Define what you mean by a customer

Separate a signup, an activated user and a paying customer. If a business account has several team members, decide whether your target counts businesses or individuals. If someone buys once and immediately leaves, record that outcome rather than treating the original sale as evidence of lasting product value.

Write a simple definition before running a campaign. For example: “A customer is a business with a paid subscription. Activation means its team completed one document review and recorded an approval decision.” These definitions are fictional, but the distinction is practical. They connect acquisition work to something the product actually helps a person do.

At a hypothetical $49 monthly price, 100 active paying accounts would represent $4,900 in gross monthly subscription revenue before costs and other adjustments. That arithmetic does not tell you how many messages to send, what it will cost to acquire the accounts or how many will remain. Those require your own observations.

Choose one buyer and one supported task

Start with a buyer you can describe concretely. “Small businesses” leaves too much unanswered. “An operations lead at a small architecture practice who coordinates client document approvals” gives you a task, a possible owner and a reason to investigate the workflow.

The Small Business Administration's market research guidance recommends examining demand, market characteristics, alternatives and direct customer feedback. Use those questions to challenge your assumptions. A large market is not evidence that your particular product is useful or that you can reach its buyers effectively.

For the fictional document-review product, write down exactly what works today: upload a version, collect comments and record approval. Also write what is missing. If the product has no drawing markup, specialized security certification or integration with a firm's project system, those gaps belong in the evaluation. Do not let an outreach draft promise them away.

Learn from the current process before pitching a replacement

Ask a few suitable people to describe a recent instance of the task. What document needed approval? Who reviewed it? How did they know which version was current? What happened when someone requested a change? A specific past example usually gives you more useful detail than asking whether a future product sounds interesting.

Use public professional information or appropriate introductions to find people, and be clear about why you are contacting them. Do not imply that a business has a problem simply because it belongs to the industry. Keep a note of what was observed, what the person told you and what remains a hypothesis.

For the architecture example, you may learn that version confusion is already handled well but approval ownership is unclear. That changes the next demonstration. Instead of touring every feature, show how an approval decision is assigned and recorded. If the product cannot help with the real task, adjust the product or audience before increasing outreach.

Make a small prospect list with reasons

Review a manageable sample rather than buying a large list and assuming every record fits. Record the business, source page, relevant role, product connection and uncertainty. Leave out entries for which you cannot explain the relevance. Keep investors, partners and potential customers in distinct groups so they do not receive the wrong message.

For each suitable prospect, choose an appropriate next step: a research question, an introduction, a focused example or a product conversation. A request for a sales meeting is not the only possible first step. Match the ask to what you know and to the effort you are asking the other person to make.

Use an address only when it is appropriate for the intended contact. Review verification information and exclusions, and follow provider requirements. A researched match is not consent, and no address check guarantees delivery. The prospect evidence checklist gives a practical worksheet for keeping those decisions visible.

Show a short path to a useful result

For the document-review product, prepare a fictional project with two document versions and one approval decision. Demonstrate how a reviewer identifies the right version, adds a comment and records the next action. Remove unrelated setup steps from the main demonstration, then explain any real prerequisites separately.

Agree on what a pilot should establish. A useful question might be whether the team can complete one genuine review without losing track of who approved which version. Record the start, responsible person, intended result and decision date. If you use a free pilot, define what you are learning and when you will discuss a paid arrangement. If you charge from the start, make the scope and price clear.

Free access and paid pilots can both provide information. Neither automatically proves or disproves demand. Look at actual use, the work required to support it, the person's alternatives and whether the proposed paid arrangement makes sense to them.

Use a measurement sheet that preserves the denominator

The following figures are a fictional sample, not expected conversion rates or an outreach target. They show why separating stages matters.

Stage in one small exerciseCountWhat it tells you
Business records reviewed30The amount of research examined
Records with sufficient relevance and contact context18The portion suitable for a further decision
Appropriate first messages sent12The denominator for message response analysis
People who replied4Responses that still need classification
Product pilots started2A separate commitment beyond a reply
Paid accounts started1An initial purchase, with retention still unobserved

Do not turn this small sample into a forecast for reaching 100. A reply can be a refusal, a referral or a question. A pilot can stall. A paying account can leave. Record the reason for each transition, along with delivery failures, exclusions and unresolved next actions.

Review progress in short working cycles

Choose a review date and ask where the process is breaking. Weak business fit points back to the audience definition. Inaccurate drafts point to missing product facts or poor review. Interested conversations that do not become pilots may expose unclear value, onboarding work or a product gap. People who activate but leave require a retention conversation rather than a larger mailing list.

Keep acquisition costs and founder time visible. The SBA's marketing and sales guidance describes using a marketing plan, budget and review process. You can apply that discipline to a small experiment: state the task, choose a channel, record the cost and decide whether the evidence supports continuing.

Ask satisfied customers for an introduction when they have actually experienced a useful result. Make the request specific and optional. Do not reuse a customer's name, quote or project details in public material without permission. An honest example is more useful than an invented success story.

Turn each review into next week's work

Write one decision, one owner and one preparation deadline after the review. For the fictional architecture product, that might mean clarifying which file versions the demonstration supports before inviting another group to see it. Check the explanation against the product that actually exists; a deadline should not turn a planned feature into a sales claim.

Keep the next test small enough that you can answer its resulting conversations. Record the audience, the supported task, the demonstration or message you will use and the date you will review the result. If onboarding is failing, reserve time to repair that before adding more traffic. If people complete the task but do not return, find out what is missing before assuming the answer is more outreach.

The small-business marketing calendar provides a working schedule with dependencies, owners and review decisions. Adapt that structure to your customer-learning cycle rather than copying its shop example or treating its hypothetical figures as SaaS benchmarks.

Check the handoff before paying for outside help

Before hiring an agency to increase prospect volume, define an accepted opportunity and name the person who will handle replies. Ask to review a small work sample and decide how duplicate records, existing customers and people who decline contact will be treated. The customer acquisition agency checklist includes a brief and a cost example for that decision.

Keep access to the records behind the report. If an outside team manages part of the process, agree how your team can retain the information it is entitled to use and preserve contact preferences. A tested contact backup is more useful than assuming every record can be recovered from a dashboard later.

Use software to support a clear process

Touchbase can help turn reviewed product information into prospect research, email drafts, campaigns, demos and reply work. It cannot establish a buyer's willingness to pay or remove the need for product and contact review. Verify the current product scope and available plans before deciding which tasks to use it for.

Work toward 100 by making the next decision observable: which buyer, which task, which evidence and which result. Keep the original record when an experiment fails. That record can tell you what to change; a larger signup total without activation or retention context cannot.

Prepared with AI assistance and checked against the sources linked in this guide.