Chapter 18

Follow the Trust Path

Identical Message, Different Sender

Imagine you run a thirty-person professional services firm. On Monday morning, this arrives in your inbox from somebody you have never heard of:

I built a tool that identifies where client projects are losing margin because of untracked work, scope changes, and delayed billing. If that is a problem you deal with, I would be glad to show you how it works on one real project.

It is a decent message. The problem is recognizable, the claim is specific enough to understand, and the sender is not asking you to schedule a “quick 30-minute chat to explore synergies,” which already puts them ahead of a surprising percentage of the internet. You still know nothing about them. You do not know whether the application works, whether the founder understands professional services, whether anyone else uses it, whether connecting your information to it would be sensible, or whether the company will exist long enough for learning the product to be worth your time. Maybe you glance at the website. Maybe you save the message. Maybe you delete it because you have seven client problems, three internal problems, and an inbox containing several other strangers who have also built something that apparently deserves your immediate attention.

Now imagine the identical paragraph arrives the next morning because a consultant you have worked with for five years forwards it to you.

The product has not changed, the claim has not changed, and the words have not changed. But the message is no longer carrying the same commercial burden. The consultant has not proved the software works. They have not proved the price makes sense, the implementation will go smoothly, or the problem is important enough for you to act on now. They certainly have not transferred some supernatural ability to turn mediocre software into a good purchase. What they have done is change the starting conditions. Yesterday, the founder was asking you to evaluate both the proposition and the founder from almost zero. Today, someone whose judgment you already have reasons to respect has placed the proposition in front of you. Even a weak endorsement such as “This looked relevant to what we discussed last month” supplies context the cold message did not have.

That context matters because a buyer is never evaluating words in isolation.

Builders sometimes treat acquisition channels as delivery infrastructure. Write the message, then decide where to send it: email, LinkedIn, a community, an advertisement, a marketplace, a partner newsletter, a conference, search. The underlying assumption is that the message contains the commercial meaning and the channel merely transports it. That is too simple. The path changes what the buyer knows before reading the first substantive claim. A message from an unknown founder says, in effect, I would like you to believe that I understand this problem. A referral from someone who works with the buyer can say, before the founder has said anything, Someone who understands my situation thought this was worth putting in front of me. A piece of technical work the buyer has followed for six months can make a product announcement arrive from someone whose competence has already been partially observed. Search can put the same offer in front of a person who has already declared, through behavior, that they are looking for something in the neighborhood of the problem. An advertisement can reach exactly the right person while supplying almost none of those advantages.

These are not better and worse versions of marketing in some universal ranking. They begin the buyer at different points, and that is the distinction I care about in this chapter.

Earlier, we separated trust from product value. A buyer can believe an application is useful and still lack enough confidence in the seller, implementation, support, security, reliability, or outcome to proceed. We also established that being technically capable of contacting somebody is not the same thing as having meaningful access to them. Now put those ideas together. The path through which a buyer encounters you can change how much uncertainty exists before evaluation even begins. I call that the trust path.

The phrase is intentionally broader than channel. Two messages can travel through the same channel and have completely different trust paths. A LinkedIn message from a stranger who found your title in a database is not commercially identical to a LinkedIn message from a former colleague. The transport mechanism is the same; the accumulated context is not. The reverse is true too. A recommendation inside a small professional community, a referral from an existing customer, and an introduction from a consultant arrive through different channels while sharing an important characteristic: somebody the buyer already takes seriously has reduced the amount of credibility the seller must establish from scratch.

That does not mean warm is always better. A warm introduction to someone who does not have the problem is still an introduction to the wrong person. A respected friend can get you a meeting with an executive who politely spends twenty minutes looking at software they have no reason to buy. You may leave encouraged because the conversation happened easily, but courtesy is not demand with nicer manners. Likewise, a buyer who finds you through an extremely specific search may be commercially more interesting than someone who knows you personally. The stranger may be trying to solve the exact problem today. Your friend may merely be willing to take the call.

The goal is not maximum warmth. The goal is a path that allows the right buyer to reach a serious evaluation without requiring you to reconstruct credibility from the ground up every time.

