Working with us
What engagements look like in practice — how briefs come together, how revisions work, where this approach pays off, and where it does not.
Last reviewed on 2026-05-12.
The shapes engagements usually take
Most engagements fall into one of three shapes. None of them are rigid — they are just useful starting points for scoping.
- One-off project. A specific piece — a landing page, a white paper, an API quickstart, a launch announcement. Briefed, drafted, reviewed, shipped. Useful when the team needs a single piece done well, not an ongoing programme.
- Monthly content programme. A defined cadence of content — usually four to ten pieces a month — built around a topic map and an editorial calendar. Useful when the goal is compounding search traffic, an active blog presence, or thought leadership over time.
- Embedded editorial support. A retainer arrangement where a writer functions like an extension of the in-house team — joining standups, working in shared docs, taking on whatever is in the queue. Useful when an in-house marketer or PM is the bottleneck on content velocity.
What clients often report
These are the patterns we hear most often when an engagement is going well. They are general; specifics are kept private under each engagement's confidentiality terms.
- First drafts arrive closer to "publish-ready" than internal drafts usually do, because the brief is taken seriously and revisions are scoped.
- Internal review cycles shorten over time as the writer learns the team's voice and editorial preferences.
- Search-driven traffic compounds rather than spikes — the value tends to show up several months in, not in the first week.
- Sales and support teams start sending links to articles instead of writing the same explanation in email each time.
Where this approach is a good fit
- You have more to write than the team can keep up with, and the backlog has real opportunity cost.
- You know who your audience is and roughly what you want them to do, even if the messaging is not finished.
- You want a writer who can ask hard questions about the brief, not one who just executes whatever lands in their inbox.
- You can give thoughtful feedback on a draft within a reasonable timeframe.
Where this approach is not the right fit
- The goal is a high volume of pages at the lowest possible cost per word. Other providers compete on that; we do not.
- The team needs guaranteed search positions or specific traffic numbers. Those depend on too many variables for an honest commitment.
- There is no real audience definition yet, and the team is not in a position to develop one. The brief stage will stall.
- Internal review is uncoordinated — five reviewers, no clear final approver, no agreed style guide. Drafts will go around in circles.
How outcomes are measured
The most useful metrics depend on the type of writing, but the categories below show up in almost every engagement.
- For blog and SEO content: organic impressions and clicks, keyword positions, scroll depth and engaged sessions, internal link clicks, assisted conversions.
- For landing pages and copy: conversion rate, bounce rate, A/B test results against the previous version, downstream metrics like activation or qualified-lead rate.
- For technical documentation: support-ticket volume on documented topics, time-to-first-API-call for new developers, qualitative feedback from engineers and product managers.
- For email programmes: open and click rates against benchmarks, unsubscribe rates, downstream behaviour (activation, repeat purchase, retention).
Numbers are useful, but they are downstream of decisions. The real question early in an engagement is whether the underlying decisions — audience, voice, topic priorities, distribution — are getting clearer over time. If they are, the metrics tend to follow.
What clients ask us about up front
A few questions come up in almost every initial conversation, so it is worth surfacing the answers in one place.
- "Do you write with AI?" AI tools are part of research and outlining; finished drafts are written and edited by people. See the About page for more detail.
- "Will you sign an NDA?" Yes. A separate NDA can be put in place before any details are shared.
- "Who owns the content?" On full payment, you do. See the Terms.
- "How fast can you start?" Usually within a week or two of an agreed brief, depending on current capacity. Rush work is possible but priced separately.
- "What if I do not like the first draft?" Revisions are part of every engagement. The goal is to leave room for substantive feedback without scope drifting indefinitely.
If this sounds like the kind of working relationship you are looking for, the next step is a short email. Send the rough scope to [email protected], or use the form on the contact page.
Start a conversation
Whether you have a single project in mind or a content programme to plan, the first email is the same: rough scope, timeline, what success looks like.
Contact us