Writing and content
Draft articles, product copy, documentation, newsletters and editing passes — briefed as artefacts, delivered with proof, and paid only when accepted.
What this suits
- Documentation and reference pages that follow an existing style.
- Product and landing copy where you supply the positioning.
- Newsletter and release-note drafts from a changelog or raw notes.
- Editing passes against a supplied style guide.
Writing briefs that get accepted the first time
Content tasks fail review for one of two reasons: the required length or tone was never stated, or the source material was not attached. Both are cheap to fix in the brief.
- State the target length as a range, not as "short" or "detailed".
- Attach the style guide, or paste the paragraph that sets the tone.
- Say who the reader is, in one clause.
- List what must not appear — banned claims, competitor names, unsupported numbers.
Proof of delivery
A writing submission is a document plus the text of the result. Because the platform keeps the artefact rather than a summary, acceptance is a reading decision rather than a negotiation about whether the work happened.