How to Scale a Pretzel Business? Expert Tips Inside

Start With Customer Pain, Not Your Vision

Most founders fall in love with their idea before they fall in love with their customer’s problem. I did. We all do. But here’s the brutal truth: nobody cares about your vision. They care about whether you’re solving something that keeps them up at night.

The best validation work I’ve seen doesn’t happen in a conference room. It happens in coffee shops, Slack groups, Reddit threads, and DMs. You’re looking for the moment when someone says, “Oh my God, yes, I’ve been dealing with this forever.” That’s not a compliment—that’s a customer.

Here’s what this actually looks like: You pick a specific problem. You find 20 people who have that problem. You ask them about it for 30 minutes. You listen more than you talk. You don’t pitch. You don’t sell. You just understand. Write down what they say. Look for patterns. If five people mention the same frustration without you leading them there, you might have something.

The entrepreneurs who skip this step? They build in a vacuum. They optimize the wrong things. They end up with a beautiful product nobody wants. Don’t be that founder.

Build Your MVP Like You’re Broke (Because You Might Be)

An MVP isn’t a watered-down version of your dream product. It’s the smallest thing you can build that teaches you something true about your market. It should take weeks, not months. And it should cost almost nothing.

I’ve watched founders spend six months and $50K building features that users never touched. Meanwhile, the founder working from her laptop with a $200 budget and a spreadsheet found product-market fit in three weeks. The difference? One was building. The other was learning.

Your MVP should be embarrassing. If it’s not, you waited too long. Measuring success at this stage isn’t about polish. It’s about whether people will use it, recommend it, or pay for it. That’s it.

Some of the fastest founders I know started with:

• A Google Form and a spreadsheet
• A no-code tool like Webflow or Bubble
• A landing page and a waiting list
• A manual service (you do the work yourself for the first 10 customers)
• An existing platform with a unique angle

The constraint forces creativity. It forces you to focus on what actually matters. And it keeps you from burning money on the wrong things.

The Art of Talking to Customers Without Being Creepy

Customer development is a skill, and like most skills, you’ll be terrible at it at first. You’ll over-explain. You’ll pitch too early. You’ll ask leading questions. That’s normal. Get over it and keep practicing.

The goal of a customer conversation isn’t to close a sale. It’s to understand how someone thinks about the problem you’re solving. You want to know their current workaround. You want to know what they’ve already tried. You want to know what they’d pay and when they’d pay it.

Here’s the framework that actually works:

1. Ask about their current situation. “Walk me through how you currently handle this.” Let them talk. Don’t interrupt.
2. Ask about their frustrations. “What’s the hardest part about that process?” Listen for emotion. That’s where the real pain lives.
3. Ask about their attempts to solve it. “Have you tried anything to make this easier?” This tells you about competitive awareness and their willingness to invest in solutions.
4. Ask about their priorities. “If you could change one thing, what would it be?” This is the north star for your product roadmap.
5. Ask about their willingness to use your solution. “If we built something that did X, would you use it?” Not “Would you buy it?” Just use. Usage is the real metric.

Then—and this is important—shut up and listen. The silence is uncomfortable. That’s where the good stuff comes out.

Document everything. Look for patterns across conversations. If you’re hearing the same thing from different people in different contexts, you’ve found something real.

Funding Isn’t a Finish Line—It’s a Starting Gun

There’s this weird mythology around fundraising. Like getting a check is the moment you’ve made it. It’s not. It’s the moment the real pressure starts.

I’ve seen founders raise money and immediately lose focus. They hire too fast. They build too much. They optimize for investor metrics instead of customer metrics. A year later, they’re out of runway, out of options, and out of luck.

The best founders I know treat early funding like oxygen. It’s necessary, but it’s not the goal. The goal is building sustainable revenue. If you can get customers before you raise money, you’re playing from a position of strength. You know your unit economics. You know your customer acquisition cost. You know what works.

