Conversation

Joe Masilotti

@joemasilotti

Jun 14, 2022

One week later and I have more insight and have narrowed down my next steps to one of three options.

Quote Tweet

Joe Masilotti

@joemasilotti

Jun 8, 2022

There are now a few businesses trying to "cheat" the business model of railsdevs. And I'm not sure how I should proceed. Some thoughts

Show this thread

Joe Masilotti

@joemasilotti

Jun 14, 2022

I learned that a fair amount of businesses are using the part-time plan to "trial" the website. They cited wanting to see the quality of leads, making sure folks respond, and a few other reasons. This isn't acceptable (IMO), but it's better than my original idea of "cheating".

Joe Masilotti

@joemasilotti

Option 1: Make it more obvious what each plan can do Shoutout to

@jennbot3000

for this one, the idea is to have a business explicitly say what type of role they are hiring for when reaching out to EACH developer. More context and ideas here:

github.com

Business subscription (part-time vs full-time) context · Discussion #489 · joemasilotti/railsdevs...

When a business on a part-time subscription starts a conversation with a developer who is interested in part-time contract, full-time contract, OR full-time employment, it's not clear to th...

3:01 PM · Jun 14, 2022

Replying to

Option 2: Shift from part-time/full-time plans to self-serve/white-glove plans You can hire anyone on either plan + 10% fee for full-time hires. But the white-glove plan includes personal onboarding, hand-picked developers, and more. Inspiration from

on this one.

Option 3: De-emphasize the part-time plan I'm not removing the part-time plan but I could bury it a little on the pricing page. Goal would be to highlight more of the features of the $299 plan and make it the default. You would only find the part-time one buried at the bottom.

Joe Masilotti

@joemasilotti

Jun 14, 2022

I'm hoping to dive in to this early next week! If you have any feedback or more ideas I'd love to hear them.