How to write better work enquiries.

A 3 minute read, written by Chris Annetts on 30 May 2017.

For somebody with little-to-no experience of the web, the idea of enquiring about a new piece of work must be more than a little daunting.

What if I say too much? What if I ask too little? What if they’re too busy? Or too expensive?

Throughout my time in the industry, I’ve been lucky enough to receive a relatively frequent flow of work enquiries. Based on my own experiences, one thing has become abundantly clear: nobody is quite sure what to send in that first email.

Here are five tips that, with a bit of luck, should put you in the good books of a prospective web professional:

If you’re expecting more than a few sentences back, you’ll have to put a little effort in yourself too.

Each project has its own set of nuances and constraints. With so much variance in the work we produce, it’s essential that we’re afforded as much information as possible.

  • Who are the company?
  • What’s the product?
  • What problem are you trying to solve?
  • Who are you audience(s)?

Every time a web professional receives a work enquiry along the lines of, “Hi. We need an app designed. 8–9 pages. When can you start?”, a kitten dies. Just don’t do it.

Knowing what it is that convinced you to send the message can quickly help build a picture of what’s important to the individual or organisation in question.

Was it locality that drew you in? Was it their experience in your field of interest? Or maybe a particular piece of work stood out? Understanding the motivations behind the enquiry allows us to align ourselves closer to your wants and needs; be it face-to-face meetings, industry know-how, or a particular design direction.

It may sound obvious, but what are you expecting to be handed at the end of the project? As a designer for example, it could be anything from static mockups created in Sketch, through to front-end templates in your chosen language or framework.

I’ll often receive enquiries that fail to specify what it is that’s being requested. At this stage, it may be that you just don’t know, and that’s fine; a web professional worth their salt will be able to advise you here. But leaving it open for interpretation is never clever.

As you may have guessed, freelancers and agencies alike spend an awful lot of energy spinning plates. We have very little influence on the periodicity of work enquiries, and like London buses, they’re rarely comfortably spaced.

Time and time again, the timeframe for the work is given as “ASAP”. Of course you want it as soon as possible; who doesn’t!? Instead, tie your timescales to actual events; in time the new school year, the busy summer months, or your new brand rollout in March.

I’ve been involved in projects that cost as little as £2,000, and others that were as much as £100,000+. There’s a massive amount of variance in cost, and knowing how much you have set aside is critical to understanding whether the enquiry has legs.

When a freelancer or agency pick up that first message, they’re making an investment in you. It takes time to read, digest, discuss, and reply; probably more time than you’d expect.

At this point, you may not know your budget yet, and that’s ok. But you’ll have a ballpark figure. Are we talking £100, £1,000 or £10,000? Any indicator is better than none.

Being upfront about your budget allows us to quickly understand whether or not the project is going to be possible, and being able to quickly dismiss an unsuitable enquiry saves both parties time and energy.