When you do raise money—whether it’s friends and family, angels, or VCs—use it strategically. Here’s what I’d prioritize:

• Customer acquisition (the only thing that matters)
• Product development (only features that customers ask for)
• Hiring (only when you’re drowning in work)
• Infrastructure (only when you’ve outgrown free tools)

Everything else is noise. Y Combinator’s library has solid frameworks on this if you want to go deeper.

Hiring Your First Team Members

Your first hires will make or break you. I mean that literally. One bad hire at the early stage can derail a company. One great hire can accelerate you by years.

Most founders hire too fast and for the wrong reasons. They’re overwhelmed, so they hire someone to take things off their plate. But if you’re not crystal clear on what needs to be done and how to measure success, you’re just hiring someone to be overwhelmed alongside you.

Here’s what I’ve learned: your first hire should be someone who’s better than you at something you’re not good at. If you’re a builder, hire someone who’s great with customers. If you’re a hustler, hire someone who can actually execute. Complementary skills matter more than pedigree.

And please, for the love of everything, hire slowly. Interview at least 10 people for your first role. Have your customers talk to them if possible. Give them a small project before you commit. You’re not just hiring someone—you’re building your culture. That matters more than you think.

For building your early team, focus on people who’ve done something before. They don’t need to have worked at Google. They just need to have shipped something, anything. That experience matters.

Metrics That Actually Matter

Early-stage founders obsess over vanity metrics. Downloads. Page views. Followers. None of that matters. What matters is retention, revenue, and growth rate.

Here’s what you should actually track:

• Weekly active users or monthly active users. Are people coming back? If not, you don’t have a product—you have a novelty.
• Churn rate. How many customers are leaving each month? If it’s more than 5-10%, something’s broken.
• Customer acquisition cost. How much are you spending to get a customer? If it’s more than they’ll pay you in year one, you’ve got a problem.
• Lifetime value. How much will a customer pay you over their lifetime? LTV should be at least 3x CAC.
• Revenue growth rate. Week over week, month over month. This is your heartbeat.

Everything else is context. Build a simple spreadsheet. Update it every week. Share it with your team. Let the numbers guide your decisions.

The founders who make it aren’t the ones who’ve figured everything out. They’re the ones who’ve learned to make decisions with incomplete information, adjust when they’re wrong, and keep moving. That’s the skill. That’s the game.

If you’re in the thick of it right now—building something, talking to customers, losing sleep over metrics—you’re doing the work. The hard part isn’t the idea. It’s the execution. It’s showing up every day and getting one percent better. That’s how companies actually get built.

For a deeper dive into lean methodology and startup execution, Harvard Business Review has some solid resources. And if you’re looking for practical frameworks, the SBA has free resources on business planning and startup fundamentals on Entrepreneur.com are worth your time.

FAQ

How long should I spend validating before I build?

4-6 weeks if you’re doing it right. Talk to 20-30 people. Look for patterns. If you’re hearing the same problem over and over, start building. If you’re not, pivot or pick a new problem. Don’t overthink it.

Should I quit my job to start a company?

Not necessarily. Build nights and weekends until you have clear traction. Revenue, users, or investor interest. Once you have one of those, the decision becomes easier. The runway you have matters, and the risk you can afford matters.

How much money do I need to start?

Less than you think. If you’re bootstrapping, you can get to MVP for under $1K if you’re lean. If you’re raising, $250K-$500K is a reasonable seed round. But money is a tool, not a signal of success.

What’s the biggest mistake early-stage founders make?

Building without feedback. Falling in love with their idea instead of their customer’s problem. Waiting too long to talk to users. Then when they do talk to users, they pitch instead of listen. The pattern is: build in isolation, launch with hope, wonder why nobody cares.

How do I know if I should pivot?

If you’ve talked to 30+ potential customers and fewer than 20% are excited, pivot. If your retention is below 20% after a month, pivot. If you’ve been growing at less than 10% week over week for three months straight, pivot. Data tells you. Listen to it.