Asher's Blog

Customers rarely buy only the function written on a product page. They may say they are buying payroll software, a background check, insurance, cloud storage, a security system or an investment product. But underneath the visible transaction, they are often buying something more emotional: the ability to stop thinking about a problem that has been occupying space in their minds.

They are paying to stop worrying. This is one of the things I think about whenever I build a product. I do not want to understand only the functional problem. I want to understand the emotional stress created by that problem. What is the customer afraid might happen? What are they checking repeatedly? What keeps them awake? What mistake could embarrass them, cost them money, damage their company or expose them to a penalty? What uncertainty have they reluctantly accepted because nobody has built a reliable way to remove it?

A good product completes a task. A great product reduces the customer’s anxiety about whether the task will be completed correctly.

That distinction is important because functionality is often easy to copy. Another company can reproduce a dashboard, add a button or advertise the same feature. It is much harder to reproduce the accumulated trust that causes a customer to say, “I do not need to worry about this anymore.”

The job behind the job

Clayton Christensen and his co-authors describe this idea in Competing Against Luck through the theory of “jobs to be done.” Customers do not simply buy products; they “hire” them to make progress in particular circumstances. The founder’s task is to understand the full progress the customer is trying to make, including its functional, social and emotional dimensions.

The functional job of payroll is to calculate and pay salaries. The emotional job is much larger. The employer wants to know that employees will receive the correct amounts on the expected day. The finance team wants to know that deductions have been calculated properly. The business owner wants to avoid discovering at the end of the year that the company owes a large statutory obligation, together with penalties and interest. The employee wants certainty that the salary on which a household depends will arrive when promised.

Nobody wants payroll merely because payroll is interesting. People want the consequences of payroll being right and the freedom not to think constantly about everything that could go wrong.

This is why a founder must look beyond the action performed by the software. A product may successfully initiate a payment and still leave the customer worried about settlement. It may generate a report and still leave the customer unsure whether the report is compliant. It may verify one piece of information while leaving the customer exposed to a larger risk.

If customers continue checking, calling, escalating and creating their own backup processes after buying your product, you may have solved the function without solving the worry.

Certainty is a product

Think about what it means for an employee to know that a salary will arrive on a particular day and at a predictable time.

That certainty affects decisions outside the payroll system. The employee can plan rent, school fees, transportation, savings and household expenses. The employer avoids the anxiety and reputational damage that accompany salary delays. The HR and finance teams do not spend the day responding to messages asking when payment will arrive.

The transaction may take only a few seconds, but the certainty surrounding it has been built through architecture, liquidity, reconciliation, support, security, processes and repeated performance.

The customer sees the result; the company must manage everything behind it. This is the deeper meaning of convenience. Convenience is not simply reducing the number of clicks. It is reducing the number of things the customer must remember, monitor and fear.

When a customer pays for insurance, the customer is buying a response to an event they hope will never happen. When someone pays a reputable accountant, they are not buying arithmetic; they are buying confidence that an expensive mistake will not be discovered later. When a business pays for cybersecurity, it is not because firewalls are exciting. It is because the business wants to continue operating without constantly imagining a breach. The strongest products convert uncertainty into a dependable outcome.

A background check is not a document

Background verification is another example. The visible output may be a report confirming identity, employment history, education, address or other relevant credentials. But the customer is not really buying a PDF. The company is trying to avoid giving the wrong person access to its money, systems, customers, data or reputation.

The consequences of getting this wrong can be enormous. In 2025, the United States Department of Justice announced coordinated action against schemes involving North Korean individuals who had fraudulently obtained remote IT jobs at American companies using stolen and fake identities. In April 2026, two United States nationals were sentenced for helping facilitate one such operation. According to the Justice Department, the broader scheme compromised the identities of more than 80 people, obtained jobs at over 100 companies and generated more than $5 million in illicit revenue. The department also reported access to sensitive company information and at least $3 million in legal, remediation and other damages to victim businesses.

That example changes the way we should think about employee verification. An unvetted employee is not merely an HR error. Depending on the role, it can become a cybersecurity incident, financial loss, regulatory breach, intellectual-property problem or threat to business continuity. The true product is therefore not “background checks.” The true product is a higher degree of confidence about the person to whom the company is granting trust.

No verification system can eliminate every risk. A responsible company should never promise absolute certainty where it cannot provide it. But a good product can make the risk visible, reduce it significantly and help the customer make a better-informed decision. That reduction in worry is valuable.

Trust must be designed into the company

Founders sometimes speak about trust as though it were a branding exercise. We think a polished website, a reassuring slogan or a recognizable investor will make customers feel safe.

