33
16 Comments

5 things to consider before starting your own SaaS

Before we started with SaaS, I had success helping lots of early-stage startups navigate pre-PMF territory from our LinkedIn agency times (we ran a LinkedIn outbound agency doing nothing but cold outreach for paying clients). We thought that there must be a way to find high-intent LinkedIn leads more efficiently, with less work required. So we focused on pursuing that idea, which led us to building our product

Throughout my journey, I’ve learned a few things that I think anyone who plans to start their own SaaS should know. 

1. Businesses only buy for a handful of reasons

Bit of an obvious thing, but this is something I actually struggled with at first. During my agency times, I actually tried to launch a startup where I built a daily reporting tool on an email basis, all because I liked the idea. In the end, nobody was interested or willing to pay for it. 

So before you start grinding and writing code, validate your idea first. What do you know about your ICP? Are they already paying for your type of solution? Does your product help generate revenue for them?

Ideally, your product should do at least one of these:

  • Make or save them money.

  • Fit easily into their existing workflow.

  • Give them better visibility through data.

Creating more revenue should be the number 1 reason why people buy your product. Businesses are much happier spending money to grow revenue than to reduce expenses. If your value proposition doesn’t offer this, maybe you should rethink your idea.

2. Don't build for an industry you barely understand

Domain expertise is a competitive advantage. My experience at the LinkedIn agency really helped me identify what my clients want and how I can best provide solutions. The tool was originally just a solution to my own problem, which worked so well that I decided to launch it.

So before you build, make sure you have a thorough understanding about how the industry works. What the biggest pain points are. How buyers make decisions. Which workflows are broken. If you don't have that experience, either start attending webinars or get a co-founder who does.

3. Competitor research is free real estate

How well your competitors are doing proves there’s demand. There’s so much you can learn from them, such as:

  • Who they're selling to

  • Their marketing strategy

  • Common complaints

  • What features the ICP is looking for

List at least 3-4 main competitors for your product and go over their landing page, API, what workflow integrations they have, package inclusions, pricing, and so on. Then think if you can offer the same features or add more value to them.

4. Build around existing workflows

Businesses rarely want another standalone tool. They want something that fits into the tools they're already using. Before you build anything, you should have a deep understanding of these things:

  • How your ICP works today.

  • Which tools they already use.

  • Where friction exists.

  • Which manual steps waste time.

Businesses invest in solutions that help them make money, but if it requires them to create a new workflow just to accommodate your product, they might as well just settle with something else. Make it easy for them to add your tool to their existing workflow. 

5. Find customers already looking for change

One of the biggest mistakes B2B founders make is trying to sell to everyone. Their product then becomes too broad, their messaging becomes generic, and nobody feels like it's built specifically for them. Instead, look for customers who are already trying to improve their workflow. They are much easier to convert into paying customers. 

We built our tool to improve the process of getting warm leads on LinkedIn for our agency clients. The good thing is we can also use the same tool to help us find leads for our startup company as well. We searched our competitors, influencers in the industry, and found people who are already discussing the issues we can solve. 

Customers with intent will also help you learn more about your product. They’re much more involved, and trust me, they will be very honest about where you’re lacking. 

One thing we did with our startup was doing 1-1 calls with our customers to hear their problems and ideas. They’ve given us good feedback about how good our tool is solving their problem, and in what ways we can improve their experience. 


__

PS: If you need high-intent leads interested in what you have to offer, have a look at IbexAI.

posted toAvatar for product IbexAI
IbexAI
  1. 2

    Making money for the customer is the fastest way to get them to open their wallets. If you aren't fixing a broken workflow that costs them time or revenue, you don't have a business.

  2. 1

    The forcing event point in the comments is underrated. Cost savings as a general pitch sits in the "nice to have" category until there's a renewal, an audit, or a deadline making the status quo suddenly painful. Timing the pitch to a forcing event changes the conversion math completely.

    Designing around existing workflows instead of asking people to adopt new ones is the insight most first-time SaaS founders learn the hard way. The product that fits into what someone already does will always beat the better product that requires them to change how they work.

  3. 1

    Point 1 needs one nuance from 20 years selling in the Microsoft channel: cost-side products sell fine when there is a forcing event attached, a renewal, an audit, an outage, a migration deadline. Revenue growth wins the wallet in calm times, but urgency wins it every time. I'd add a sixth: find the event that forces your buyer to act this quarter, then position against it.

  4. 1

    Great insights, especially the point about building around existing workflows. I think a lot of founders underestimate how much friction a "small behavior change" can create for users. Also agree that talking to customers early and often is one of the biggest competitive advantages an early-stage SaaS can have.

  5. 1

    Great breakdown, especially the point about building around existing workflows. Looking back, was there one feature you initially thought would be essential but your early customers barely used?

  6. 1

    Love the transparency here, especially around your first startup attempt with the email reporting tool. It’s the classic trap: building a 'vitamin' (nice to have) versus a 'painkiller' (must have).

    Coming from a cold outreach agency background is your absolute unfair advantage here. You didn't read about the ICP's pain points in a report; you lived them every day trying to secure paying clients. Building a tool to scratch your own operational itch ensures you're automatically hitting Point #1 (making or saving money) and Point #5 (targeting high-intent buyers). This is gold for anyone trying to transition from agency work to software product.

  7. 1

    Great advice. I especially agree with validating the idea before building. It can save months of work.

  8. 1

    I am a web app developer. I build 25apps and each app solve daily life problems I cover many life aspects business tools beauty woman wellness tracker health education managent series hotel hospital pharmacy school lab now need help to grow I build from scratch

    1. 1

      Here's a thoughtful reply you can post:

      That's an impressive foundation. Building 25 apps from scratch already proves you have the technical skills. Now the challenge isn't development—it's distribution. Instead of promoting all 25 apps at once, pick 1–2 with the strongest market demand, share the problems they solve through case studies and short demo videos, collect user testimonials, and build in public. Consistent content and a clear niche will help you gain far more traction than trying to market everything simultaneously. Wishing you success! 🚀

  9. 1

    Quality plays an important role

  10. 1

    This resonates. Building PM OS (SOW → project plan generator with GPT-4o),

    the biggest surprise was that the "obvious" MVP scope wasn't obvious until

    I watched someone actually try to use it. I built full task-hierarchy

    generation first, when people initially just wanted a 30-second skimmable

    summary. What was your biggest pre-launch assumption that turned out wrong?

  11. 1

    Your own story - agency to product - is the most robust way of doing most of this!

  12. 1

    Nice breakdown Matt — this is one of those posts that gives people a real framework instead of just hype.

    A simple way to see it is that SaaS fails when the product is built before the pain is clearly understood.
    The strongest point here is that people buy into workflows they already trust, not brand-new habits they have to learn from scratch.
    Have you thought about how much easier the sell becomes when the product fits into an existing motion?

  13. 1

    The points about domain expertise and building around existing workflows especially hit home – I’ve seen a lot of products fail because founders don’t really understand the day-to-day reality of their ICP. Curious: when you were validating IbexAI, what was the most useful signal that told you “okay, this is worth going all in on”?

    1. 2

      Paying customers and retention