Engineering · Test and measurement · Industrial · Energy
Engineering content, written properly.
Technical articles, application notes, case studies and product content for companies that make physical products. Each piece has to satisfy the engineer who checks the figures, the buyer who signs off, and the search engine both of them use.
Why is most engineering content so poor?
It is usually written by one of two people: a marketer who does not understand the product, so every sentence becomes "innovative solutions" and "seamless integration", or an engineer who understands it completely and has never had to consider the reader, so the result is a datasheet with paragraphs. Neither gets read, and neither gets a product specified.
The job is to understand the product and the reader equally. Know the product well enough to explain why it matters, then explain it in the order a reader needs. What problem it solves. What it replaces. What the numbers mean. Where the catch is. Engineers are sceptical readers, and they respond to writing that respects that.
What I've written
- HBK (Hottinger Brüel & Kjær): content on NVH testing and sound and vibration measurement, the Fusion-LN data acquisition platform, and a customer case study for NASA
- IMI: articles on valve manifolds and energy saving in pneumatic and fluid control systems
- Hoymiles: solar and microinverter content for installers and homeowners
- Panasonic and Epicor: technology and manufacturing content, ghostwritten and published under the brand names
- Data Interchange: EDI and API integration for manufacturing supply chains
Consumer-facing guides to solar panels, inverters and renewables for the Independent and the FMB are covered under SEO content.
- HBKNVH testing: noise, vibration and harshness contentTechnical
- HBKFusion-LN data acquisition platformProduct
- HBKCustomer case study with NASACase study
- IMIValve manifolds in pneumatic and fluid control systemsTechnical
- IMIEnergy saving in compressed air and fluid controlTechnical
- HoymilesSolar and microinverter content for installers and homeownersProduct
- PanasonicTechnology content, ghostwritten under the brand nameTechnology
- EpicorManufacturing software content, ghostwritten under the brand nameManufacturing
- Data InterchangeAPI integration for manufacturing supply chainsEnterprise
Published under the brands' names or behind logins. Samples on request.
The brief
Written for the engineer, the buyer and the search engine at once
Good technical content does three jobs at once: it convinces the engineer it is accurate, gives the buyer a reason to proceed, and ranks for the query the engineer searched for. I write for all three readers in the same piece.
Brief a technical piece →Questions people ask
Questions about engineering content
What engineering sectors do you write for?
Test and measurement (HBK: NVH testing, the Fusion-LN data acquisition platform, and a case study for NASA), industrial automation and fluid control (IMI: manifolds and energy saving), solar and renewables (Hoymiles, plus solar guides for the Independent and the FMB), enterprise manufacturing software (Epicor) and consumer electronics (Panasonic).
Do you have an engineering background?
No. I'm a writer who has spent several years on technical subjects. I work from datasheets, standards, application notes, primary research and interviews with your engineers, and the subject-matter expert reviews every draft for accuracy before it goes anywhere.
Can you interview our engineers?
Yes, and it is usually the best way to get a piece right: a 30 to 45-minute call with the subject-matter expert, a draft they review for accuracy, and a final version that reads clearly rather than like a datasheet.
What formats do you write?
Application notes, technical articles, case studies, white papers, product and solution pages, knowledge base content, buyer's guides and ghostwritten pieces for trade press.
Will it rank and get cited by AI search?
If it is written properly, yes. Engineers search in specifics, and AI answer engines cite specifics. Definitions, figures, standards and named sources are what both reward. See AI search optimisation for how I structure it.