How much should I charge the client for my mobile app?

[Takka 13,377]

3 hours ago, Puddin said:

Unless that company has 2 employees, $50 (pronounced fitty) is way too low.

At such a low quantity, it's either not going to be economical for the creator or not economical for the client, and since it's at the client's request, they're the ones that should bear the burden of that cost. I'd say a base price of like $250, and then you could consider a licensing model to inflate the price beyond that, if they want it for more than like 5 or 10 guys. You're putting in the same amount of work if one guy uses it or if 500 people use it, so there should be a base price that recoups the creator's investment.

 

In the future I'd suggest naming a price for their request, and say if they're not happy with the result that they simply don't have to buy it. But they should be aware of the cost of what they're asking for.

[Solaris 3,581]

On 8/30/2017 at 8:42 PM, Daywu said:

Hey guys, I need yall's opinion on this matter. I am making a mobile app for a local company in my area. The app is used to keep track of employees' time sheets. They are able to clock in/clock out their times, calculates their hours, and sections them off by weeks. Now for the admin, he/she can view an employee's time sheet, and delete, modify, and add an employee. I know it is a simple app but my question is, what is a reasonable amount to charge the consumer for this app? The consumer is offering $50 for the app which is ridiculously low. I asked him for around $250-$500, but he's not willing to offer that amount. 

Considering things like Deltek and whatnot, you are being ripped off for that kind of work and it sounds like the client is a cheap piece of shit that doesn't want to pay for already existing services. Don't develop it once and get a flat lump sum. Develop it, make it proprietary and make them sign a support agreement so the client doesn't come back 10 years later and expect you to update their software for free and threaten legal action if you refuse. The code is YOURS. Do not let them say that because it's their money it's their code. I would sit down with a lawyer that specializes in contract/licensing/service level agreements.

[Daywu 194]

1 hour ago, Solaris said:

make it proprietary and make them sign a support agreement so the client doesn't come back 10 years later and expect you to update their software for free and threaten legal action if you refuse.

Thanks for the heads up! I shall definitely look into this and bring it up in the next meeting.

 

I appreciate all the help and the advice you guys are giving me. I will stand my ground and will not let this arrogant bastard pay me cheap for something I worked hard on. If he doesn't want it... that's fine with me. He can continue writing everyone's times in his fucking notebook. The next time I do this for someone, I am going to discuss a price before coding anything to make sure the consumer is not wasting my time. I have learned my lesson and I'll keep you guys updated of the results.

 

Edited September 1, 2017 by Daywu

[Solaris 3,581]

11 hours ago, Daywu said:

I am going to discuss a price before coding anything to make sure the consumer is not wasting my time.

Yes, do not do anything until they show money and sign off that they requested the service. It's more CYA and non-repudiation of services if they decide to make it a legal issue. It also prevents them from trying to negotiate further down the line to try to lower the already agreed-upon charges.

[Daywu 194]

UPDATE: The consumer never got back to me about the app, so I never sold it to the company. From this experience, I have learned that I should have documented contracts and come to an agreement before I start anything. Otherwise, I would just be wasting my time like what just happened in this situation.

Edited March 19, 2018 by Daywu

[Sunstriker7 698]

That sucks, but it's a good lesson. At least you learned it cheap.