1
7 Comments

I Built a SaaS for Freelancers — Now I'm Looking for My First Users

Why I built Propuls, what it does, and what I'm learning about turning a finished product into a real business.

I’ve spent months building SaaS products with AI, no-code and code. Now I’m facing the part that comes after building: finding the right users.

One of the products I’ve built is Propuls, a SaaS designed for freelancers, consultants and small agencies.

The idea is simple: running a service business often means jumping between different tools to manage prospects, offers, proposals, invoices and client workflows.

Propuls brings these workflows together in one place, with AI features designed to help reduce repetitive work.

What Propuls currently helps with:

  • Managing prospects and opportunities

  • Creating offers and proposals

  • Generating invoices

  • Managing client-related workflows

  • Using AI to speed up repetitive tasks

The product is already live.

Now comes the interesting part.

I want to find real users, understand how they use the product, discover what they actually need, and improve Propuls based on real feedback.

I’ll be experimenting with different ways of getting users: communities, content, direct outreach, partnerships and other acquisition channels.

I’ll share what works, what doesn’t, and what I learn along the way.

If you’re a freelancer, consultant or agency owner, I’d also be interested in hearing how you currently manage your prospects, proposals, invoices and client workflow.

Propuls: https://getpropuls.com

posted toAvatar for product Propuls
Propuls
  1. 1
    Freelancers can lose a client simply because they forgot to follow up while busy delivering work for another. I'd show a freelancer finishing a project, then Propuls surfacing an unanswered client message and the next action beside the existing workload. That everyday moment explains one workspace better than a feature tour.
    1. 1
      merci beaucoup pour votre apport je tiendrai compte
  2. 1
    The part about finding the right users resonates. I'm building something for a slightly different part of the agency workflow, and one thing I'm realizing is that agencies often don't have one single “client workflow” — the process changes quite a bit once a project moves from sales → development → client review → revisions → ongoing work. I'm curious: when you're talking to freelancers and small agencies, which part of their client workflow seems to cause the most friction so far?
  3. 1
    Because Propuls spans prospects, proposals, invoices and client workflow, I’d avoid testing channels before testing the entry pain. Pick one moment with a clear cost — for example, a proposal accepted but the handoff to invoicing/client delivery breaks — then find 10 freelancers publicly describing that moment. If they will show the current workaround, you have a discovery cohort; if they only say the all-in-one idea sounds useful, you have interest but not yet a problem worth switching for.
    1. 1
      oui voilà évidemment, c'est le meilleur chemin que vous proposez
  4. 1
    I’d pick one painful workflow instead of marketing the whole suite at once. “Manage proposals, invoices, prospects and clients” is broad. “Stop rebuilding the same proposal from scratch every week” gives you a much easier conversation to start with freelancers. Get traction around one pain first. The rest of the product becomes a nice surprise after they’re inside.
    1. 1
      Merci beaucoup, je vais en tenir compte rigoureusement