That distinction becomes especially important for small companies and new products because founders often begin with very little institutional proof. You do not yet have the customer list, the case studies, the years of operating history, or the brand that allows a buyer to make comfortable assumptions before clicking anything, and you cannot manufacture that history with better copy. But you may not need to, because you may have something else. Someone already knows your work. A former colleague has seen you deliver. A consultant serves the market you are trying to enter. A professional community has watched you answer difficult questions without immediately turning every conversation into a pitch. A customer knows another buyer with the same problem. Those are not merely names in a network. Potentially, they are shorter trust paths.

That is where I would look before automatically deciding that the first customer requires the largest possible audience. The early commercial question is not simply, Where can I put this message? It is, Through what path can a plausible buyer encounter this offer with enough reason to take the next step seriously? Sometimes the answer will eventually be search, cold outbound, content, paid acquisition, a marketplace, or some combination of them. We will get there. But the shortest path often begins closer to home, with people who already have a reason to believe something about you before you ask them to believe something about the product.

When Someone Else Vouches

Warm trust works when the buyer already knows you. Borrowed trust works when they do not.

We looked at borrowed trust in the chapter on trust, mostly as a form of proof: a consultant, an existing customer, a professional community, a marketplace, or a platform the buyer already relies on can lend the seller some credibility before the evaluation begins. The point here is narrower and more operational. Borrowed trust is not only something that makes a buyer more comfortable once they are looking at you. It is one of the main routes by which the right buyer comes to look at you at all.

The founder from the previous chapter is the cleanest example I have. He had plenty of public attention and almost no revenue, and the useful turn came when a small group of consultants who already advised professional-services firms on the very process his application affected agreed to look at the product. When one of them introduced it to relevant firms, the introduction did more than deliver contact information. Compare the two messages reaching the same firm. The first arrives directly from the founder: We built software that can improve this administrative process. The second comes through a consultant who works with the firm on that process: I have looked at this, and I think it may be relevant to the problem we’ve been discussing. The second message contains additional information even if the consultant says almost nothing about the product itself. The buyer knows why the message arrived. Someone familiar with the situation has already performed at least a crude relevance filter. The product is no longer merely one of the thousands of things that could theoretically help a professional-services firm. It has been connected to a problem by someone whose judgment already has standing with the buyer.

That is the useful part, and it is also easy to overstate. The consultant has not proven that the software works, that the implementation will succeed, that the price is justified, or that the buyer should act now. Trust transfers selectively, and it transfers along the line of whatever the buyer trusts the intermediary for. This sounds obvious, but founders can become strangely excited about anyone with access to an audience. Someone has 100,000 followers. Someone runs a community. Someone has relationships with several companies in the industry. Excellent. Before deciding that this person represents a distribution breakthrough, I want to know what their audience trusts them for, because reach and credibility are not interchangeable, and neither are credibility and relevance. A creator followed for entertaining commentary about startups may have an enormous audience of founders and almost no influence over which accounting system those founders purchase. A niche consultant with an audience of 800 people may have remarkable influence over exactly that decision, because those 800 people hire the consultant to help make it. The smaller audience can carry more commercially useful trust.

Partners deserve a specific warning because they are the version of borrowed trust that most often gets announced before it has done anything. A strong partner may create access, explain the product in language the buyer already understands, reduce perceived vendor risk, help with implementation, and provide a path into accounts that would otherwise take months to reach. They may also want margin, control the customer relationship, describe the product inaccurately, or prioritize whatever is easiest for them to sell. They may enthusiastically announce a partnership, add your logo to a page, participate in three meetings, and never introduce you to anyone who could plausibly buy. I have learned to distinguish the existence of a partnership from the behavior of a partner for roughly the same reason I distinguish the existence of an audience from distribution. The noun is not the result.

What matters is whether trust actually moves, and that is an empirical question. Does the intermediary put the product in front of relevant buyers? Does the buyer give the proposition more serious attention because of that path? Does the intermediary supply useful context rather than merely forwarding a link? Do introduced prospects behave differently from comparable cold prospects? Does the relationship keep producing opportunities, or did one unusually helpful person create one lucky meeting? Borrowed trust deserves the same evidence discipline as every other part of the business.

