Hien Phan
Hien Phan
WorkAI craftWritingAbout
WorkAI craftWritingAbout

Apps

SpeakEn
Back to Writing

What I Learned from My First Sales Call

The idea of selling felt terrifying. I recount my very first direct sales interaction, the mistakes I made, and the unexpected lessons I learned about valuing my product.

December 15, 2024•5 min read•Hien Phan
Indie Hacking
mvp
learning
mistakes

My palms were sweating. My throat felt like it was closing up. This was it - my first real conversation about selling my product.

For weeks, I’d been building and refining "TaskFlow," my little app designed to help solo founders organize their day. I loved the building part, the problem-solving, the coding. But the idea of actually talking to someone, asking for money, felt like a mountain I couldn't climb.

A person with sweaty palms holding a laptop, looking nervous.

The Fear of the "Ask"

Selling felt…icky. Like I was bothering people or trying to trick them into buying something they didn't need.

My internal monologue was a disaster: "What if they think it's overpriced? What if they don't see the value?

What if I sound like a total amateur?"

This fear kept me from reaching out to potential users for feedback, let alone sales. I was stuck in this loop of perfecting the product in isolation, convinced that eventually, it would just sell itself. Spoiler alert: it doesn't.

My "Discovery Call Basics" Framework

To finally break through this, I decided I needed a simple plan. I wasn't going to become a sales guru overnight, but I could at least have a structured conversation. I came up with what I called "Discovery Call Basics."

It wasn't a rigid script, but more of a mental checklist and guiding questions:

  1. Understand Their Problem: Start by asking them about their biggest challenges related to the problem my app solves.

What’s their current workflow? What frustrates them?

  1. Listen More Than You Talk: This is crucial.

People want to be heard. My job was to understand their pain points, not to immediately present my solution.

  1. Gently Introduce Your Solution: Once I understood their needs, I could see if TaskFlow was a good fit. I'd explain how it addresses their specific pain points, not just list features.
  2. Talk About Value, Not Just Price: Instead of saying "It costs $29," I aimed to connect the features to the benefits. "This feature can save you X hours per week, which translates to Y value for your business."
  3. Ask for the Sale (or Next Step): If it felt like a good fit, I'd ask if they'd like to try it out or move forward.

A simple flowchart showing the steps of a discovery call: Problem -> Listen -> Solution -> Value -> Ask.

My First Real Conversation

I finally scheduled a call with a fellow solo founder who had expressed interest. I used my "Discovery Call Basics." The first few minutes were still a bit shaky, but by focusing on their problems, I started to relax.

They talked about feeling overwhelmed, juggling too many tasks, and losing track of priorities. It was exactly what I designed TaskFlow to help with.

When it was my turn to talk, I didn't just list features. I said, "It sounds like keeping your task list organized and knowing what to focus on next is a big challenge. TaskFlow has a built-in priority system and a daily focus view that really helps with that, so you don't feel pulled in a million directions."

The Unexpected Lesson: Valuing My Time and Effort

The most surprising part? The user was genuinely interested.

They asked about pricing, and I told them the monthly subscription. I braced myself for a reaction, but they said, "That sounds reasonable for what it does."

It hit me then: my fear was largely internal. I was undervaluing my own work and the problem I was solving. This person saw the value because I had clearly communicated it, by first understanding their needs.

A graphic showing a price tag with a question mark, then transforming into a value proposition with checkmarks.

Takeaways for You

If you’re like me and the thought of selling makes your stomach churn, here’s what I learned:

  • Preparation Reduces Anxiety: Having a simple framework like "Discovery Call Basics" gives you a roadmap. You don't need to be a sales expert, just a good listener and communicator.
  • Focus on the User's Problem: Your primary goal is to understand their pain. When you do that, your solution becomes a natural fit, not a hard sell.
  • Value is About Solving Problems: Frame your product’s benefits in terms of how they solve the user’s specific challenges. Quantify it if you can (e.g., time saved).
  • Your Work Has Value: Don't be afraid to charge for your time and the solution you’ve built. If you’ve solved a real problem, people will pay for it.

My first sales call was awkward, sure, but it was also incredibly liberating. It taught me that selling isn't about being pushy; it's about connecting with people and offering a solution to their problems. And that's something I can definitely get comfortable with.

Previous

How I Stopped Being Busy and Started Building

Next

What I Do When I'm Completely Stuck

Hien Phan
Hien Phan

Full-stack engineer shipping production-grade web systems. Real apps, real stack.

Navigate

  • Work
  • Writing
  • About
  • Contact

Live apps

  • SpeakEn

Reach out

harrisonphan5@gmail.com

Saigon, Vietnam
Product-minded teams. AI-native product work welcome. Remote-friendly. Based in Vietnam (GMT+7).

© 2026 Hien Phan. All rights reserved.

Built with Next.js · TypeScript · SQLite · self-hosted KVM