Ok, in that case I'd make the landing page all about pricing.

I'd also think about if there aren't any other benefits your approach might have. Maybe having everything happen on my phone is a benefit in that I can mix the automated messages with personal ones.

Or that I can use the same phone number for taking calls, etc.

Like @jernejpregelj pointed out there's multiple facets to this.

There's the legal part (equity, revenue/profit sharing, etc) and the logistical/community part.

As for the legal part I recommend talking to financial advisor. I recommend implementing something like this incrementally. Start at a place where you own all equity, but make a public promise to work towards the 51-49 split. Be open, share your numbers, etc. And formalise things over time as profits increase along with community participation. You don't really know what things should look like, until you're actually experiencing the model.

As for the logistical part, I don't think there's a product for this as it's a pretty unique approach. But again, I think you can just start out incrementally. Since it's a developer-oriented product I think it's fine to start with a GitHub Repo and clever usage of issues and labels. As you run into limitations you can start looking for other solutions, or building your own. But like the legal aspect, you probably don't really know what you'll need until you're in the thick of it. So just start simple and incrementally improve on things.

You can try t.me/wipgigs

I would recommend specifying what you're looking for though. Nomad List and WIP are very different products from a technical perspective.

It's also not clear what you mean with v1.0 – I don't even know what version number I'd give WIP right now as it's been improved incrementally.

Perhaps you can run an experiment with a freemium option.

Free gets you some/all the job posts, but a week later.
Paid gets you all of the job posts the same day.

That allows you to grow your userbase, but still charge those people who are willing to pay.

Clever idea. I can see this being useful for more than just job listings. Being able to created a saved Twitter search and getting a daily/weekly recap of matches can be useful for all kinds of things. But it's good to start off in one vertical like you do now.

As for the revenue model, I think the real money is on the other side of the equation. Companies who are hiring tend to pay $300+ to post a job listing.

So to get let's say $1,000 in monthly revenue, you either need to grow to 180 paying subscribers or find 3-4 companies posting a job listing each month. The latter requires a decent sized audience, but once you have that I think you'll make significantly more money.

Therefore I'd lean towards making it free of charge (or perhaps "pay-with-a-tweet", that sort of thing), and building up your user base of job seekers. Or at least experiment a bit with a free option to see how fast you can grow it, if you were to go that route.

Interesting experiment!

Keep in mind that each team member has full access to the product. Which means people would be able edit/delete/complete each other's #nomadlife todos.

Of course I'm always open to changing functionality like this, if there's significant demand from the community. So let's see how it goes :)

Looks like you already figured it out, but for other people reading this: YES, a product can have multiple makers.

1. Visit your product page
2. Click the Edit button
3. Add a maker (they will need a WIP account)
4. Have them accept the product invitation they receive via email

You can now both manage todos for the product. That means adding/editing/deleting/completing. Just be careful when deleting/uncompleting a teammate's todo as that might affect their streak.

If your main differentiator is price, I think you should prominently display your rates and compare them to the competition.

If I understand correctly, you somehow let me install an app on my phone, and then SMS messages are sent through that phone? That seems rather counter intuitive. I'll need to buy a bunch of phones, attach them to their chargers in my office/home, hope they don't restart due to automatic updates, keep track of their subscriptions, etc.

That seems backwards. The whole industry is moving the opposite direction towards managed solutions. Just look at cloud hosting. We went from managing our own hardware servers, to AWS.

Unless the alternative is significantly more expensive, I'm not sure I understand the business model. Is there a benefit to this approach versus using a Twilio-like API? Apart from pricing?

Thanks for making/updating this 🙌

One thing you can do throughout the week is bookmark the articles you end up reading. Perhaps you already bookmark them anyway. And then every once in a while take some time to analyze them. What made you want to read them? How did you know it would be worth your time without having read it first? (Kind of a paradox when you think about it.)