There is one other boundary worth keeping clear. You can borrow credibility. You cannot borrow the buyer’s problem. A trusted consultant can persuade someone that you deserve a meeting. A customer can tell a peer that your company delivered what it promised. A marketplace can reduce uncertainty around acquiring the software. None of them can permanently compensate for weak economics, an irrelevant buyer, a vague offer, or a product that fails when people use it. The strongest borrowed-trust path gets you past uncertainty that should not have prevented evaluation in the first place. It gives the proposition a fair hearing. Then the proposition still has to survive the hearing.

For an early founder, that can be enormously valuable. Instead of trying to manufacture credibility independently in every interaction, you can look for places where relevant credibility already exists and where the person or institution holding it has a legitimate reason to connect you to the buyer. But eventually you want something more durable. You want buyers who have never met you, received no personal introduction, and owe nothing to an intermediary to encounter enough evidence that they begin trusting your judgment anyway. That kind of trust cannot simply be borrowed. It has to be earned.

Earned Trust

Borrowed trust depends on somebody else being willing to lend you some of theirs. Earned trust is slower. Nobody makes the introduction. Nobody places a respected hand on your shoulder and tells the buyer you are worth listening to. Instead, the buyer encounters evidence that allows them to reach part of that conclusion themselves.

This is where content can become commercially useful, although I use the word content reluctantly because it now describes everything from a twelve-page technical analysis to a photograph of someone’s coffee beside the observation that founders should never give up. The useful distinction is not whether you publish. It is whether what you make public gives a relevant buyer evidence of how you think, what you understand, or what you can actually do.

Suppose you sell software that helps engineering consultancies assemble a recurring compliance package. You could publish three posts a week announcing new features, celebrating release milestones, discussing AI trends, and reminding the world that manual workflows are inefficient. You are publishing. Now suppose instead you publish a careful teardown of the compliance workflow your product addresses. You show where information usually originates, where handoffs fail, which parts require professional judgment, which parts can reasonably be automated, and where an automated system should stop rather than confidently inventing something expensive. A buyer who works inside that process can inspect your understanding before speaking with you. That is different. You have not proven that your product is good, and you certainly have not proven that the buyer should purchase it. But you have created evidence that you understand something relevant enough to the buyer’s world that a conversation with you may be worth having.

Technical founders have unusually good raw material for this kind of trust because we can show work. A functioning demo is work. So is good documentation, a useful open-source component, a benchmark that discloses how it was run, a detailed explanation of an architecture decision, a small tool that solves one part of the buyer’s problem, or a thoughtful comparison that includes the situations where your own approach is not the right choice. Documenting where your own system fails, instead of pretending every test was magnificent, is work too, and it demonstrates judgment. None of these deserves to be turned into a universal acquisition formula. I am not suggesting that every SaaS founder should start an open-source project, publish a benchmark, record thirty-seven tutorial videos, and spend the next year becoming a minor internet celebrity before asking anyone for money. The point is simpler. Claims require the buyer to believe you. Work gives the buyer something to inspect.

That difference matters most when the seller is relatively unknown. The founder of a young company can say, “We understand this workflow deeply,” a sentence the buyer has heard from every vendor whose sales deck successfully opened. Or the founder can make enough of their thinking visible that the buyer can form an opinion independently. “Thought leader in AI transformation” asks the reader to accept a title. A technically precise explanation of why a particular automation will fail under three common operating conditions lets the reader judge whether the person appears to know what they are talking about. One requests credibility. The other creates evidence from which credibility might emerge.

That still leaves an important problem: earned trust has to be relevant to the purchase. You can become highly trusted for the wrong thing. A developer may build an enormous following by publishing excellent material about language models, agent frameworks, infrastructure, and software architecture, and that audience may genuinely respect the developer’s technical judgment. If the developer later sells a product that helps dental practices reduce insurance claim denials, the existing credibility is not worthless, but a large portion of it fails to cross the distance between subjects. The dentist is not evaluating whether you understand vector databases. Trust has a domain.

That is why the best public work for an early commercial path often sits near the actual buyer problem rather than merely near the founder’s interests. The question is not, What can I publish consistently? Builders can answer that question so aggressively that we end up recreating the activity problem from the previous chapter. The better question is, What could a serious buyer encounter that would make evaluating this company feel less speculative? Sometimes that is writing. Sometimes documentation does more work than a newsletter, and sometimes a useful calculator, diagnostic, template, or implementation guide provides stronger evidence than months of general commentary.

