1
4 Comments

Why I stopped treating this as a one-time event

I’ve been working solo on a product called PitchArti, and it’s forced me to rethink how pitching actually works for founders.

Most of us treat pitching as something we do only when we have to. Investor meeting, demo day, sales call. We prepare, pitch, and then move on, usually without clear feedback on what was actually unclear.

While building PitchArti, I started testing a different assumption: pitching improves the same way any other skill does, through regular practice and feedback.

What I’m seeing so far is interesting. When founders pitch more often and get specific feedback on clarity, improvement becomes much more predictable. The pressure drops, weak parts show up faster, and the story gets sharper over time.

I’m still early and learning as I go, but this shift from “one perfect pitch” to “practice and iterate” feels important, especially for solo founders who don’t get many reps.

Curious how others here approach pitching. Do you practice it regularly, or mostly when it really counts?

on December 31, 2025
  1. 1

    I love this perspective! Pitching is often seen as a one-off performance, but treating it like a skill to be honed makes sense. Repetition helps you internalize your story and get comfortable addressing objections. I try to weave a version of my pitch into casual conversations and gather feedback from friends and other founders. Do you have any frameworks for capturing feedback or running mini 'practice sessions'? Also curious how you measure improvement over time.

    1. 1

      Really appreciate your detailed reply. That approach of weaving your pitch into everyday conversations sounds like a great way to get informal feedback and reduce pressure. We hear variations of that same theme from founders again and again.

      What we’ve learned from building PitchArti is that the structure around feedback matters a lot. Casual talk and friendly reactions are valuable, but they don’t always pinpoint the specific parts of a pitch that are unclear or confusing. That’s why PitchArti’s weekly rounds focus on giving founders clear, actionable feedback on exactly what parts of the pitch need more explanation or clarity backed by scoring and repeatable performance indicators. Over time, those patterns show up and help you refine your story in a way that simple reassurance often doesn’t.

      Measuring improvement in PitchArti isn’t just about whether people like a pitch — it’s about tracking clarity signals over multiple attempts and seeing whether the same issues continue to show up or start to disappear. When the feedback changes, that’s when you know you’ve actually improved.

      If you ever want to see how we’ve mapped that structured feedback into something you can try with your own practice sessions, I’m happy to share how it works or walk through an example. Just let me know.

      1. 1

        Thanks for expanding on this, it's really helpful. The idea of tracking clarity signals across multiple attempts resonates — it's easy to mistake polite nods for understanding. I'm curious: when you analyse a founder's pitch over time, do you look at objective metrics (e.g., filler words, length, structure) or more qualitative patterns in feedback? Any tips for someone trying to run their own practice sessions without dedicated tooling?

        1. 1

          That’s a really good distinction, and you’re right, polite nods are one of the biggest false positives in pitching. We tend to look at both objective and qualitative signals, but they serve different purposes. Simple objective cues like how quickly someone can accurately repeat the problem back to you, whether the pitch stays structurally consistent across attempts, and whether it becomes more concise over time without losing meaning are often early indicators that clarity is improving. Things like filler words usually resolve themselves once the story tightens.

          Where most of the real progress shows up is in qualitative patterns. Repeated questions about the same part of the pitch usually signal the true bottleneck, while a shift in objections from “I don’t understand” to “I get it, but it’s not for me” is actually a positive sign. Another useful signal is whether feedback changes at all between attempts, if it doesn’t, it often means the underlying issue hasn’t been addressed yet.

          If you’re running practice sessions without dedicated tooling, keeping it lightweight works best. Ask the same two or three questions after every pitch, write feedback down verbatim instead of summarizing it, and change only one element of the pitch between sessions so you can isolate what actually helped. That manual process is essentially what we later systematized in PitchArti the structure just makes those patterns easier to spot over time.