3 comments

  • christophilus 13 hours ago
    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.

    • ufvy 12 hours ago
      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.

      • christophilus 7 hours ago
        I’d slightly lean towards prioritizing making good matches. But I’d allow folks to set their own rates shortly thereafter.
  • ufvy 13 hours ago
    Ask me anything. My first launch
  • 6510 6 hours ago
    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