I'm in the works of a Fiverr-esque competitor. There's going to be the core model of 0% commissions and other features that I won't bother splaying out here.
One thing that's been bugging me, is making an effective dispute process.
My dad suggested for a "deliverables list", something that is absolutely critical in real world industry software development. My counter to it was with freelancer services like graphic artists/designers, business centric tasks (marketing, documentation, consultation, etc.) its really difficult to define a list of concrete deliverables.
So I ask all of you, what is a PRACTICAL dispute process in your eyes? And what is an IDEAL dispute process?
PRACTICAL = Something that you've seen before that works, its real, and likely to scale/work at a large platform size.
IDEAL = Your perfect vision of how a dispute process would go. Usually comes with a lot of assumptions about the Client, Freelancer, and the Dispute Moderator / Scam Resolver, however you want to phrase it.
Feedback here on the thread OR on in my DMs on Discord
Devil#0666
One thing that's been bugging me, is making an effective dispute process.
My dad suggested for a "deliverables list", something that is absolutely critical in real world industry software development. My counter to it was with freelancer services like graphic artists/designers, business centric tasks (marketing, documentation, consultation, etc.) its really difficult to define a list of concrete deliverables.
So I ask all of you, what is a PRACTICAL dispute process in your eyes? And what is an IDEAL dispute process?
PRACTICAL = Something that you've seen before that works, its real, and likely to scale/work at a large platform size.
IDEAL = Your perfect vision of how a dispute process would go. Usually comes with a lot of assumptions about the Client, Freelancer, and the Dispute Moderator / Scam Resolver, however you want to phrase it.
Feedback here on the thread OR on in my DMs on Discord
Devil#0666
