Refusing to Share Custom Software Tool with Coworker: AITA for Seeking Compensation?

A tech startup problem turned into a full-blown office power struggle when a 28-year-old guy built a custom software tool that saved the team hours, then refused to hand it over to a coworker who demanded access.

He’d designed it during his free time, kept it quiet because he considered it his personal project, and when Sarah found out, she pushed for full access with no discussion and no terms. After he said no, the team leader stepped in and pressured him to share it with everyone, arguing that since he built it while employed, it automatically belonged to the company.

Now he’s stuck between teamwork and the feeling that Sarah’s “just give me everything” attitude is getting rewarded instead of his effort.

Original Post

So I'm (28M) working at a tech startup, and I've always been the go-to person for solving complex problems efficiently. About six months ago, I designed a custom software tool during my free time to streamline our project management process.

This tool has significantly improved our team's productivity and saved us hours of work. However, I never mentioned it to my coworkers as I saw it as my personal project.

Recently, one of my coworkers, let's call her Sarah, found out about the tool and demanded that I grant her full access without discussing any terms.

I politely declined, explaining that I put a lot of time and effort into developing it, and I believe I should be compensated or at least acknowledged for my work. Sarah didn't take my refusal well and complained to our team leader, who then pressured me to share the tool with everyone without any compensation.

I feel conflicted because I value teamwork but also think it's unfair for Sarah to demand access without considering my efforts. The team leader believes that since I developed it during my employment, it automatically belongs to the company without any additional reward for me.

I'm torn between supporting the team and standing up for what I believe is fair. So, AITA?

This lack of structure can lead to misunderstandings, as seen in the Reddit thread.

Comment from u/CoffeeAddict89

Comment from u/coding_dragon_42

Comment from u/TechieGirl23

Comment from u/PizzaLover99

Comment from u/GadgetGeek9000

Sarah went from discovering the tool to demanding full access, and that’s where the vibe instantly soured.

It’s a bit like the teen who refused Vietnamese dinner after her dad insisted.

The guy’s refusal came with a clear reason, he put in his own time, so he wanted compensation or at least recognition.

When the team leader pressured him to share it “without any additional reward,” the debate shifted from fairness to policy.

What would you do in this situation? Share your opinion in the comments.

With the team caught in the middle, his question is basically whether he should cave just to keep the peace with Sarah and the leader.

The recent Reddit thread about a software developer's refusal to share a custom tool with a coworker underscores the critical issue of ownership and recognition in the tech startup landscape. As startups thrive on collaboration, the tension between sharing and entitlement can create significant workplace challenges.

Moreover, the situation highlights the necessity for transparent communication to mitigate conflicts over individual contributions. Without established guidelines, employees may feel undervalued or taken advantage of, potentially stifling creativity and productivity. By fostering an environment that prioritizes dialogue and respect for personal contributions, startups can not only enhance employee morale but also drive innovation and collaboration.

The situation presented in the Reddit thread underscores a significant tension between individual contributions and the collaborative spirit that is often touted in tech startups. The developer's hesitation to share his custom software tool without financial compensation illustrates a deeper psychological need for recognition and fairness, a factor that is frequently neglected in high-pressure environments. This reluctance is not merely about the tool itself but reflects a broader concern that many employees share: the fear of having their efforts go unrecognized. The conflict with Sarah emerges not just from a disagreement over a software tool but from a fundamental breakdown in communication about expectations and value. Promoting open dialogue can be a crucial step in addressing these underlying issues, helping to cultivate a workplace culture where contributions are valued and recognized, thus reducing the likelihood of resentment and conflict.

Nobody wants to build a time-saving tool, then get treated like it was free labor just because they had a job.

For another “family says yes, you say no” standoff, see the woman pressured to invest in her sister’s failing bakery.