I think participants should be able to set their rates. They might start low and increase it as their reputation grows.
Quality is a tough problem, and I don’t think anyone has managed to solve it. Someone can ace an interview and still be a crappy employee. I think this could sort itself out with time and reputation building, so maybe don’t worry about it.
For finding rooms, it seems like freelancers should be able to describe what they are looking for, and then you match that to a room’s description/ purpose. AI could potentially be beneficial here, as the matching should be fuzzy.
Really appreciate this thoughtful feedback! You've identified some key improvements:
*Variable rates*: Love this idea. Right now it's flat $72/hr, but you're right – a junior dev shouldn't charge the same as a senior architect. Thinking through implementation:
Option A: Participants set their own rate ($30-$200/hr range?)
- Pro: Market finds equilibrium
- Con: Chefs don't know cost upfront (pre-auth becomes tricky)
Option B: Skill tiers (Junior $45/hr, Mid $72/hr, Senior $120/hr)
- Pro: Predictable pricing for chefs
- Con: Who decides the tier?
Leaning toward Option A with a visible rate display before participants join. What do you think?
*Quality & reputation*: Totally agree – even Google/Meta make bad hires sometimes. Your "let it sort itself out" approach makes sense. I'm thinking:
- Public profile showing: total earnings, # sessions, avg session length
- No ratings initially (avoids gaming/fake reviews)
- Let the market decide: if someone consistently gets kicked or has 2-min sessions, that's a signal
The earnings transparency might be enough – someone with $10k earned across 200 sessions is probably legit.
*Room matching with AI*: This is brilliant and solves the discovery problem elegantly. Currently participants just see a list of open rooms. Your idea:
1. Freelancer creates profile: "React expert, 5 yrs exp, good at performance optimization"
2. Chef creates room: "Need help with Redux state management causing re-renders"
3. AI matches and notifies relevant freelancers: "New room matches your skills"
This could use semantic search (embeddings) to match "Redux performance" to "state management optimization" even if terms don't overlap exactly.
Quick prototype question: Should I prioritize variable rates or AI matching first? Which would have more immediate impact?
Thanks again – this is exactly the kind of feedback I need.
The entrepreneur chat session should start with an LLM to analyze the task, asks questions and writes an information dense summary as well as an extended one. (rather than the usual truncation) If applicable it should also ask if information from previous jobs should be pulled in. The freelancer will scroll over the open tasks, view the extended description and asks the LLM for further specifics. (to be included in a new short/long description)
The LLM may also send push notifications if your settings, history and profile suggest you are uniquely qualified for the job.
The front page should be a work space with 3 tabs. The default tab is for the tasks currently open. Programmers should not be bothered with endless docs and tons of clicking around, they should type the url and immediately see what they are suppose to do. All other things come second.
Second tab is for posting jobs.
3rd tab is for people who some how ended up on the page not knowing why they are there.
What I like to do is not bother people with registration until it is required. You can spend as much time as you like typing a task description, if you don't actually submit it there is no need to pay or register. They need to write down what is on their mind, it is terrible to bother them with other things.
Maybe flexible pricing should be a plan B for when you have insufficient jobs coming in for the number of developers online/registered OR insufficient devs for the amount of tasks posted.
I think participants should be able to set their rates. They might start low and increase it as their reputation grows.
Quality is a tough problem, and I don’t think anyone has managed to solve it. Someone can ace an interview and still be a crappy employee. I think this could sort itself out with time and reputation building, so maybe don’t worry about it.
For finding rooms, it seems like freelancers should be able to describe what they are looking for, and then you match that to a room’s description/ purpose. AI could potentially be beneficial here, as the matching should be fuzzy.
Really appreciate this thoughtful feedback! You've identified some key improvements:
*Variable rates*: Love this idea. Right now it's flat $72/hr, but you're right – a junior dev shouldn't charge the same as a senior architect. Thinking through implementation:
Option A: Participants set their own rate ($30-$200/hr range?) - Pro: Market finds equilibrium - Con: Chefs don't know cost upfront (pre-auth becomes tricky)
Option B: Skill tiers (Junior $45/hr, Mid $72/hr, Senior $120/hr) - Pro: Predictable pricing for chefs - Con: Who decides the tier?
Leaning toward Option A with a visible rate display before participants join. What do you think?
*Quality & reputation*: Totally agree – even Google/Meta make bad hires sometimes. Your "let it sort itself out" approach makes sense. I'm thinking:
- Public profile showing: total earnings, # sessions, avg session length - No ratings initially (avoids gaming/fake reviews) - Let the market decide: if someone consistently gets kicked or has 2-min sessions, that's a signal
The earnings transparency might be enough – someone with $10k earned across 200 sessions is probably legit.
*Room matching with AI*: This is brilliant and solves the discovery problem elegantly. Currently participants just see a list of open rooms. Your idea:
1. Freelancer creates profile: "React expert, 5 yrs exp, good at performance optimization" 2. Chef creates room: "Need help with Redux state management causing re-renders" 3. AI matches and notifies relevant freelancers: "New room matches your skills"
This could use semantic search (embeddings) to match "Redux performance" to "state management optimization" even if terms don't overlap exactly.
Quick prototype question: Should I prioritize variable rates or AI matching first? Which would have more immediate impact?
Thanks again – this is exactly the kind of feedback I need.
I’d slightly lean towards prioritizing making good matches. But I’d allow folks to set their own rates shortly thereafter.
imho...
The entrepreneur chat session should start with an LLM to analyze the task, asks questions and writes an information dense summary as well as an extended one. (rather than the usual truncation) If applicable it should also ask if information from previous jobs should be pulled in. The freelancer will scroll over the open tasks, view the extended description and asks the LLM for further specifics. (to be included in a new short/long description)
The LLM may also send push notifications if your settings, history and profile suggest you are uniquely qualified for the job.
The front page should be a work space with 3 tabs. The default tab is for the tasks currently open. Programmers should not be bothered with endless docs and tons of clicking around, they should type the url and immediately see what they are suppose to do. All other things come second.
Second tab is for posting jobs.
3rd tab is for people who some how ended up on the page not knowing why they are there.
What I like to do is not bother people with registration until it is required. You can spend as much time as you like typing a task description, if you don't actually submit it there is no need to pay or register. They need to write down what is on their mind, it is terrible to bother them with other things.
Good luck!
Ask me anything. My first launch
Could have more flexible pricing and offer less expensive or even free* help from students. It seems a great place to learn.
* pay only a platform fee
1.2 dollars per minute is pretty cheap.
Maybe flexible pricing should be a plan B for when you have insufficient jobs coming in for the number of developers online/registered OR insufficient devs for the amount of tasks posted.