- Nov 8, 2009
- 8,887
- 9,192
I was thinking about building an app for a medium-large company that needs one but has not put a foot forward to get one made. They already have some other technology in place and their customers are very vocal, so I think once I show the customers, they'd take some interest.
They have a very large budget and a recurring high-ticket customer base of thousands of people.
I have enough connections with the customers to be able to get many customers using it and supporting it. Then the pressure and gossip about the app between customers would hopefully sell it to the company or I could even monetize it through other means. I could finish say 30% of the features and list some other ideas and say "Coming Soon" in the app so the customers would start to ask the business about when that feature is coming.
I hate proposing stuff that doesn't exist when I know I can put a few dozen hours of creative programming into an iOS app for a business that will spark interest and potentially sell for $xx,xxx, it's very intriguing. I'm sure many of us have done this for websites and other B2B products: after you build something, apply it to the business, and show them exactly how it can be used to benefit, the client takes significantly more interest in what you're selling.
So basically, is there a way I could structure the app for the company and get away with it? It would not be harmful to them, but beneficial so I have a hard time thinking they'd have a problem with it. I'd like to use their name as the name of the app so people can find it via search. So really, I can argue both sides.
Would love to hear a bit from the experienced folks on here.
They have a very large budget and a recurring high-ticket customer base of thousands of people.
I have enough connections with the customers to be able to get many customers using it and supporting it. Then the pressure and gossip about the app between customers would hopefully sell it to the company or I could even monetize it through other means. I could finish say 30% of the features and list some other ideas and say "Coming Soon" in the app so the customers would start to ask the business about when that feature is coming.
I hate proposing stuff that doesn't exist when I know I can put a few dozen hours of creative programming into an iOS app for a business that will spark interest and potentially sell for $xx,xxx, it's very intriguing. I'm sure many of us have done this for websites and other B2B products: after you build something, apply it to the business, and show them exactly how it can be used to benefit, the client takes significantly more interest in what you're selling.
So basically, is there a way I could structure the app for the company and get away with it? It would not be harmful to them, but beneficial so I have a hard time thinking they'd have a problem with it. I'd like to use their name as the name of the app so people can find it via search. So really, I can argue both sides.
Would love to hear a bit from the experienced folks on here.