Those things may help someone begin a relationship with the company, but lasting trust is operational.

Trust is created when the payment arrives; it is created when the numbers reconcile. It is created when customer support responds during a problem rather than disappearing. It is created when the company protects customer data, communicates honestly, keeps adequate liquidity and refuses to take risks with money that does not belong to it.

The emotional experience of the customer is downstream from the operating decisions of the company.

If customers are anxious, the problem may not be the colour of the interface or the wording of the notification. The product may be exposing an underlying weakness in settlement, reconciliation, security, communication or support. You cannot design calm on the screen while creating danger behind it.

Peace of mind is not copywriting; it is the result of a well-run system.

What certification does—and does not do

This is one reason standards and certifications matter. ISO explains that certification can add credibility by demonstrating that a product, service or management system meets defined expectations. For example, an independent certification audit can evaluate whether an organization’s management system conforms to the requirements of a relevant ISO standard. The process can require the company to define responsibilities, control variations, use evidence, document processes and pursue continual improvement.

For a customer, this offers an additional layer of assurance. It says that the company is not merely asking to be trusted on the strength of its own claims; aspects of its system have been assessed against an established standard by an external certification body.

But we must describe this carefully. ISO itself does not certify companies, and certification is not a guarantee that nothing will ever go wrong. A certificate cannot replace competent employees, good judgment, sufficient capital, continuous monitoring or responsible leadership. It is evidence of a system and a level of scrutiny, not a promise of perfection.

For us at Eazipay, obtaining relevant certifications is part of building the architecture of trust. It communicates that security, quality and process are being treated seriously. Yet the responsibility continues after the audit; the company must live the process every day.

Young businesses that cannot yet afford formal certification do not have permission to ignore the underlying risks. Long before a certificate is possible, a founder can map critical processes, define access controls, separate duties, maintain audit trails, protect credentials, test backups, prepare incident responses and ask qualified experts to challenge the system. The certificate may come later; the responsibility begins immediately.

Your economics are part of the customer experience

There is another side of customer reassurance that founders often overlook: the economics of the company itself.

If your business model is structurally unsound, your customers are not safe simply because the product works today.

I once heard about a business that was paying more in transaction costs than it charged customers. I heard about another arrangement in which a company promised customers immediate settlement even though its payment-infrastructure provider settled with the company on a T+1 basis—the next business day. The company was effectively financing the timing difference itself.

There can be strategic reasons to subsidize a product temporarily, and prefunding can be managed responsibly when it is deliberate, adequately capitalized and carefully controlled. The problem is not automatically that the company pays before it receives settlement. The problem is making a permanent customer promise without understanding or funding the liquidity obligation created by that promise.

Every transaction then widens the exposure. Growth makes the problem larger rather than solving it.

If a company earns less on a transaction than it spends to complete it, volume may accelerate its losses. If customer withdrawals can occur immediately but the company’s assets cannot be converted into cash quickly, a liquidity mismatch has been created. If the business borrows expensively to fund a promise for which customers are not paying, the experience may look seamless while the company is quietly becoming fragile.

That fragility eventually reaches the customer. It appears as delayed transactions, unexplained restrictions, poor support, lost balances or, in the worst case, the disappearance of the company. The founder’s failure to understand margins, settlement cycles and liquidity becomes the customer’s anxiety and loss.

Business continuity is therefore part of product design. The customer is not only buying what the company can do today. The customer is relying on the company still being capable of doing it tomorrow.

The risks customers cannot see

Some of the most important founder decisions involve risks the customer will never know existed.

Customers do not see the conversations about who can authorize a payment, how frequently balances are reconciled, what happens when a bank or payment provider is unavailable, where personal information is stored or how the company responds when an employee’s access should be revoked.

They may never know about the fraud that was prevented, the incorrect transaction that was stopped or the vulnerability that was fixed before it was exploited.

This invisibility can tempt a young company to postpone the work. There is always a visible feature to build, a campaign to launch or a customer request to answer. Controls feel slower because their value is often measured through events that do not happen.

But prevention is a product outcome. A founder should deliberately identify what could cause irreparable harm to a customer. Customer money is an obvious category. Personal and business data are another. There are also regulatory filings, identity decisions, access permissions, investment instructions and records on which future decisions will depend.

For each area, the company should ask: What is the worst credible failure? How would we detect it? Who could cause it? What control prevents it? What would we do if the control failed? How quickly could we restore service? How would we communicate with affected customers?

These are not questions to reserve for large companies. The consequences do not wait for the company to become large before arriving.

