23
90 Comments

I built a dead-simple CRM for solo salespeople — just launched

[UPDATE — Free 1-month Pro for 20 people]

Got a lot of great feedback from this thread — thank you all. A few people asked if they could try the full version before committing.

So I'm giving away 1 month of Pro free to the first 20 people who want it.

Coupon code: EARLY1 (20 uses only)

How to redeem:

Sign up at closerkit.app
Go to Settings → Upgrade to Pro
On the checkout page, scroll to the bottom and click Add discount code
Enter EARLY1 and apply
No credit card needed. Just try it and let me know what you think — reply here or email me directly.


[UPDATE]
Got incredible feedback from this thread. Already shipped a few changes:

  • Moved to a real domain: closerkit.app (rebranded from Dealpad — "never lose a follow-up" framing several of you suggested felt much sharper)
  • Fixed the mobile experience
  • Follow-up reminders now send at 9 AM in each user's local timezone

https://closerkit.app

Still watching whether users come back to log a second deal — that's the activation metric I'm now tracking based on advice here. This thread has been more useful than a week of solo thinking.
Thank you all.


[ORIGINAL POST]
Hey IH! I just launched Dealpad on Product Hunt today.

I built it because every CRM I tried was built for teams, not individuals. HubSpot, Salesforce — way too much setup for one person who just wants to track their deals.

Dealpad is a lightweight Kanban-style pipeline tracker:

  • Drag & drop deals across stages
  • Follow-up reminders
  • Weighted pipeline value
  • Won/Lost tracking with stats

Free plan (5 deals) + Pro at $9/mo.

Would love honest feedback from the IH community!

https://dealpad-two.vercel.app