And sometimes public work does almost nothing. That boundary matters. A buyer can read everything you have written and still lack urgency. Thousands of people can admire your technical work without belonging to the market. A tutorial can generate traffic from people who want to learn how you built something rather than people who want to buy the result. An open-source project can attract developers while the economic buyer remains somewhere else entirely. The previous chapter’s warning still applies: audience is not buyer access.

Earned trust is therefore not measured cleanly by followers, subscribers, reactions, or page views. Those tell you that attention occurred. If the purpose of the work is commercial trust, I want to look farther downstream. Do relevant buyers mention it? Do conversations begin at a more advanced level because the buyer already understands your thinking? Does your public work get forwarded inside the kinds of organizations you want to reach? Does a prospective customer say, in effect, “I’ve been reading what you’ve written about this, and I think you might understand our problem”? Those behaviors are more interesting than whether an algorithm briefly became fond of you.

Earned trust also compounds differently from warm or borrowed trust. A warm relationship usually belongs to particular people. Borrowed trust often depends on an intermediary remaining willing to connect you. Public evidence can remain available when you are asleep, in another meeting, or doing the apparently unfashionable work of actually building the product. That makes it potentially durable. It also makes it slow. You cannot publish one intelligent article on Tuesday and demand that the market trust you by Thursday. Reputation has an annoying preference for accumulating on its own schedule. For some products, that is fine. The founder can build useful public evidence while pursuing other acquisition paths, and over time more conversations begin with less uncertainty.

But an early business does not always have the luxury of waiting for every buyer to discover years of excellent work organically. Sometimes the right buyer does not know you, does not know anyone willing to introduce you, has never encountered your public work, and is not currently searching for what you sell. You may still have a very good reason to talk to them. At that point, you have to interrupt.

Transferred Trust

Trust can also move through a system the buyer already accepts. An official marketplace, a known integration, an established platform ecosystem, a reseller, an implementation partner, or a procurement-approved vendor relationship can transfer some confidence to a company the buyer has never dealt with directly.

The transfer is never complete. Being listed in a marketplace does not make a new product reliable, and putting a familiar logo in the integration section does not grant you the vendor’s reputation wholesale. What changes is the starting condition. The buyer may no longer be asking, "Who are these people and why are they anywhere near this workflow?" They may instead begin with a narrower question: "Does this extension of something I already trust solve the problem well enough?"

That difference can be constructed deliberately. If your buyers already live inside a trusted ecosystem, an integration can be a distribution decision as much as a product decision. If a consultancy already owns the relationship, a partnership can reduce the trust distance. If a community has earned credibility by filtering bad vendors, being invited into that community changes the introduction.

Do not confuse transferred trust with borrowed authority you did not earn. The partner, platform, or marketplace is placing some of its own reputation at risk, which is why credible trust paths usually have standards, review, or incentives attached. The useful question is not simply whether the lead is warm or cold. It is what existing source of confidence makes the next step feel less reckless to the buyer.

Build a Portfolio of Trust Paths

A founder who has finally found one acquisition path that works is usually in no hurry to complicate things. That instinct is healthy. If former colleagues are producing serious introductions, use them. If buyers keep finding you through a narrow search problem, learn how to capture more of that demand. If one consultant repeatedly puts the product in front of appropriate firms, do not interrupt a functioning commercial system because someone online announced that every company now needs a podcast. Early businesses often need focus more than diversification.

But focus becomes fragility when the entire path to customers depends on one person, platform, algorithm, marketplace, search term, community, or advertising account continuing to behave exactly as it does today. A consultant retires. A marketplace changes its ranking. Search results shift, advertising costs rise, a community bans promotion, and the colleague who made your first three introductions has now introduced you to everyone they reasonably can. Nothing is necessarily wrong with the product. The business simply depended on borrowed infrastructure that turned out not to belong to the business.