Do not promise “worry no more” carelessly

The ideal product helps customers worry less, and perhaps eventually not worry about that particular task at all. But a company must be careful not to create false reassurance.

There is a difference between transferring responsibility and pretending risk no longer exists.

A payroll company can automate calculations and filings, but the employer may still need to provide correct employee information and maintain adequate funds. A background-check company can verify available records, but it cannot guarantee the future conduct of an employee. An investment platform can improve access and reporting, but it cannot eliminate market risk. A cybersecurity provider can reduce exposure, but it cannot promise that an attack will never succeed.

Trust grows when the product tells the customer what it handles, what remains the customer’s responsibility and what happens when exceptional circumstances arise.

The objective is not to hide uncertainty; it is to manage it honestly and competently.

Sometimes the most reassuring sentence a company can say is not “Nothing can go wrong.” It is: “We have considered what can go wrong, we have built protections around it, and if an incident occurs, this is exactly how we will respond.”

Build for the moment of anxiety

If you want to understand the quality of your product, observe it at the moment when the customer is most worried.

What happens when payroll is approaching and the account has not been funded? What happens when a transfer appears delayed? What happens when a suspicious employee credential is discovered? What happens when a statutory deadline is hours away? What happens when a customer fears that money or data may have been compromised?

Many products are designed for the happy path, when all information is correct and every external provider is working. Trust is built on the unhappy path. That is when customers discover whether the company has thought deeply about their reality.

A reassuring product should make status visible. It should tell the customer what has happened, what is happening next, whether action is required and when the issue should be resolved. It should provide access to a capable human being when automation is insufficient. It should avoid vague language and empty assurances.

Silence multiplies anxiety. Clarity reduces it. The founder should therefore design not only the successful transaction but also the exception, delay, reversal, complaint and recovery. Customers will forgive some failures when the company communicates early, takes responsibility and resolves the problem. They are less likely to forgive confusion, defensiveness or disappearance.

The questions every founder should ask

When we are designing or reviewing a product, I believe we should ask questions that go beyond functionality:

• What is the customer worried will happen before using this product?
• What are they still worried about after using it?
• What do they repeatedly check because they do not fully trust the outcome?
• What is the financial, emotional and reputational consequence of failure?
• What hidden dependencies could prevent us from keeping our promise?
• Are our margins and liquidity strong enough to keep serving customers as we grow?
• Who has access to customer funds and data, and how is that access controlled?
• What evidence do we give customers that the system is working?
• What happens when an external provider fails?
• How quickly can we detect, explain and correct a mistake?

The answers may lead to new features, but they may also lead to changes in finance, operations, security, staffing, contracts or customer communication. That is because the product is not merely the software. The product is the entire system that produces the customer’s outcome.

The company takes over the worry

The best way I can describe a strong product is this: the company accepts responsibility for understanding a problem more deeply than the customer should have to.

The customer should not need to become an expert in payroll legislation before paying employees. The customer should not need to understand every settlement arrangement behind a transfer. The customer should not need to know every technical method used to protect a database. The company studies those complexities, builds the appropriate safeguards and presents the customer with a simple, dependable experience.

This simplicity is not the absence of complexity; it is complexity responsibly absorbed by the provider.

That is what people are willing to pay for. They pay for the salary to arrive; they pay for the filing to be accurate. They pay for the candidate to be properly checked. They pay for the data to remain protected. They pay for someone competent to have anticipated the problem before it becomes an emergency.

Ultimately, customers pay to recover attention. They want to return to their businesses, families and lives without carrying the unresolved problem in their minds.

So when you are building a product, do not ask only, “Does it work?”

Ask whether it creates certainty. Ask whether it reduces the customer’s need to check. Ask whether your operating model can sustain the promise. Ask whether you have protected the things whose loss would be irreparable. Ask what still makes the customer anxious and what responsible action would remove that anxiety.

A good product performs a function; an important product earns trust.

And when that trust is supported by sound systems, honest communication and a business capable of enduring, the customer receives something more valuable than a feature: the freedom to stop worrying. —

References and further reading

• Clayton M. Christensen, Taddy Hall, Karen Dillon and David S. Duncan, Competing Against Luck: The Story of Innovation and Customer Choice.
• Donald A. Norman, Emotional Design: Why We Love (or Hate) Everyday Things.
• United States Department of Justice, Coordinated actions against North Korean remote IT-worker schemes.
• United States Department of Justice, Sentencing of two facilitators of a fraudulent remote IT-worker scheme.
• International Organization for Standardization, Certification and ISO 9001 explained.