AITA for “stealing” 15.000€ of a family?

A freelance software developer recently found themselves in a moral dilemma after accepting a project that would cost a family nearly all of their savings. The job seemed straightforward on paper: build an app according to the client’s specifications and deliver a polished product. However, the situation became uncomfortable when the developer realized the idea behind the app seemed unlikely to succeed.

Despite their doubts, the family remained convinced the project would bring in significant income. While some friends argued the developer should refuse the job to protect the family’s finances, others insisted that clients are responsible for their own business decisions. Unsure where professional responsibility ends and personal ethics begin, the developer shared the situation online to ask whether continuing with the project makes them the one in the wrong.

‘AITA for “stealing” 15.000€ of a family?’

The developer explained their freelance work and how the unusual project began.

The situation became concerning when the developer evaluated the app idea itself.

After discussing the situation with friends, the developer wondered where responsibility truly lies.

Situations like this highlight the complicated ethical landscape freelancers often face. Independent professionals frequently work on projects where they are hired to execute an idea rather than evaluate whether the idea itself is financially viable. In this case, the developer sees their role as purely technical: build the requested app and deliver the product as specified.

From a professional standpoint, many freelancers operate under this exact principle. Clients are responsible for the business risk of their own ideas, while developers provide the technical service they were hired for. As long as the developer does not mislead the client, exaggerate the project’s potential, or intentionally deliver poor work, their role remains focused on fulfilling the contract.

However, some observers argue that professionals also carry a soft ethical responsibility to offer honest feedback if they believe a client is making a costly mistake. Transparency can sometimes prevent misunderstandings later, particularly if the project fails and the client looks for someone to blame. Ultimately, the situation reflects a broader tension in freelance industries: balancing personal livelihood with the uneasy feeling that a client’s optimism might be leading them toward a risky investment.

Here’s how people reacted to the post:

Many commenters supported the developer, arguing that clients are responsible for their own choices.

Some users offered more balanced takes about professional responsibility.

A few commenters added humorous perspectives about the realities of freelance work.

This situation raises interesting questions about where professional responsibility ends and personal ethics begin. The developer believes their role is to build a product according to the client’s request, while some observers argue that warning the family about potential risks might be the more ethical approach.

At the same time, business ideas succeed and fail all the time, often in unpredictable ways. Should freelancers step in when they believe a client is making a poor financial decision, or is that simply beyond the scope of their job? And if you were in the developer’s position, would you accept the project—or walk away?