AccessLedger
Track and revoke temporary contractor access
I’m trying to validate whether this problem is real enough to justify a product.
In many teams, temporary contractor or vendor access is tracked in spreadsheets or ad-hoc notes. Expiry dates get missed, ownership is unclear, and revocation depends on someone remembering to follow up.
I built a small MVP called AccessLedger to test a simple idea:
every access should have an owner, an expiry date, reminders, and a clear record of when access was revoked.
I’m not selling — I’m validating.
Questions for you:
1) Is this a problem you actually see in your team?
2) How do you track temporary access today?
3) What would need to be true for you to trust a tool like this internally?
If helpful, I can share the product page or a demo link.
3 Comments
Congrats on the launch, looks solid. How are you currently thinking about acquiring early users and gathering feedback?
Sorry for the late reply, I somehow missed this comment earlier.
Right now I’m focusing on problem validation rather than scaling acquisition. I’m trying to talk directly to teams that manage contractor or vendor access and understand how they currently handle it.
So far, I’m gathering feedback through Indie Hackers, founder communities, and direct conversations. The goal isn’t growth yet, it’s making sure the pain is real and clearly defined before building further.
Appreciate the question, how would you approach early validation in a B2B context?
Great question, B2B validation is definitely a different process.
In my experience, early validation in a B2B context relies on a few key factors:
1. Start with Specific Painful Workflows: Focus on recurring, high-friction processes that waste time or money, rather than broad, general problems.
2. Engage Budget Owners, Not Just Users: While end users may experience the pain, validation occurs only when someone with purchasing authority acknowledges that it’s worth solving.
3. Test Willingness to Commit, Not Just Interest: Instead of asking, “Would you use this?”, I look for stronger signals, such as:
- Agreeing to a pilot program
- Introducing me to the procurement team
- Sharing internal documentation
- Pre-committing budget if certain criteria are met
4. Map the Buying Process Early: In B2B, validation should address not only whether the solution is useful, but also whether it can gain approval.
I also prefer to focus on one specific vertical and delve deep into it, rather than spreading validation efforts across too many segments too early.
I'm curious: do you think contractor/vendor access management is painful enough that teams are actively searching for alternatives, or is it more of a “nice-to-improve” workflow at this stage?