13
18 Comments

Launching TaskJect — a project & task manager for small dev teams

Hey Indie Hackers 👋

I just launched TaskJect — a lightweight project and task management tool designed specifically for small technical teams like ours.

⚒️ Why I built it:

My team of 5 developers needed a task manager that was:

  • Fast (without React overhead)

  • Focused on essentials

  • Easy to use and self-host if needed

  • Not bloated like Jira, ClickUp, or Asana

Most tools we tried were overloaded with features, had a steep learning curve, or felt like they were built for enterprise PMs — not developers. So we built what we needed.

🚀 What TaskJect does:

  • Project and task tracking

  • Per-project permissions and roles

  • Basic team analytics

  • Clean, backend-first UI (ASP.NET Core 6, Razor Pages)

  • Hosted version available — free to try

👀 Who it’s for:

  • Small software/product teams (2–7 people)

  • Backend-first projects that don’t need a heavy UI

  • Founders and devs who just want clarity and control

🔗 Live now:

👉 https://taskject.com

Would love your feedback:

  • What’s missing?

  • Would this work for your workflow?

  • What would make you switch from your current tool?

Appreciate any thoughts, suggestions, or questions 🙌

posted to Icon for TaskJect
TaskJect
  1. 4

    I really like the simplicity of TaskJect, cutting out unnecessary features that often slow down tools like Jira.

    In my current project, I’ve been exploring ways to add task flows for defining, implementing, and verifying analytics events. I actually found a few ideas in your project that gave me inspiration.

    One thing that might be useful is adding support for linking or integrating with other tools like GitHub or Figma. It could make collaboration smoother, instead of just pasting raw links in the task descriptions.

    Wishing you all the best with the launch.

    1. 2

      Thank you so much! Really appreciate you taking the time to explore TaskJect.

      We’re definitely considering GitHub integration — it’s one of the most requested features already.
      As for Figma, we’re open to it, but we’d love to hear from actual users who rely on it in their workflow to better understand how integration would help them (beyond just embedding links).

      If you're open to sharing more about how you use Figma for tasks or collaboration, we’d love to learn from that.

      Thanks again — it’s super motivating to know that TaskJect sparked some inspiration in your project!

      1. 1

        One of the main issues I often face is that links shared in tasks point to the general Figma file or project, without including a specific screen or frame, because they don't link to a concrete node_id. It would even make sense to support linking to multiple node_ids when a feature touches several screens. So when working on a particular feature, I often have to dig through the file to find the right section.

        This is just from a developer's perspective. Maybe product or QA teams have different needs. But having more precise linking or visual previews would definitely save time and reduce confusion during implementation.

        1. 1

          Thanks a lot for the thoughtful feedback!

          We're definitely aiming to evolve TaskJect in a way that brings more value to technical professionals, so your insights — especially from a developer's perspective — are incredibly valuable. I don't work directly in that area myself, which makes your input even more helpful.

          We'll add this idea to our backlog. That said, to implement it well, we'd need to collaborate with someone who really understands the pain point — possibly someone like you — to ensure we’re solving the right problem in the right way.

          Would love to stay in touch if you’re open to that!

          1. 1

            Sounds good! You can find some contact info in my profile.

  2. 2

    Love the video. You did a great job of explaining the product. Do you have plans to do more videos, maybe to focus on specific features? I'm wondering if I should do some videos for my product so I'm curious about how you went about it and whether it has helped convert users?

    1. 1

      Thanks for the kind words and for taking the time to watch the video!

      Yes, we definitely plan to create more videos — most likely in the form of short guides focused on specific features. We’ve noticed that while we aimed for everything in TaskJect to be intuitive, some mechanics still benefit from a quick visual walkthrough.

      In theory, video content can certainly help convert users, but based on our research, YouTube isn’t currently among the top 5 channels where our target audience discovers new tools. So while we’ll keep producing helpful content for existing users, we’re a bit more cautious about using video purely as a growth driver — at least for now.

      Would love to hear how you're thinking about videos for your product too!

      1. 1

        I'm thinking that the initial "here's what this is and how it can help you" video would not only show how the product works but also touch on the benefits. I guess the first video will be introductory and will be a gloss-over of how it works, but the next would be strictly educational, with no concern for conversions. I think video will be important but I'm not sure I'm going to do a stellar job of it. Definitely going to try though!

  3. 2

    Cool. I’m not a dev, but I’ve been building a tool while working , so I get the frustration with bloated platforms.
    This looks clean and focused , love that it’s built for small companies. One thing though: any plans to add simple AI suggestions (like prioritizing tasks or flagging blockers)? Might help non-technical teams too.

    1. 1

      Your suggestion sounds interesting, especially for helping non-technical teams. But we need to clearly define which aspects AI can handle effectively. For example, whether it's prioritizing based on deadlines or identifying blockers through task dependencies. Thanks for the idea, I’ll definitely keep it in mind!

  4. 2

    that really looks good and good UI

    1. 1

      Thank you!

      If TaskJect seems like something your team might benefit from, I’d be happy to set you up with early access. Right now we're keeping registrations private so we can stay closely in touch with early users and adapt the product around real workflows.

      Just drop a comment or DM me — I’d love to get your input and hear how TaskJect could fit into your current process.

  5. 2

    Looks really good. My team is in pretty early stage and we’re currently using trello, this one looks like a better alternative.

    The upgrade I’d consider is adding comments section under tasks to communicate about them. I think that’d really benefit the workflow! Or is it already included and I just didn’t notice?

    Anyways looks super smooth and efficient!

    I sent you a request and would love to give it a shot with my team!

    1. 1

      Awesome to hear you're considering it for your team!

      You're right: at the moment, tasks include a description and a separate notes section for the TeamLead, but there isn’t a comment thread yet. That said, collaborative features like comments are definitely on our radar, and your use case gives it even more weight.

      Also, huge thanks for deciding to join TaskJect - really appreciate the trust! I’ve seen your request and will get you set up shortly. Looking forward to your feedback once your team gets started.

  6. 2

    Looks simple and interesting — I’m surprised to see such low pricing, not to mention a free tier. One thing that caught my eye: why is there no user registration available?

    1. 1

      Great question!

      Right now, registration is closed by design. One of the key features we offer is the ability for each team using TaskJect to submit requests for improvements or custom features. We handle each of these requests manually - because we genuinely want to understand real user needs and build something that matters.

      That said, it also means we’re intentionally limiting access at this early stage due to both human and infrastructure constraints. We want to stay focused, avoid random signups that lead to spam or noise, and make sure we’re supporting teams who are serious about shaping the product.

      We’ll gradually open things up as we scale. Thanks for asking - your interest means a lot!

  7. 2

    This is super helpful. I’m also launching my first free product — curious how you promoted yours?

    1. 1

      Thanks! Congrats on your launch too — that’s a huge step 🚀

      For TaskJect, we started by posting on platforms where early adopters and indie founders hang out:

      • BetaList (still in review)

      • Indie Hackers (this post 🙂)

      • LinkedIn — mostly via personal updates from my profile

      • YouTube — short demo to show how it works in action

      No paid ads so far — we’re testing organic reach first, learning what resonates, and adjusting as we go.

      Would love to hear how you’re approaching your launch too!