Intro
Startup growth rarely fails because of one big mistake. It usually breaks under the weight of small missteps: hiring the wrong person too early, building features without customer proof, or letting communication drift until teams operate in silos. In this episode of the DevReady Podcast, Andrew Romeo (CEO and Co-Founder of Aerion Technologies and Co-Founder of DevReady.Ai) sits down with Jarren Pinchuck, Operations and Growth Executive and Advisor at Startmate, to unpack what founders can do differently from day one. They explore how to hire for culture fit without relying purely on gut feel, how to run customer discovery conversations before you have a product, and why customer-led teams build stronger products faster.
Jarren Pinchuck’s startup journey, from hospitality to tech
Jarren’s career is built on a pattern many founders recognise: learning by doing, making fast decisions, and figuring it out while the work is happening. He started in South Africa, studied marketing, advertising and communications, then quickly realised the advertising world was not for him. After six weeks in an ad agency, he made a sharp pivot into hospitality, motivated partly by the need to earn more money and fund travel.
That restaurant environment became a practical training ground for growth and operations. You do not get hidden behind email threads when a customer is unhappy in a busy venue. You learn service recovery quickly, you learn how to communicate under pressure, and you build a strong instinct for what customers value.
For Jarren, those years created a foundation he still uses today. He learned that most businesses share the same fundamentals: you market and sell a service, you focus on repeat customers, and you earn referrals by delivering a great experience. It is simple, but not easy, and the details matter.
The first product: solving a real operations problem in restaurants
Andrew asks how Jarren’s first tech product came to life and what gap he noticed in the market. Jarren points to something surprisingly small but deeply familiar to anyone who has worked in hospitality: the kitchen bell. Food is ready, it sits at the hatch, and the chef rings a bell to signal the waiting staff. It is inefficient, it is annoying, and diners can hear it more than people realise.
On a trip to the United States, Jarren saw pager technology used in food courts, where customers can walk around until their pager buzzes. He also discovered that similar systems existed for waiters and waitresses, with small devices worn on the hip. The kitchen could trigger different alerts, like “food ready”, “clear plates”, or other service cues.
For large restaurants and noisy venues, this solved a genuine coordination problem. Staff could not always hear the bell, the kitchen could be far away, and loud environments made communication unreliable. Jarren and his team brought the solution to South Africa, treated setup and programming as part of onboarding, and managed the technical side themselves because restaurant owners did not want to deal with it.
What went wrong: market timing, sales volume, and scalability
The episode does not gloss over the hard parts. Andrew asks what the door to door selling experience was like and what Jarren learned from it. Jarren is candid: they were likely too early to market in South Africa. Many customers had not even seen paging solutions in food courts yet, which meant the “new behaviour” hurdle was high.
There were also practical and commercial challenges. Jarren realised he was not selling with enough volume and that his approach was not scalable. Selling one unit, installing one unit, then servicing one unit created a bottleneck, because he was stuck delivering each step himself.
The product also came with troubleshooting issues. Signal frequency could fail in some venues, especially across multiple levels, and repeaters were sometimes required. Bootstrapping left limited time and resources to solve all of those operational constraints properly. Looking back, Jarren believes there was a stronger opportunity in food courts and takeaway environments, but he did not pivot quickly enough.
That reflection matters for founders. Product success is not only about building something useful. It is also about choosing the right market entry point, validating urgency, and designing a delivery model that can scale beyond your own time.
Pivoting into recurring revenue and learning growth fundamentals
After the paging product, Jarren and his partner pivoted into a corporate coffee model. It was a major shift, but it came from the same source: paying attention to people and noticing what they struggled with. They had built relationships with wealthy business customers through hospitality and saw a gap. Good coffee was not widely accessible in offices, the machines were expensive, and many workplaces could not offer a high-quality experience to visitors and staff.
Their solution was a lease-style model. They supported and serviced machines, partnered with a finance company, and made money through ongoing coffee bean distribution. The hardware enabled the relationship, but the consumables created recurring revenue, which is a useful lesson for founders thinking about sustainable business models.
Jarren later moved into water purification, then relocated to London, where he spent years in online gaming and casinos. That period marked his deeper exposure to tech, platforms, payments, and SEO-driven growth. The skills translated directly into modern product marketing and acquisition: driving traffic to a product or landing page, improving conversion, and building growth systems.
Why Jarren loves startups and what founders often underestimate
Andrew asks what keeps Jarren in startups, given the high-velocity pace. Jarren describes loving scrappy environments where there is always something to fix, improve, or test. The work is never fully done, but the feedback loop is fast. You can often see the impact of what you did yesterday, even if it is a small improvement.
That speed is also why startups amplify problems. A miscommunication becomes a product mistake quickly. A poor hire can distort priorities and slow progress. A lack of customer contact can push a roadmap into the wrong direction. The same intensity that makes startups exciting also increases the cost of getting the basics wrong.
Startup hiring: culture fit, communication, and alignment
A major theme of the episode is hiring. Jarren argues that people are the most important part of any business, but in early-stage startups the margin for error is much smaller. In a team of five to fifteen, one or two misaligned people can “wreck the whole” effort by pulling against the founder’s vision, disrupting communication, and impacting customers or product direction.
Andrew expands on the challenge: people bring their own personal values into a business, but teams still need a shared professional value system that supports the mission. Jarren agrees and says that while gut feel is a helpful starting point, he also relies on a structured hiring framework.
For technical roles like engineering, skill testing matters. But for most roles, the key factors include communication style, curiosity, and cultural fit, especially where the role influences customers. Jarren emphasises that product managers and engineers should meet customers too, because product decisions need real feedback, not internal assumptions.
A practical tactic: get customers in front of the team
Jarren shares a tactic that many startups can implement quickly: customer show-and-tell sessions. In one company, a customer success manager brought in a customer once a month to explain how they used the product, what challenges they faced, and what outcomes they needed. Developers and product managers attended, listened, and asked questions directly.
The result was energising. Engineers could see the real value of what they were building, and they often spotted simple improvements quickly, sometimes a small change that solved a problem immediately. Andrew highlights the motivation benefit too: most people do not want to build features that sit unused, and direct customer feedback reduces that risk.
Customer discovery before the product: a mindset shift that works
Andrew asks how founders can get in front of customers early, even before a product exists, without fear of pushing ideas out too soon. Jarren’s answer is a mindset shift: early conversations should not be framed as sales. They should be discovery, learning, and sometimes education.
He points out a simple truth that founders can use: people like talking about themselves, especially business owners. The harder part is not getting them to share problems, but finding the time. When founders lead with “there is no sales pitch, we are learning about problems in your industry”, many people are open to the conversation because the downside is low and the potential value is high.
Andrew adds an important practice: avoid leading the conversation with your solution. If you tell people what you are building too early, you can unintentionally influence their answers. Better discovery comes from asking open questions, understanding what customers do today, and letting insights emerge without forcing them.
Jarren closes this loop by saying that open-ended customer conversations often reveal unexpected “gold” that founders would never find if they only asked narrow, solution-led questions.
Topics Covered
- Jarren Pinchuck’s startup journey from South Africa to Australia
- Customer service lessons from hospitality and how they shape founders
- Identifying market gaps and turning operational pain into product ideas
- Launching a first tech product in hospitality and what worked, what did not
- Early sales execution, scalability challenges, and learning to pivot
- Building scrappy startup operating rhythms and responding to fast feedback loops
- Hiring for culture fit, communication, and alignment with founder vision
- Bringing engineers and product teams closer to customers for better product decisions
- Customer discovery before product build, including how to run non-sales conversations
Key takeaways from this episode
- Early-stage hiring has a smaller margin for error, and culture misalignment can derail product and customers quickly.
- Customer discovery should be framed as learning, not selling, especially before you have a product.
- Teams build better products when engineers and product managers stay close to real customer feedback.
- Trust and communication are not “soft” topics, they are operational systems that must scale with the business.
- Being customer-led is a competitive advantage because it reduces guesswork and accelerates iteration.
Useful Links
FAQs
What is culture fit in startup hiring?
Culture fit means hiring people who align with how your team communicates, works, and makes decisions, not just their skills.
What is customer discovery in early-stage startups?
Customer discovery is speaking with potential customers to understand problems, workflows, and needs before building a product.
How do you talk to customers without selling?
Position the conversation as learning and discovery. Ask open questions and focus on their challenges, not your solution.