That is why I eventually want a portfolio of trust paths. Not a collection of marketing accounts, and not eight channels because eight feels diversified. A portfolio means the business has more than one credible way for a relevant buyer to move from not knowing you exist to taking the offer seriously. Those paths do not have to do the same job, and often they should not. A founder might earn trust through detailed public work, capture existing intent through search, create specific conversations through targeted outbound, and receive occasional introductions from customers or advisers. Another company might rely heavily on an industry marketplace for discovery while a partner network helps larger buyers through evaluation. A consumer application may use paid acquisition for reach while reviews, creator recommendations, and product experience carry most of the trust burden afterward. The paths reinforce one another.

This matters because, as the previous chapter noted, buyers rarely experience acquisition in the neat sequence our dashboards would prefer. A person may read something you published months ago, later hear your company mentioned by a colleague, search the name, and finally respond when someone forwards a case study. Software will assign the credit somewhere. What the buyer experienced was a path in which the article established expertise, the colleague supplied borrowed trust, search made the company easy to recover, and the later proof reduced uncertainty enough to act. Commercial systems become stronger when those pieces cooperate.

They become weaker when founders mistake diversification for scattering effort. I have seen the opposite pattern often enough to be suspicious of it. Revenue is weak, so the founder adds LinkedIn. Then cold email. Then a newsletter, then search articles, then a marketplace listing, then affiliates, then paid traffic. Six weeks later, every channel is underdeveloped, none has generated enough behavior to interpret, and the founder is maintaining a small media company around a product nobody has decided to buy. That is not a portfolio. It is unresolved uncertainty distributed across multiple browser tabs.

A better sequence is to let one or two plausible paths earn attention first. If warm relationships produce serious evaluations, learn what makes those evaluations serious. If a consultant introduces excellent buyers, understand why that consultant sees the fit and whether other people occupy a similar position in the market. If carefully targeted outbound produces conversations, study the conditions shared by the people who respond. Then look for a second path that either reproduces the useful condition or compensates for the first path’s weakness. That second path does not need to be large. If referrals are excellent but unpredictable, search may provide steadier discovery. If content creates recognition but few direct opportunities, outbound may turn that recognition into specific conversations. The point is not balance for its own sake. It is resilience and information. I would rather have two small trust paths I understand than six large channels whose contribution I cannot explain.

When evaluating a path, I care about more than how many people it reaches. Does it reach the kind of buyer who can plausibly purchase? What trust arrives with the encounter? How quickly can the path produce evidence? What does it cost in money, founder time, favors, or partner margin? Can I observe what happens after the encounter? Does the path teach me something even when the buyer says no? And if it works, is there a plausible way for it to produce another opportunity? Those questions make very different channels comparable without pretending they are identical. A warm introduction may score extremely well on trust and learning but poorly on repeatability. Cold outbound may provide excellent targeting and fast feedback while carrying a high credibility burden. Paid acquisition may be highly repeatable once the economics work, but expensive while the proposition remains uncertain. There is no universal winner. That is the point. The market, offer, buyer, price, risk, and founder’s existing position determine which combination makes sense.

For an early app builder, the practical exercise is not to select the fashionable channel. Take the paths currently available to you and ask which one creates the shortest credible route to a serious evaluation. Start there. Then ask what would happen if that route disappeared tomorrow. If the answer is that customer acquisition would stop completely, you have identified a dependency worth reducing, and the next path should be built deliberately rather than added because activity feels safer than diagnosis. Do not assume that the path producing the most traffic produces the strongest buyers. Follow the trust. A buyer may trust you because they already know you. They may borrow someone else’s confidence. They may inspect your public work and form their own judgment. They may respond to a well-targeted interruption, arrive with intent through search, or encounter you because you paid to be there. Each path creates different starting conditions, and your job is to understand those conditions well enough to choose rather than imitate.

By this point, the commercial problem has changed considerably from where the book began. We are no longer asking whether the app shipped, whether people say they like it, or whether posting more often might somehow produce revenue. We have a buyer, a problem, an offer, a price, a purchase moment, and one or more plausible routes through which trust can reach the market. Now people can actually enter the system.

That creates a new scarcity: your time. Once access improves, the founder can suddenly spend entire days in conversations. Some are flattering. Some are interesting. Some generate feature requests. Some come from people who love the idea but cannot buy anything. Some come from buyers close enough to a real decision that an hour with them could change the business.

The meetings all occupy the same sixty minutes. They are not worth the same sixty minutes.