Menu Close
Close
Get in Touch

Documentation and proposals for the GIS industry, written from inside it.

Technical writing for GIS software companies, system integrators, and the teams responding to GIS tenders. User manuals, admin guides, training materials, technical proposals, and the supporting documents that surround a project — written by someone who has spent fifteen years inside the industry rather than around it.

Learn More
Fitness expert
Personalized training for a strong and active lifestyle
Personal coach
Creative vision

Why a GIS-industry writer, and not just any writer.

Technical writing for GIS software has a context generalist writers spend the first weeks of a project trying to absorb — what a layer is, how spatial queries work, what a user actually does with the tool. That ramp-up time gets charged to the budget either way: explicitly as billed hours, or implicitly as documentation that misses the things only someone in the industry would have caught.
Fifteen years as a lead technical writer and content strategist at a GIS company is what I bring instead of that ramp-up time. The documentation reads as if it was written by someone who has used the software, because — in the way that matters for documentation — it was. The bid responses are framed the way evaluators want to read them, because I have written them from the company side for years.
What You Get

The specific deliverables

Technical writing covers a range of distinct deliverables, each with its own conventions and audience. If you came here looking for a specific kind of writing, this list should help you find it.
User Manuals
End-user documentation for GIS software — the manual a user opens when they need to know how to do something with the application. Written for the actual user role, structured for both linear reading and quick reference lookup, illustrated where it helps the work.
Admin Manuals
Documentation for system administrators, IT staff, and the people responsible for setup, configuration, user permissions, and ongoing maintenance. Separate from end-user documentation because the audience and the level of detail are different.
Quick Guides

Short, focused documents for new users who need to be productive within a few hours rather than learn the whole application. Often a useful companion piece to a full user manual.

Training Materials
Workbooks, exercises, and instructor materials for in-person, online, or self-paced training sessions. Structured around what the trainee will learn to do, not just the features that exist.
Technical Proposals

Full technical proposals, tender responses, and bid documents: from compliance-checking the RFP, through drafting and review, to final submission-ready format. Includes the supporting materials a bid needs: executive summaries, technical sections, win-theme threading, and graphics where text alone is not enough.

Project Presentations

Slide decks and presentation materials for post-bid presentations, project kick-off meetings, milestone reviews, and project closure. Designed to be presented, not read; clear structure, controlled visual density, and writing that a presenter can deliver without reading from the slide.

Project Reports
Status reports, milestone reports, technical progress reports, and the templates a team uses to produce these consistently. Useful when a project will generate the same kind of report repeatedly and the format needs to be set up properly once.
Content Strategy
For teams who need to build out a documentation set from scratch, or audit and reorganize an existing one. What to write, in what order, for which audience, and how to keep it maintained as the software evolves.
Service overview

UI/UX design

01

Start with a call
Most projects start with a short call — usually 30 minutes — to understand what you need, who the audience is, and what already exists. For documentation projects, this is also when I review the software or product if it is available. For bid work, this is when we read the RFP together and identify what the response will need to address.
Modern websites

Web development

02

Written scope, agreed checkpoints
A written scope comes after that call — what is included, what is out of scope, how long it will take, and what it will cost. No surprises later. The work then proceeds with agreed checkpoints rather than a single final reveal, so you can course-correct as the draft takes shape.
Smart planning

Digital strategy

03

Delivery and what comes next
On delivery you receive the final documents in the formats you need — typically editable source files plus exported PDFs — along with any related artifacts the project produced. For projects that will need future updates, I can stay on for revisions or take on the next round of work.
Target Audience

Who this is for

If any of the following describes your situation, this is probably the right service to start a conversation about.
01.

A GIS software company that needs user-facing documentation for a new product or major release.

02.

A team responding to a GIS-related tender or RFP that needs an experienced technical proposal writer.

03.

A system integrator or consulting firm building a custom GIS solution that needs documentation and training materials.

04.

An in-house team whose documentation has grown unevenly over the years and needs auditing or restructuring.

05.

A government client or agency that needs technical writing on a GIS project from someone familiar with public-sector conventions.

06.

A startup or smaller company that needs documentation done properly but does not have a full-time writer on staff.

Have questions? Get in touch!