Before a micro SaaS acquisition, map the operating work you will take over: the product, customer commitments, business accounts, and seller support. A platform with no customers creates a different first-day job from a service people already rely on. Clarify that starting point before drawing up a growth plan.
In Episode 117 of The Happy Customer Channel, Stuart Faught describes several ways buyers have approached his software businesses. Some want a brand and platform they can grow. Others want help reaching a particular stage. He also describes using asset purchases in his own transactions. These are his experiences, not a standard deal structure for every buyer.
Clarify which starting point is on offer
Begin by describing the actual business you are evaluating. Does it have active customers? Are those customers paying, testing, or inactive? Does it have a documented product and a brand but no existing accounts? The answers should shape the questions that follow.
Faught notes that some buyers prefer an opportunity without customers because they want to do the selling themselves. That is a different proposition from taking responsibility for a service people already use. A label such as “ready to scale” needs a specific description of what is ready and what remains to be built.
Ask for an operating map
Use the following THCC handoff questions to map the work. List the product, the systems that support it, and the people who understand those systems. Then ask the seller to walk through an ordinary customer request and a problem that needs technical attention.
- Product: can the seller demonstrate the normal customer workflow and explain its known limitations?
- Access: which business-owned domains, hosting, code, billing and support accounts are involved, and what transfer permissions do their providers require?
- Customers: where are support promises, open requests and recurring responsibilities recorded?
- Knowledge: where are deployment, maintenance, recovery and support procedures documented?
- Ownership: who takes each handoff action, and what observable result shows it is complete?
Acquire.com’s technical due diligence guide provides further context on examining a software business. Confirm the relevant rights, permissions and provider transfer requirements instead of assuming every account or agreement can move unchanged.
Make seller support specific
Faught describes situations in which his team stays involved after the initial transaction. For an operator, the useful questions concern the work: who answers a product question, who handles an incident, which training is included, and when that involvement ends.
For each support commitment, identify the person, the task and the point when the task is complete. A product walkthrough, incident response and training session are different commitments. Record the unanswered questions and keep the operating plan aligned with the actual agreement and specialist review.
Look at the experience customers will have
A change in ownership can reach customers through a billing question, a support reply, or an unexpected product issue. Map those interactions before assuming the business can run without the seller’s knowledge. Identify the person who takes responsibility when a customer’s issue crosses systems or teams.
THCC’s article on customer journey accountability offers a useful way to think about these handoffs. Knowing who owns the next action is part of delivering the experience customers were promised.
Keep the handoff and the growth plan separate
An orderly transfer gives the next operator a clearer starting point. Growth still requires its own plan. Ask how customers have been reached, which activities the seller personally handled, and what the buyer can realistically continue. Treat that as a set of questions to investigate rather than a forecast.
Questions buyers ask
Is a product with no customers the same as an operating SaaS business?
It represents a different starting point. A buyer may need to validate the offer, reach customers, and build support practices. An existing customer base brings evidence to examine and ongoing responsibilities to understand.
What should a first handoff conversation accomplish?
It should identify what exists, what is being discussed for transfer, who understands the operating work, and which questions remain unanswered. It does not replace technical, financial, or legal diligence.
Watch the source episode
Watch the full Stuart Faught interview for his explanation of buyer preferences and seller involvement. Browse THCC’s entrepreneurship episodes for more ownership conversations.
