4 ms·
EXISTING: 1. Rental properties. Have 3 rentals that we purchased last year as part of a 1031 exchange (after selling the family ranch). I manage them and its b
by callmeed 10y ago
EXISTING:
1. Rental properties. Have 3 rentals that we purchased last year as part of a 1031 exchange (after selling the family ranch). I manage them and its been fairly low maintenance so far (knock on wood). FWIW student rentals in a university town aren't as bad as you might think. Most have a steady source of rent (parents or financial aid) and if you choose students in hard majors, they're less likely to party and trash the place (my theory).
2. Niche websites. I'm silent partner in a company that does website design and hosting for a niche industry. Obviously, we have people running operations and support so its only passive for me, but it makes a lot of money. I know Wix and Squarespace and Weebly are the big players here but tons of small businesses still need help with their website. Don't overlook something you think is a solved problem.
IN THE WORKS:
3. Jekyll-based landing pages. I think Unbounce and similar services are overpriced if you're just experimenting. So I've built a few landing pages specifically for Jekyll. I've ran a few tests with an attorney and another small business. Going well so far. Plan is to sell them as a one-time purchase for $29 or so. Just need to find a front-end/design partner to help crank out a few more layouts.
4. An API for lists. This might sound weird but I always needs lists of things in projects I make. Think "all the currency codes" or "all the universities in the US". So I've built some scrapers for a bunch of lists and plan to provide them as a simple API or YAML/PList downloads (for iOS apps).
5. Apple TV stuff. Got some Apple TV stuff in the works. Just not sure how that platform is gonna play out.
- AznHisoka 10y agoOn lists I'd want: - a list of all possible domain name tlds (org, edu, info, etc)
- callmeed 10y agoWorking on it
- alexbilbie 10y agohttps://publicsuffix.org https://publicsuffix.org
- stevekemp 10y ago> An API for lists. I've written a few microservices for listing-lists, getting list-members, which generally just serve the contents of a JSON/YAML file. I've done it often enough that I can see the value in a list-server, but equally it's something I'd struggle to see monetizing well, or even at all. How do you plan to handle that? (Because in the worst case you can just be lazy and embed your list-data in your application itself as a lazy-loaded YAML file which is parsed on each request.)
- callmeed 10y agoYeah, I often use the YAML or PList approach myself. My initial pricing experiment will be something like: 1. Buy any single list one-time for $9 (as a JSON/YAML/PLIST download) 2. Pay $49 per year for API access to all lists
- stevekemp 10y agoThat's an interesting pricing model, thanks for sharing. I guess the key to drive subscriptions would be to ensure that your data-sources were updated constantly (where appropriate). I know in the past I've struggled to handle updates to things like UK postal-codes, where additions are frequent and omissions lead to errors being presented to clients.
- callmeed 10y agoYeah, good updates are important but something I think can be mostly automated. BTW, if you're interested in teaming up on it at all, by all means get in touch. I'm never opposed to a capable partner.
- stevekemp 10y agoI think the programming side is trivial enough that you'd probably not benefit from my help/involvement. The harder part is gathering accurate data, working out what lists users even want, and the promotion of the service/site. These last parts are the ones I'd struggle to be useful at.