Startups with a Customer-Centric Mindset
Introduction
One evening, I was sipping tea with a friend, the founder of a startup whose team you could count on your fingers. He was talking with enthusiasm about his absolute belief in customer experience principles, and how he saw his product’s success as tied to its ability to win hearts before money. But amid that enthusiasm, there was one obstacle imposing itself on the table: he had no budget to hire a dedicated customer experience specialist, full-time or even part-time.
Did this mean he had to put off applying customer experience principles until his company grew? He asked, looking at me as if searching for an answer that would rescue him from this bind. I smiled, and gave him a short response: the road to an exceptional customer experience doesn’t start with a department or a full-time employee. It starts with a mindset and simple steps that can be executed even by a startup team of just five people. I then asked him for some time to organise my thoughts and give him a detailed answer.
In this article, I answer his question. If the question drew you in and you want to know the answer, read on.
Lead by Example
Tony Hsieh, the founder of Zappos, led his company with a customer-centric culture to the extent that, for ten years before Amazon’s acquisition, he didn’t need to set up a separate customer experience department. The culture he started himself made every member of the team live the experience and serve the customer as part of their daily work, without waiting for instructions, policies, or procedures.
If you want the customer to be present in the mind and heart of every member of the team, remember that your team is constantly watching you and learns from your words and actions more than from any guide or policy. When you place the customer at the centre of your discussions and decisions, and clearly show that what matters to you is the impact of the work on their experience, everyone will start mirroring and adopting your behaviour. Over time, these individual practices transform into a firmly established fabric in the company’s culture, making serving the customer a collective and natural responsibility, not an imposed task.
To embed this culture in practice, customer problems and challenges can become a standing item on the agenda of regular team meetings, whether weekly or monthly. In this item, the team discusses real cases customers have faced, what caused the problem, how the team responded, and what changes or improvements could be made to avoid recurrence. Small success stories can also be reviewed, where a customer problem was solved in an innovative or fast way, so they become a source of inspiration for others. See also Customer-Centric Operating Model.
Understanding the Customer
If we implicitly agree that we innovate services or products for the customer, and we don’t disagree that our business model and the sustainability of our profits will be tied to how successful our services or products are at meeting our customers’ needs or solving their challenges, why don’t we work hard to make understanding our customers an ongoing habit on our agendas?
Many founders fall into the trap of assumption (“I think the customer…”). If you want to understand your customer well, you first need to be convinced that you are not the customer, that you don’t represent them, and that you don’t understand how they think or behave, even if you are the very person experiencing the problem you’re trying to solve. Drop your ego, strip yourself of your beliefs, and don’t assume anything on behalf of the customer, because you will be the role model for everyone working with you.
All you need to understand your customer is to build a weekly habit of discovery to probe the needs of the target segment and the challenges that trouble them and for which they haven’t found alternative solutions, through interviews and tests, to tie product development decisions to real value for the customer and commercial value for the company. The matter isn’t complex, and you don’t have to be a seasoned researcher to conduct these interviews, because it’s a skill that develops with practice. The most important thing in the discovery process is for your focus to be on the problem space, not the solution space. In the founding stage, make your entire focus crystallising the problem clearly, because everything you’ll build later depends on this sensitive point, which saves you months of work that may potentially be wasted if you’re solving a fictional problem your mind created rather than a real problem your target customers face.
If the problem has crystallised for you, you can maintain a group of customers who believe in your idea and meet with them regularly to discuss product developments and consult them on the road map, what’s known as a Customer Advisory Board practice. You have to interact with them constantly and give them an incentive that encourages them to stay with you. For example, a free subscription to the service for life. See also Voice of Customer (VoC).
The Customer Journey
Everyone has heard the idea of placing the customer at the core of your decisions, but few have mastered applying it. To begin with, let me tell you that you make hundreds of decisions every day, and it’s intuitive that it’s impossible for you to think about the customer before every decision. But I’ll suggest a good alternative: draw a (hypothetical) and comprehensive customer journey map that includes all the stages the customer will go through, not just in using the service/product but what happens before that and what happens after. Then, on a weekly basis, modify it to become real based on the facts you gather from the previous habit.
The advice here is to avoid the common gap that occurs between what the customer experiences on the ground and what you think/assume you’re providing your customer. You and all members of the company have to look at what you offer holistically, not as isolated stages, because this will help you make sure the experience is consistent and seamless across all stages and touchpoints. See also Customer Journey Mapping and Service Blueprint.
ℹ️ Are you not familiar with the customer journey tool? Watch this video to form a clear picture of it.
Measuring Experiences
It isn’t wise in the early stages to dive into quantitative measurements or to drown customers in surveys. Most people have started ignoring them on purpose. In this period, your effort should be focused on one core thing: making sure that the solution space you provide, whether a service or a product, genuinely addresses a real problem or challenge facing the target segment, meets their expectations, and that they’re willing to pay money for. In this stage, qualitative data remains far more important than quantitative data, because it gives you a deeper understanding of customer motivations and behaviours.
Avoid the obsession with numbers, or what could be called the “worship of quantity”. Don’t busy yourself now with metrics like satisfaction or loyalty rates, and don’t focus on increasing the number of visitors or the time they spend on your site. The more important thing is to help customers find what they need easily, and to provide them with real value that solves their problems. Your appreciation for their time and your respect for their minds is what will guarantee you sustainable success, not flashy showmanship or repetitive, empty content. See also NPS, CSAT, CES.
In this early stage, it’s important to start thinking about the operational metrics that can reflect the state of the experience without the need for direct communication with customers. What is meant here is that you work on building the data infrastructure correctly from the start, so that later it enables you to measure experience metrics accurately and easily. This early investment in establishing an effective measurement and operating system will save you a lot of time and resources in the future, and give you continuous visibility into the state of the experience without the need to rely entirely on surveys or direct communication with customers.
Designing and Improving Experiences
The process here is exactly like a continuous life cycle that doesn’t stop. You start first by understanding the problem space precisely, then move to defining a solution space, which can be considered the design side. After that, the validation stage begins to verify the soundness and effectiveness of this solution with customers through tests and actual trials. As soon as you’ve identified the strengths and weaknesses, you move to the improvement stage and make the necessary adjustments.
With your commitment to the weekly habit of understanding customers, you come back again to add more features and characteristics to the solution. That is, you enter again into the design stage, then test these additions with customers, to enter again into the improvement cycle. Every now and then, you may notice a drop in some operational metrics, which calls for searching for the root cause of these changes and working to address it, which may require designing a new solution or improving the existing one. Likewise, you may receive complaints from customers about difficulties in use, so you redesign some parts or improve their design, so that the process remains in a state of constant movement that doesn’t stop. See also Closed-Loop Feedback.
But beware of falling into the minimum viable product trap. The problem isn’t with the concept itself, but with its poor application. It’s true that you don’t need to invest large amounts in the first version of your product or one of its features, but the fatal mistake is to forget completely that this initial product needs later development. With the crowding of priorities, the second stage of its development may not come at all, leaving the product or feature in its incomplete state as a half-finished solution, which weakens the experience and harms the customer in the long run.
My advice here is to have a clear reference file for all improvement and design initiatives, whose main goal is meticulous follow-up and not unintentionally overlooking any initiative. Review this file weekly, and make sure to prioritise based on clear criteria that help you determine what should be executed first and what can be postponed, so that you can balance developing new features with completing the improvement of existing features or products, instead of having initiatives pile up without being completed.
Human Capital
No startup, no matter how innovative the idea or distinctive the product, can deliver an exceptional customer experience if it neglects its employees. In a small team environment, every employee is like the first line of defence and the real ambassador of the company’s culture in front of the customer. Therefore, respecting and appreciating human capital is considered a strategic necessity for building a successful and sustainable customer experience.
In startups, the founder or founding team may make a common mistake: looking for people who “follow orders” instead of looking for people smarter than them and more capable of seeing what the founder themselves may not see. Great teams aren’t built from human robots, but from people with critical minds, innovative ideas, and a passion for initiative.
Hire people smarter than you, and listen to them. Don’t tie them to rigid task lists, and don’t close the door to their opinions because the “idea” is your spoiled child. Make the work environment a safe space for discussion and experimentation, where every individual feels their voice is heard and their contribution actually impacts the company’s future. The employee whose opinion is respected and who is given space to influence will pass on this sense of empowerment to the customer in every interaction.
And remember that in the small team, every employee wears several hats and plays several roles. This diversity in roles is a golden opportunity to build a shared culture where everyone sees the full picture, not just a part of it, and feels they’re participating in creating the experience, not just in executing it.
Startups that respect their employees, invest in their training, and give them trust don’t just get higher performance; they build an internal loyalty that is directly reflected in customer loyalty. Simply, a happy and motivated employee makes a happy and loyal customer.
Which Type of Growth is Best?
SLG or PLG or CLG | (Sales/Product/Customer)-Led Growth?
Which is the better approach to growth: sales-led growth, product-led growth, or customer-led growth?
There is no magic recipe that fits all startups. The most suitable approach is the one that balances the speed of the customer reaching value with the complexity of the purchase decision. Customer-led growth is like a lens you must always wear, so as not to drift away from what matters to the customer. If you find you’re spending a lot to acquire a new customer, your product likely isn’t meeting market needs, and your spending is just an attempt to fill this gap.
In the idea stage, before reaching product-market fit, let customer-led growth be what you follow, which is what we’ve detailed in this article. Add to that the product-led growth approach in a small version to verify the speed of reaching value.
When moving to the early-fit stage (less than 10 million riyals in annual revenue), make product-led growth the default approach if the product reaches value quickly and doesn’t need complex integrations, while adding sales-led growth for large accounts or those that need human nurturing, while maintaining customer-led growth as a guide for the road map.
In the expansion stage toward mid-market or large enterprises, blend product-led growth through self-onboarding with sales-led growth via human intervention for expansion and closing deals, while always maintaining customer-led growth as the primary lens guiding what you build and how you deliver it.
The bottom line: customer-led growth remains present and accompanies the startup at all its stages, as the compass that prevents it from drifting away from what actually matters to the customer.
In Closing
I return to that conversation that was the initial spark for writing these lines. In short, a startup doesn’t need a huge budget or a specialised team to start applying customer experience principles. All it needs is a mindset led by the founder through example, and an ongoing habit of understanding customers and improving what is provided to them. And customer-led growth remains the compass that keeps the company from drifting away from its customers’ real needs.
To my friend Ayman Ezzat, who carried the customer’s concern in his heart before his team or budget grew, I dedicate this article and wish you and your company all success, and that the customer’s needs remain the compass that guides you at every stage of your journey. Resources may grow over time, but the customer-centric mindset is the real capital that every company should invest in from day one.
← Articles MOC