When you post project briefs on a site like Codeable, you’re putting yourself out there in front of developers who have proven themselves worthy of being called experts. We might see as many as fifty project briefs a day, and someone in our position can easily discern which projects are worth investigating further and which ones would be a complete headache for us. There isn’t a soft way to put this, but I mean it with all respect: when you post your project briefs, you need to bring it. You need to, in a few sentences, let us know that you know what your project is all about. That you’ve thought it through, and that you respect our time and expertise. Project briefs that expect me, or any other developer worth his salt, to read minds or solve esoteric problems just flat out won’t be considered. In fact, simply writing a competent proposal will put you in the top half of potential clients We estimate that 45% of projects posted on Codeable get passed over because not a single developer wants to take them on. We’ve all managed projects that were trainwrecks from the beginning and spun them into gold at some point in our careers, but that’s why we’ve earned the right to opt out of them
Share This