posted to Icon for group SAAS
SAAS
on May 31, 2026
  1. 3

    Congrats on the launch!
    I like the focus on solo founders and freelancers - most CRMs feel way too heavy for individual users. Simple, focused products often win. Good luck !

    1. 1

      Thanks! That's exactly the bet — focused beats bloated for this use case. Appreciate the support 🙏

  2. 2

    Hey I'm on the same track that you are on . I hope to see you succeed . My first interaction on this app . Looking forward to learning a lot from you all

    1. 1

      Thanks! Same here — building in public and figuring it out as we go. Good luck with your journey too 🙏

  3. 2

    Awesome updates! Moving to a dedicated domain (closerkit. app) and sharpening the positioning around "never lose a follow-up" is a massive upgrade. It frames the product around a high-intent pain point rather than just being "another lightweight CRM."

    Focusing on the second deal log as your primary activation metric is exactly the right move. For an individual user, a CRM is only as good as the habit it builds. If they come back to log a second deal, it means the friction of your UI is low enough to compete with their notes app or mental checklist.

    Since you are tracking that specific metric now, a couple of things to consider to help drive that second log:

    The "Success" State Trigger: When they move their first deal to "Won" or "Lost," that's the perfect micro-moment to prompt them with a clean, rewarding empty-state button that says "Celebrate and add your next opportunity."

    The Value Loop: Make sure that 9 AM local timezone reminder feels incredibly low-friction to act on. If they can update a deal status directly from an email notification or with a single click, they are much more likely to keep using the app as their single source of truth.

    1. 1

      This is incredibly useful — thank you. The "Success State Trigger" idea is exactly the kind of habit loop I want to build. And you're right about the email notification friction. Being able to update a deal directly from the reminder email is on my list now. Really appreciate the depth here!

  4. 2

    Congratulations on launching!

    Have you tested authorization controls around customer records and sales data?

    I've seen CRM products expose data through IDOR vulnerabilities.

    1. 1

      Good flag — authorization controls are something I've handled at the row level through Supabase RLS, so each user can only access their own records. IDOR is exactly the kind of thing that's easy to miss early. If you've done any testing or have specific vectors worth checking, I'd genuinely appreciate the heads up.

      1. 2

        Glad to hear you’re already enforcing RLS properly — that alone puts you ahead of a surprising number of early-stage SaaS products I’ve reviewed.

        Where I usually still see authorization issues surface is around secondary flows: exports, cached responses, background endpoints, shared resources, or subtle parameter manipulation between authenticated users. The primary queries are often secure, but edge-case logic tends to become the real attack surface as products scale.

        A lot of founders underestimate how quickly small authorization gaps turn into serious security debt once integrations, customer data, and team features start growing. Fixing those issues early is significantly cheaper than cleaning them up after production incidents or compliance pressure.

        The fact you’re thinking about this now is genuinely a strong sign. Most teams wait until something breaks publicly.

        If you continue hardening the platform later, I’d be happy to share additional testing approaches and attack-path checks that are commonly missed during early SaaS development.

        1. 1

          Really appreciate the detailed breakdown — secondary flows are exactly the kind of thing that's easy to overlook when you're moving fast. Exports, cached responses, parameter manipulation between authenticated users — those are on my checklist now.

          Would genuinely take you up on that offer as the product scales. Happy to reach out when I'm ready to do a more thorough review.

  5. 2

    nice, the rename to closerkit and the "never lose a follow-up" framing is way sharper than dealpad tbh. the 9am follow-up reminder is a nice touch, timing is half the battle. is it solo-only or are you thinking team stuff later? i could see a one-person consultant basically living in this.

    1. 1

      Solo-only for now — the whole point is that it's built for one person, not a team. A one-person consultant living in it is exactly the ICP I'm building toward. Team features would pull it in a direction I'm actively trying to avoid. If it ever goes that way it'd be as a separate tier, not a core pivot.

      1. 2

        saw the EARLY1 giveaway in your update, smart way to get people over the trial hump without asking for a card. one thing worth watching during those 30 days is whether folks come back in week two, that told me way more than signup numbers ever did. still curious where you landed on the solo vs small team question btw.

        1. 1

          Week two retention is exactly the metric I'm watching now. Signup numbers feel good but they don't tell you if the product actually clicked.

          Still solo-only. That answer hasn't changed — if anything I'm more convinced after seeing who actually sticks around. The one-person consultant living in it is still exactly who I'm building for.

  6. 2

    Congrats on the launch.

    Getting something live is harder than most people think. I'm working on my first SaaS MVP right now and the launch process has been a great learning experience.

    What was the hardest part of building it?

    1. 1

      Honestly, the hardest part wasn't the code — it was stopping myself from building too much. Every time I'd think 'what if users want X feature?' and have to actively resist adding it. Shipping something intentionally limited feels wrong until you realize that's exactly the point. Good luck with your MVP — the fact that you're launching is already further than most people get.

      1. 1

        Thanks, I think that's one of the hardest lessons for founders.
        The temptation to keep adding features never really goes away. The more I work on my own MVP, the more I realize that launching and getting feedback is usually more valuable than building in isolation.
        Appreciate the advice.

        1. 1

          Exactly — shipping beats perfecting every time. Good luck with your MVP, hope the launch goes well!

          1. 2

            Thank you! I completely agree that shipping beats perfection. I'm trying to validate demand as early as possible before investing too much time into new features. Wishing you success with your projects as well.

  7. 2

    I shipped a tiny B2B tool into the same solo-founder crowd, and the thing that helped activation wasn't more features, it was making the trust layer dead obvious on day one. Since you're tracking whether people come back to log a second deal, I'd also make the first reminder email point to a clean privacy and billing page, folks usually patch that with Termly or TermsFeed, I built PrivacyForge because that stuff drifts once Stripe and analytics get added. Boring tweak, but it makes a $9 tool feel safer fast, imo.

    1. 1

      Good timing on this — the first reminder email pointing to a clean privacy and billing page is something I haven't done yet. You're right that a $9 tool needs to feel safe before someone puts real deal data in. Adding that to the list.

  8. 2

    One acquisition angle worth testing: search for Reddit threads where solo salespeople complain about missing follow-ups, then answer the thread — don't pitch the product. I've done this on browser-tool niches and the conversion from "genuine answer in a complaint thread" beats any launch post by a wide margin. Solo sales reps tend to cluster in niche subreddits by industry (real estate, recruiting, insurance) more than in r/sales. Those are the threads worth finding.

    1. 1

      This is the most actionable acquisition tip I've gotten. Launch posts get ignored, but a genuine answer in a complaint thread gets read. The niche subreddit angle makes sense too — r/realestate, r/recruiting are probably where the actual pain lives, not r/sales. Going to start hunting those threads. Thanks.

  9. 2

    Simple is the right instinct, but it is also the trap. Simple CRM is a crowded graveyard, and most solo salespeople already have a CRM they ignore: a notebook, a spreadsheet, their inbox. The reason they ignore it is data entry, so the bar to make them switch is brutal. Your other post nailed the real wedge though: losing deals because you forgot to follow up. That is not a storage problem, it is a discipline problem, and discipline is what people actually pay to fix. I would build and market around the follow-up engine, the nudge that says you told this person you would call Tuesday and it is Tuesday, and let the CRM part be the quiet thing underneath. One hard question: solo salespeople are famously cheap and churny. Have you checked whether the buyer with real money is actually the 2 to 5 person sales team, not the true solo?

    1. 1

      The 'discipline problem not a storage problem' framing is the clearest articulation of what this needs to be. The CRM part should be invisible — the nudge is the product. On the buyer question: honestly haven't validated it yet. Solo salespeople might be too cheap and churny, and the 2-5 person team might be where the actual willingness to pay is. That's worth testing. The problem is the same either way — the team just has slightly more budget and slightly more deals to lose track of.

  10. 2

    Congrats on the launch. How are you planning to acquire your first 100 users? Are you focusing on organic outreach, partnerships, or paid channels?

    1. 1

      Purely organic for now — no budget for paid. The plan is to keep showing up in communities like this one, find the people who already feel the pain, and get them to try it for free. First 100 users through conversations, not ads. If the product is actually solving the problem, word of mouth should start doing some of the work eventually.

  11. 2

    Are you luanch your app but you app is not secure becuase ai is not perfect dm for my service build secure with me

    1. 1

      Thanks, but we're good on security for now.

  12. 2

    Love the focus on solo salespeople specifically. Most CRMs are overbuilt for what a single operator actually needs. The pricing model makes sense. What's been the biggest blocker so far in getting early users to actually stick with it past the first deal?

    1. 1

      Honest answer: still too early to know for sure — the user base is small enough that I don't have statistically meaningful data yet. But my hypothesis is that the blocker isn't the first deal, it's the second week. People add deals when they're motivated right after signing up, then forget to come back. That's why follow-up reminders are the feature I'm betting on most — if the app surfaces 'hey, you haven't touched this deal in 5 days,' it creates a reason to return. Will know more once I have a few more weeks of data.

  13. 2

    I had the same "keep it lighter than the spreadsheet" problem on a small ops tool, and the surprise was how fast trust questions show up once customer notes or call logs enter the app. The simple setup helps, but I'd also make the boring trust layer stupid clear on day one, people patch that with TermsFeed first, some with Termly, I built PrivacyForge because those pages drift the second Stripe or analytics changes. sounds minor, but for solo sellers its part of whether they'll put real pipeline data in.

    1. 1

      Really good point — I hadn't thought about trust as an onboarding blocker but it makes sense. If someone's about to put real deal names, contact info, and revenue numbers into an app, they want to know it's safe before they type the first character. Privacy policy and data handling needs to be way more visible than it currently is. Adding that to the list. Thanks for flagging it from experience.

  14. 2

    The too-much-setup problem is real. In enterprise sales teams I've worked in, we'd pay for Salesforce and 80% of reps were still logging deals in a spreadsheet because the CRM update took longer than the actual call.

    If you're targeting solo salespeople, the one thing worth timing is onboarding friction. The moment logging a deal feels like homework, they stop doing it and the tool becomes useless. What's the minimum a user has to fill in to add a deal right now?

    1. 1

      Right now: just a name and which stage it's in. That's it. Everything else — value, contact, notes — is optional. The goal was to make adding a deal faster than writing it in a spreadsheet. Whether that's actually true in practice is something I'm watching closely with early users.

      1. 2

        'Still open on a busy Tuesday' is the frame I've been missing for my own product. I've been looking at installs and trial activations but not that specific behaviour. For Genie 007 my equivalent is whether someone uses it on day 8. Drop-off is usually around day 4-5, novelty fades before the habit locks in. Users who make it past day 7 convert to paid at around 34%. Under 10% for those who don't. So day 7 is basically my activation gate. How long before you could see the second-deal metric clearly with CloserKit?

        1. 1

          The day 7 conversion data is exactly what I needed to hear — 34% vs under 10% is a massive gap, and drop-off at day 4-5 makes sense as the novelty window. For CloserKit the second-deal metric is probably visible within the first week since the use case is daily — if someone adds a deal and comes back to add another within 7 days, that's the signal. Right now I don't have enough users to see the pattern clearly, but that's the number I'm watching. What did you change to push more users past day 7?

          1. 2

            Second deal within 7 days is a clean activation signal. It's usage that comes from the product solving a real problem rather than curiosity. The tricky bit at early stage is the noise. When I had under 30 users I'd get excited about a pattern that turned out to be 3 or 4 people. Once you hit 20-30 users who've added 2+ deals you'll start to see whether day 7 is the right threshold or whether the real signal is earlier. What's your active user count at right now?

            1. 1

              Still early — not enough users yet to separate signal from noise, which is exactly the problem you described. Under 30 makes every pattern look meaningful when it's really just 3 people.

              Active user count is small enough that I'm still in "find the right person" mode rather than "read the retention data" mode. Focusing on getting to that 20–30 threshold before I trust any pattern I see.

              The noise problem at early stage is underrated. Good to know day 7 becomes clearer once you have the volume.

  15. 2

    The advice to broaden this into a full sales operating layer is worth resisting. Every bloated CRM started as someone's bigger vision. Solo salespeople do not churn out of simple tools, they churn out of tools that make them do data entry they have no time for. Simple is not a weakness here, it is the whole reason someone picks you over HubSpot.

    I sold for years before I ran companies, and the CRM only ever worked when updating it took less effort than not updating it. The number that matters early is not features, it is whether your users still have it open on a busy Tuesday. Nail that one behavior first. What does activation look like for you, the percent of signups who log a second deal?

    1. 1

      This is the counter I needed to the 'add more features' comments. The CRM graveyard is full of tools that started simple and slowly became what they were replacing. 'Still open on a busy Tuesday' is exactly the right metric — I hadn't framed it that way but that's what I'm actually optimizing for. Second deal logged is a good activation proxy. Honest answer: I don't have that data yet, but I'm going to start tracking it now.

  16. 2

    Fellow solo operator here — the "CRM built for teams" frustration is so real. I've been juggling everything myself too. The positioning clicks immediately. Curious about the upgrade nudge once the 5-deal limit hits — does it feel natural or forced in testing?

    1. 1

      Honest answer — haven't had enough users hit the limit yet to know. The nudge exists but I haven't seen real data on whether it feels natural or forced. If you hit it, I'd genuinely love to hear how it felt.

  17. 2

    I’ve been in a similar spot where I built something lightweight to solve a specific pain point I had, and it’s always a challenge to position it in a way that resonates with the right audience. I think the feedback about focusing on the job-to-be-done rather than “simpler CRM” is spot on. The “never lose a follow-up” angle feels much more tangible and actionable for solo salespeople.

    One thing I’ve found helpful when testing messaging is to actually talk to your first users and ask them to describe the product in their own words. Often, they’ll surface the most compelling language for your positioning. Also, I’d focus on finding a niche within solo salespeople—like real estate agents, freelancers, or consultants—and tailor your outreach to their specific workflows. A broad audience can be hard to target early.

    Curious, how are you planning to get your first few paying users? Are you focusing on Product Hunt traffic, or do you have other channels in mind?

    1. 1

      The 'ask users to describe it in their own words' tip is gold — I'm going to do exactly that with the first few signups. Their language will probably be better than anything I write on a landing page.
      On niche: freelancers and consultants feel like the right starting wedge. They do their own outreach, track their own deals, and have no IT team to set up a CRM for them.
      For first paying users — honestly it's been Product Hunt and IndieHackers so far. No paid channels yet. The bet is that early adopters from these communities will give enough feedback to sharpen the positioning before I try to scale anything.

      1. 2

        That sounds like a solid plan! Focusing on freelancers and consultants makes a lot of sense given their unique pain points with CRMs. Early feedback from Product Hunt and Indie Hackers should be super valuable—are you planning to iterate quickly based on their input or wait until you have a larger pool of users?

        1. 1

          Iterating now, not waiting. Already shipped 3 changes based on this thread alone — domain, mobile fix, timezone-aware reminders. The bet is that 6 users giving real feedback is more valuable than 60 users giving none. If someone tells me something feels broken, I'd rather fix it this week than in 3 months.

  18. 2

    Two structural problems worth flagging.

    "Simpler than HubSpot/Salesforce" has been the pitch from ~50 startups — Streak, Pipedrive, Folk, Attio, Less Annoying CRM, Bigin, OnePageCRM, Salesflare. Most died or stayed tiny. HubSpot's free tier already beats most "simpler CRM" offerings on functionality.

    "Solo salesperson" isn't a buyer persona — it's a workflow. Real estate agents use Follow Up Boss, insurance agents use industry CRMs, freelancers use spreadsheets, founders doing sales use HubSpot free or Notion. They identify by industry, not "solo salesperson."

    $9/mo vs HubSpot free requires a sharp wedge. "Simpler" isn't it.

    Missing features that limit CRM credibility: email integration (solo sellers work from email), contact enrichment, activity logging, mobile app. Without these, "CRM" is generous — it's a Trello board with deal probability multiplied.

    The Vercel URL on a paid product is also a credibility hit. Register a real domain.

    1. 1

      Fair and sharp feedback across the board. The 'simpler' positioning point is valid — I've seen the graveyard of lightweight CRMs too. The job-to-be-done framing makes more sense than the comparison angle.
      On persona: noted. 'Solo salesperson' might be too broad — freelancers, founders, and SDRs all have different workflows.
      Domain is on the list. Vercel URL was a launch-day shortcut.
      The harder question you're raising — email integration, contact enrichment — is whether this stays a focused pipeline tracker or tries to become a full workflow tool. Still figuring that out.

      1. 2

        The shipping speed here is genuinely rare — most founders take feedback as "things to think about." Rebranding to ClosrKit, registering the domain, adding timezone-aware reminders, picking the right activation metric, all in days. That's the part that actually matters.

        On your harder question (focused tracker vs full workflow tool) — pressure-tested this through HiveMind (myosin.xyz/hivemind, code HivemindIH123), the AI strategy copilot we built for exactly this kind of "which direction do I bet on" call. Sharing the analysis since the framework might help:

        The framing has a hidden trap. Most "stay focused" products die because focus doesn't justify $9/mo. Most "expand to workflow tool" products die competing with HubSpot. The real question isn't focus vs expand. It's: what's the wedge that makes ONE specific user category pay $9/mo despite HubSpot free existing.

        The wedge for $9 CRM in 2026 is vertical specificity, not feature breadth. You don't need email integration to compete with HubSpot. You need ONE niche where ClosrKit plus deep workflow knowledge beats HubSpot's generic free. "CRM for real estate agents in [market]." "CRM for freelance creatives tracking client deals." "CRM for consultants doing project-based revenue." Vertical specificity makes feature gaps matter less because the workflow IS the product.

        "Never lose a follow-up" is sharper framing than what you had, but it's still a feature, not a user. Who specifically loses follow-ups in a way painful enough to pay $9/mo? Industry-specific answer wins.

        Best concrete move: interview the users who logged 2+ deals. The pattern in those users is your ICP. You're already tracking the right signal — now talk to the people generating it.

        1. 1

          The vertical specificity point reframes everything. Competing with HubSpot on features is a losing game — but 'CRM for freelance consultants tracking client deals' is a different product entirely, even if the code is identical. The 2+ deal users interview idea is the move I'm doing this week. That's where the real ICP signal is. Thanks for the HiveMind framing — genuinely useful.

  19. 2

    I would recommend to a third pricing tier with some rich features, i believe you might already have some feedback from existing users.... so maybe you can integrate it and add 3rd pricing tier which will make your 2nd tier affordable. Just a thought

    1. 1

      Good point on the anchoring effect — a higher tier does make the middle tier feel more reasonable. Right now I'm keeping it simple while I figure out what power users actually need, but a third tier is definitely on the radar once there's enough signal on which features are worth building out. Thanks for the thought!

  20. 2

    The “built for teams, not individuals” point is a real wedge. A lot of CRMs feel like they assume a manager is watching a pipeline, not one person just trying to remember who to follow up with.

    I’d be curious which feature people actually use first: drag/drop pipeline, reminders, or notes/history. My guess is reminders if the target is solo salespeople.

    1. 1

      That's exactly the hypothesis I'm building around — reminders first. Most solo salespeople don't lose deals because they forgot to track them, they lose them because they forgot to follow up. The pipeline view is the overview, but reminders are what actually keep deals alive. Will be watching which feature gets used first once more people are active — good data to have early.

  21. 2

    I'm Trevor, I help micro-SaaS and App founders grow MRR through BD, sales, partnerships, and distribution. Basically the growth side so you can stay focused on the product.

    I am open working with you

    1. 1

      Thanks! Still early stage, focusing on product for now.

  22. 2

    Nice clean home page. Simple wins.

    1. 1

      Thanks! Kept it as simple as the product itself 🙏

  23. 2

    Clean execution. I like the “solo-first CRM” positioning.

    One thing I’ve noticed with these tools is the real challenge isn’t tracking deals, it’s maintaining consistency in follow-ups over time without the user actively managing the system every day.

    Curious how you’re thinking about preventing it from becoming just another “manual update app” after the initial excitement wears off?

    1. 1

      This is the core retention challenge honestly. My bet is on follow-up reminders — if the app pings you when a deal goes cold, you come back. But you're right, I'll be watching drop-off closely after the first week.

  24. 2

    The "dead-simple" positioning is hard to stick to once users start requesting features. What's your rule for deciding what NOT to build? Curious how you're drawing the line.

    1. 1

      Simple rule: if a solo salesperson wouldn't need it on day one, it doesn't ship. Team features, reporting dashboards, custom fields — all cut. The moment it feels like HubSpot, I've failed.

      1. 2

        This is the right religion. I build for SMBs too and every extra feature is a tax on the one person who just wanted the thing to work. "The moment it feels like HubSpot, I've failed" — stealing that as a north star. How do you hold the line when a user begs for a feature?

        1. 1

          Honestly, the filter is: would removing this feature make someone cancel? If yes, consider it. If no, it's a nice-to-have and it waits. The harder part is when 5 different users ask for 5 different things — each one feels urgent but they'd each pull the product in a different direction. So far the answer has been 'log it, watch if it comes up again, don't ship it yet.

          1. 2

            That cancel-test is a clean heuristic. The "5 users, 5 directions" problem is real — I've started weighting requests by whether they come from people who use the core feature daily vs one-off askers. A power user's request usually points at the real gap. Do you track who's asking, or just what?

            1. 1

              Honestly, just what right now — not who. But your point about power users is the right filter. A request from someone who opens the app every day means something different than a request from someone who signed up and never came back. Going to start tagging feature requests by user activity level. Simple but probably changes which ones actually get built.

              1. 2

                Honestly, just what right now — not who. But your point about power users is the right filter... Going to start tagging feature requests by user activity level. Simple but probably changes which ones actually get built.

  25. 2

    Solo salespeople are honestly the most underserved segment in the CRM space — most tools are built for teams with way more features than one person needs. Love the focused approach here.

    1. 1

      Exactly why I built it. Every CRM I tried assumed I had a manager to report to 😅

  26. 2

    Congrats on the launch, Dealpad! 🚀 The UI looks incredibly clean, and the problem you're solving for solo salespeople is very real.Quick technical feedback: Since it’s hosted on Vercel, make sure your mobile-first rendering and Core Web Vitals are fully optimized to capture organic traffic on Google later on. Tech tools often suffer from heavy JS payload on mobile.Rooting for you on Product Hunt! 📈

    1. 1

      Really appreciate this — hadn't prioritized mobile performance yet but this is a good reminder. Will run a Lighthouse audit this week. Thanks for rooting for us 🙏

  27. 2

    This is a clean wedge. Most CRMs add structure for managers, reporting, teams, permissions, and forecasting, but a solo salesperson mainly needs one thing: know what deals are active, what needs follow-up, and what is likely to close.

    The Kanban angle makes sense because it keeps the product close to the way a solo seller actually thinks.

    The part I would pressure-test early is the brand frame. Dealpad is clear, but it also sounds very close to a lightweight deal board. If the product stays as a simple pipeline tracker, that works. But if you expand into reminders, stats, follow-up logic, prospecting, notes, or AI-assisted sales workflow, the name may start feeling smaller than the product.

    Before more Product Hunt traffic, users, and search memory lock in, I’d think about whether the brand should carry the broader solo-sales workspace direction.

    Xevoa .com would fit that direction well because it feels more like a modern sales workflow platform than just a place to store deals.

    1. 1

      Really thoughtful feedback on the brand. 'Dealpad' works for now but you're right that if it expands beyond deal tracking the name might feel limiting. Something to keep in mind as the product evolves.

      1. 2

        That is the exact point I’d watch.

        Dealpad is fine while the product is only “a simple board for deals.” The risk starts when users begin remembering it that way while you are quietly building something broader.

        For a solo salesperson, the bigger category is not really “deal tracking.” It is the daily sales operating layer: active deals, follow-ups, reminders, notes, close likelihood, and eventually workflow intelligence around what to do next.

        That is a much stronger product direction than a lightweight CRM board.

        So the timing matters. Product Hunt traffic, first users, onboarding copy, screenshots, and early testimonials all start teaching the market what Dealpad is. If they learn “simple deal board,” it becomes harder later to move the product into a broader sales workspace frame.

        That is why Xevoa.com stood out to me. It feels more like a modern workflow platform that can carry the broader solo-sales direction, while Dealpad keeps pulling the product back toward “place where deals sit.”

        I would not treat this as abstract branding. I’d pressure-test it before too much early product memory gets built around the smaller frame.

        1. 1

          This is the tension I'm sitting with right now. You're right that early product memory is hard to undo — if the first 500 users learn 'simple deal board,' repositioning later is an uphill battle. The 'daily sales operating layer' framing is interesting and probably closer to where this goes if it grows. Not ready to commit to a broader brand direction yet, but this is exactly the kind of pressure-test worth doing early. Appreciate you pushing on it.

          1. 2

            That is the right way to think about it.

            I would not rush a rename just because the product might expand. But I also would not treat the name as something to revisit only after traction, because traction is exactly what makes the current frame harder to undo.

            The clean test is probably this:

            If the product is mostly a simple Kanban board for deals, Dealpad is clear and useful.

            If the product is becoming the daily operating layer for solo salespeople, then the name needs to carry more than “where deals sit.” It has to support follow-up logic, reminders, close likelihood, notes, workflow, and the feeling that this is the seller’s command center.

            That is where Xevoa.com felt stronger to me. It gives the product room to feel like a real sales workflow platform instead of a lightweight deal board.

            I’d pressure-test both names against the product you want users to remember 12 months from now, not just the version they see today.

            1. 1

              Actually just moved to closerkit.app — which already signals a broader direction than just deal tracking. The test you're describing is exactly right though: what do I want users to remember this as in 12 months? Still figuring that out, but the name shift was a step toward something that feels less like 'a board where deals sit.' Appreciate you pushing on this consistently.

              1. 2

                That move makes sense. CloserKit already points more toward outcome and sales workflow than Dealpad did.

                The next thing I’d pressure-test is whether “CloserKit” still feels like a toolkit, or whether the product wants to become the actual daily sales operating layer for solo sellers.

                That difference matters because it changes the homepage, onboarding, feature naming, and who you attract first.

                If you want, I can pressure-test this properly in a short written breakdown: CloserKit’s current frame, stronger 12-month positioning, first user segment, and how to make the product feel bigger than a simple sales board without overbranding it too early.

                1. 1

                  Yes, I'd genuinely appreciate that. The toolkit vs. daily operating layer question is exactly what I'm wrestling with — and you're right that it changes everything downstream. Would love to see the breakdown.

                  1. 1

                    Absolutely. This is worth doing properly because the toolkit vs. daily operating layer choice will shape the homepage, onboarding, and first-user targeting.

                    What’s the best email to send it to?

  28. 1

    Just dropped a free 1-month Pro coupon for the first 20 people — code is EARLY1 at checkout. Details in the post above ↑

  29. 1

    Finding leads is the other half of this puzzle. We built Rixly to catch buying signals in real-time — then your CRM closes them.

  30. 1

    Congratulations on your launch , I run MVP ads that brings leads . I will run your first one free tonight -Dm

  31. 1

    Quick update based on the feedback here —

    ● Moved to a real domain: closerkit.app (rebranded from Dealpad — the "never lose a follow-up" framing several of you suggested felt much sharper)
    ● Fixed the mobile experience
    ● Follow-up reminders now send at 9 AM in each user's local timezone

    Still watching whether users come back to log a second deal — that's the activation metric I'm now tracking per the advice in this thread.

    Still iterating, so if anything feels off as you poke around, I'd genuinely love to hear it. This thread has already been more useful than a week of solo thinking.

Trending on Indie Hackers
I sent 43 cold emails with my own tool. 17 replied. 1 paid. Here’s the unofficial launch. User Avatar 173 comments I built for one user. Myself. User Avatar 72 comments I came up with a great idea for a solo Vibe Coding project, and I'm testing it out right now User Avatar 23 comments I built a web-based vector editor from scratch and integrated an AI Agent. Need just ONE beta tester! User Avatar 22 comments AI prices dropped 97% since 2023. So why are AI bills 3x higher? User Avatar 19 comments Why Your Users are Leaving in Silence (and How to Fix the "Leaky Bucket" with AI) User Avatar 17 comments