Technical Blog Post

Starting at

$

500

About this service

Summary

A technical blog post can introduce a new feature, explain important concepts your software or SaaS relies on, discuss solutions to common issues that users face, or be something else entirely. I will help you define the purpose and scope of the post, then write it and create illustrations. I will make sure that the post is technically spotless for professionals reading your blog as well as appealing to the general public.

Process

Information gathering Every post you publish needs to align with your business objectives. Are you building brand awareness? Driving up conversions? Upselling? We'll discuss the goals of the post and agree on the outline and the scope.
First draft I write and share the first drafts of all planned posts with you.
Illustrations I will create screenshots, diagrams, and other illustrations.
Revisions and finalization I will incorporate your edits and feedback to make the final revision of the post that is ready to go live.

FAQs

  • What is a regular post?

    A regular post is between 700 and 1200 words. Long-form posts, which take more time and effort to craft, are typically above 1200 words.

  • Can you make four posts a month? Or eight?

    Yes, let's talk.

  • What if we decide to postpone rolling out a feature that we were going to discuss in a blog post?

    I recommend having a minimum of two posts ready at all times to replace the one that bites the dust.

  • Do you do research and link to sources?

    I always do due research and have my posts fact-checked by experts in my client's company. How much linking to sources will be done in the final draft ultimately depends on you. I can be Wikipedia-pedantic if you like.

  • How do you write release notes?

    A typical software release includes new features, improvements, and a number of fixes—some trivial and some critical. The trick is to know what to focus on exactly, what level of detail to stick with, and when to stop and list some things under "Misc changes". Step 1 is to compile the overall list of changes; I can extract that from 'git log'. Step 2 is to categorize and group the changes. Step 3 is to assign importance to each one, then write the copy and make illustrations. The first few times I will need some help setting feature priorities. Once I know my way around the product, I can do that myself.

What's included

  • Quick delivery

    For pieces below 1200 words, I will write the first draft in 2 days. For long-form posts, this will take up to 3-4 days.

  • Any format

    The post can be an introduction to a new feature, an explainer, release notes, or a thought leadership piece.

  • Few iterations

    Once we agree on the scope, style, and level of detail, I will write the copy that exactly matches your requirements.

  • Well-researched content

    I actually use the SaaS or the software I write about, double-check all facts I present, and link back to sources.

Recommendations

(5.0)

Brad Collette • Ondsel

Client • Dec 19, 2024

I hired Alex initially to write some marketing content. He did an excellent job with the content but also proved to be far more versatile. He was able to coordinate website redesign, recommend experts, help with analytics, and so much more. He quickly became a trusted advisor and an essential member of the team. Can't recommend him highly enough.

Jarosław Foksa • Boxy SVG

Client • Nov 15, 2024

I hired Alex for the first time years ago because I really liked the quality of his articles on his blog. He ended up doing several projects for me. Every time he delivered great results that required very little tweaking after the first draft. I will gladly work with him again in the future.


Duration

2 days

Skills and tools

Copywriter
Technical Writer
Google Docs

Industries

Cloud Computing
SaaS
Software

Work with me