Jumping into a new development project is an exciting time. If you’re a client, you’ll be bustling with ideas, ready to get started and make your dreams come alive (or fix up where the last person stuffed up!). If you’re a developer, you’ll be keen to get the ball rolling and start laying the project groundwork.
But there are some things that a client can say to a freelance developer in that first conversation, or even halfway along with the project, that won’t leave a good impression.
Let’s check out what freelance developers might just be thinking when a few words are uttered, and our tips for clients and developers who encounter these scenarios.
Looking for top talent fast? See how Arc can help you:
⚡️ Find developers, designers, marketers, and more
⚡️ Freelance or full-time remote + fully vetted
⚡️ Save up to 80% with global hires
Hire top talent with Arc risk-free →
In pre-project discussions…
1. You’re the expert, I trust your judgment!
“Ah, you don’t know what you really want, so you want me to come up with the ideas for you? The last guy I did that for said that it wasn’t what he envisioned at all, without outlining his vision. Nope, not going down this rabbit hole again.”
Tip for clients: Make sure that your project requirements are well outlined. Think of your developer as a builder — they can’t build your house without a plan. Feel free to ask for their informed suggestions or opinions, but realize they are just that: suggestions.
Tip for freelance developers: Explain to your potential client that you require direction to build the product of their dreams. You can suggest options to gain further understanding of what they are looking for, but they should make the ultimate decision.
2. It’s like a combination of Soundcloud, Facebook, and Skype
“Huge, complex platforms are years and years of work with a team of great developers. It’s not like I can just copy and paste Facebook!”
Tip for clients: If your project has a lot of “bits” and is like a large, existing platform, you will need to invest a significant amount of time and money and hire a team of developers, not just one developer.
Tip for freelance developers: Outline to the client the time/money involved in such a project, and if the client has the resources and you can pull together a team, the project may still be workable.
Read More: The Ultimate Freelance Software Developer Hiring Guide
3. I have a tight budget
“Does this mean you’re asking me to reduce my rate? Look, I might be able to take a pay cut if it sounds like an amazing, ongoing, and well-planned project or it’s something I’m very passionate about — but that’s it.”
Tip for clients: A developer’s advertised rate is because that is their current market worth. You may be able to negotiate a lower rate, depending on the project, however lowballing can be seen as insulting. You can use the freelance rate post as a guideline.
Tip for freelance developers: Assuming you’ve properly set your freelance rate, decide whether you’re interested in doing the project at a reduced rate and whether it will be worth it to you personally. Make sure to also have a rough idea of how long the project might take and the hours involved.
4. I pay by equity since this will be 100% successful
“I don’t work for free, no matter how successful you think this is going to be. I still have bills to pay.”
Tip for clients: If you can’t afford a developer, your other options are learning to code yourself, spending the money (if you have it!), or seeking out financial backers to help build your project.
Tip for freelance developers: Explain politely that you can’t afford equity as payment, and your going rate is your current market value.
5. We could be partners
“I don’t know you, and you’re asking me to be your business partner? Ok, that’s not weird at all, no.”
Tip for clients: Even if you think the developer sounds amazing and you want to be partners straight away, play it cool. Think of it like how strange it would be asking someone to marry you on the first date! Go on a few work dates with a potential partner first.
Tip for freelance developers: Laugh and say I’d have to get to know you first!
Read More: Good Developers Don’t Always Make Good *Freelance* Developers
6. I think it will be really successful, I asked a few of my friends…
“Hey, I’ll build it for you if you like, but if you’re basing your market research on people who like you after a few glasses of wine, you might not have thought this through enough.”
Tip for clients: Do some solid market research before building your product.
Tip for freelance developers: If you are happy to build the product for the client, go ahead. Product success is not your concern unless you have equity shares.
7. Let’s take this off-platform
“The freelance platform I use is to ensure I get paid! The last client I had that I went off-platform with disappeared without a cent in my bank account…”
Tip for clients: Developers use freelance platforms to protect themselves financially. By all means, use Zoom meetings or Asana, or whatever tools you prefer for planning and communications, but keep time tracking and payments via the platform you found them on.
Tip for freelance developers: Explain that using the platform protects you both – that you will do good work for the client, assured by the public feedback system, and that it makes payments easy and safe.
8. We will have more projects in the future
“Sure, you say that now. Let’s just see how this pans out first.”
Tip for clients: See how the project works out first!
Tip for freelance developers: Don’t get your hopes up too high. Test out the waters and see if this really is a client that you would also want to work with in the future if an opportunity arises.
Read More: How to Create a Software Development Workflow for Freelance Hires
Halfway through the project…
9. Can we use blockchain / React Native / X? I’ve been reading a lot about it lately
“Do you know how you want to use it, if it’s applicable, how much time it’s going to add to the project and someone who knows how to do it? Cause I sure don’t, and the learning curve is steep!”
Tip for clients: If you’ve researched the technology enough and know how it’s applicable to your project, ask the developer how to proceed with it — and if it’s possible.
Tip for freelance developers: Ask how it will fit into the project and make a decision about whether it is going to be possible — with estimates of time, budget, and whether other developers will need to be hired for the project.
10. We’re pivoting
“Looks like we’ll be archiving half the codebase then. I wonder when this will ever be finished? Is this going to be impossible to achieve? At least I have work for the foreseeable future.”
Tip for clients: You might be excited about pivoting, but it’s a curveball for your developer. Try your best to instill that excitement within your conversation so your developer is on the same page.
Tip for freelance developers: Hey, don’t they say a change is as good as a holiday? Perhaps it pays not to be too mentally invested in a project.
Read More: How to Integrate Freelance Software Developers Into Your Current Team
11. I’m retiring / changing jobs / going on an extended vacation
“Hmmm, I guess this project is up in the air unless someone else is interested and excited about ownership on your end. I wonder if I should start looking for new clients…”
Tip for clients: As a courtesy, try to have a migration plan in place so your developer can feel assured of how the project will be progressing once you leave.
Tip for freelance developers: Make contact and start a conversation with the new technical lead of the project to determine the next steps.
12. I’m going to need you to roll over to these systems as part of our internal IT restructure
“Uh-oh. Company infrastructure changes are often painful, buggy, and drawn out. This should be fun.”
Tip for clients: Provide documentation for the new systems and as much info as possible to your developer, as well as the reasoning behind the new changes.
Tip for developers: Be patient with the process and let your client know if it is causing disruptions to your workflow, so that you can work out how to streamline it more and not have schedule blowouts.
13. We’re canceling the project
“Looks like it’s time to start looking for work again! I hope it’s not because you’ve gone into administration, and I haven’t been paid for the past month yet, eep.”
Tip for clients: Let your developer down gently and make sure all payments are up to date.
Tip for developers: Look for new opportunities and reach out to your networks!
Read More: How to Do Taxes When Hiring a Freelancer
Wrapping Up
As a client seeking a developer, make sure you’ve scoped the project properly, have some idea of the difficulty or technology level required, and realize that this is your freelance developer’s full-time job — they can’t afford to work for nothing.
Devs? If you think a client is wasting your time, it’s fine to end the conversation politely (and if you are happy so far, don’t forget to ask them vetting questions, before you start a project, too!). And if you haven’t already, apply to be a freelancer on Arc.
With these tips in mind, clients and developers can both try to avoid huge unforeseen changes in the middle of a project — it’s (generally) no good for anyone involved.
If you’re a developer, what “interesting” things have clients said to you, and how did you respond? Let us know in the comments section below!
You can also try Arc, your shortcut to the world’s best remote talent:
⚡️ Access 450,000 top developers, designers, and marketers
⚡️ Vetted and ready to interview
⚡️ Freelance or full-time
