Desperately Seeking a Native English Technical Writer?

Native English Technical Writer - UK

Hire a native English-speaking technical writer

Fed up with technical writers who say they write in English, but deliver content that is in broken English and needs editing? Don’t worry, you’re not alone – lots of businesses are finding out the hard way that outsourcing technical writing ends up costing more than they expected. Because how much does poor quality documentation cost your company? Think about it. What do customers do when they don’t understand the documentation? They contact customer support. Which costs you each and every time. Then you decide to put the documentation right – that’s an additional cost. And while all this is happening, your customers are getting frustrated with your products and services.

Quality is important. And that’s what you get from StrayGoat Writing Services. As an English technical writer, living in the UK, I write and speak in ‘native English’. And I’m a very experienced and highly qualified technical writer too (I’m also a trained copywriter, so if you need a marketing angle on your content, that’s not a problem).

Documentation for Customers in the USA, UK, Canada, Australia, New Zealand…anywhere!

When you are looking for a technical writer who can turn your translated English into polished, professional-quality documentation, there are a few things you need to consider:

  • The technical expertise of your customers
  • The type of language your customers understand
  • The ‘flavour’ (or ‘flavor’) of English they use.

The first two points are important no matter what language your documentation is written in. To connect with your customers and make their lives easier, your documentation has to be written in a way that meets their needs. That means designed to provide them with the right level of information, using terms and concepts that they understand. This is all about understanding who your customers are, and any good technical writer will look to find out this information right at the start of the project.

The third point might not seem so important at first, because there isn’t a huge difference in the language used by Americans and Brits and Aussies and all the rest. But there is some difference, and in certain places, it can cause confusion, or even worse, ambiguity. It is also important to be mindful of definite terms, such as ‘prevents’ and ‘ensures’, as these could get you into trouble, especially in cultures where customers are quick to take legal action (USA!).

How do I know about these issues? I have learned about them through experience and training. When I worked for Schneider Electric, a huge international company, I had to write in US English all the time, as that was the company policy for documentation across the world. I also had to avoid certain terms that were considered unsuitable.

These days, I avoid those ‘unsuitable’ terms all the time – it has become a good habit of mine. So when I write or edit your content, I can make sure you avoid those potential traps.

But What About the Cost? I Could Just Hire a Technical Writer in India for Less

It is true, you will find cheaper technical writers in India and other countries too. But are they going to meet all your needs?

  • High quality documentation, written in a style that your customers understand
  • Instructions and conceptual information that avoids ambiguity and common ‘faults’
  • Clear, consistent communication with you and your team throughout the process
  • Payment as agreed, no requests for full payment before the job is complete.

From what customers (and other technical writers) tell me, getting all of the above with an outsourced technical writer is rare indeed. And the problems they have told me about match some of the issues I have experienced when I’ve hired programmers and web designers on the cheap – the quality of product and service isn’t there. As the saying goes – “You get what you pay for”.

If you offer poor quality documentation, how will your customers react? Will they bombard your customer support? Will they complain? Will they turn to other, easier to use or understand products? Even worse, if the documentation is confusing, could they get hurt? I’m not trying to scare you – these are real issues that can affect your business and customers.

Going for the cheapest price now could lead to much higher costs later.

What is the Cost of Hiring a Native English Technical Writer?

Like all things in life, the cost is going to depend on:

  • How much experience the technical writer has
  • How complex your product or service is
  • The amount of content you need to be written or edited.

Choose me, and I will create/edit your content for £30-40 per hour, depending on the complexity of the project and the amount of writing needed. That’s a maximum of £40 per hour for a native-English technical writer with 18 years of experience, a degree in technical communication, plus copywriting skills. So, not as pricey as you may have thought.

You’ll be Working from Home in the UK?

Yes. I work from home and prefer to communicate via email and Skype. I’ve worked with people in Australia, Poland, Ukraine, the USA and Canada in this way and there’s never been a problem. Sure, sometimes things get a little lost in translation, but that can happen face-to-face too! Trust me, it works – I work for UK companies like this too, and some of their developers are from different countries.

Time zone differences can be tricky, especially if you are on the other side of the world. But it can work in your favour too. For example, let’s say you are in China and need a particular page to be 100% right as soon as possible. I can pick that up and get it done while your business is closed for the night and it will be ready first thing in the morning. Time zones can be good as well as bad :)

Select the link to find out more about hiring me as a work-from-home-technical-writer.

Hire A Native English Technical Writer Today

Ready to hire me? Yes? Then please get in touch and let me know about your project. Click here to go to the Contact Form page.