Field notes. John Arndt, Soxoa. Published .
A founder can spend weeks building something and still have nothing useful to send an editor. The work may be real. The pitch explains only what the product does.
An editor needs a reader consequence: a local decision, a documented pattern, a surprising limitation or a practice worth examining. The product can establish why you know the subject. It does not supply the whole story.
We used this approach in a Sacramento editorial project in September 2026. The completed collection included ten articles, publication-specific pitches, source notes and commercial disclosures. The subjects came from work already underway. Later revisions addressed an editor's comments on a shared draft. Those are concrete deliverables and editorial work. They do not establish that every article was accepted or published.
The reusable skill is the process that connects documented experience to a suitable publication.
Find the consequence outside your company
Start with what happened or what you can demonstrate. Then ask who needs to understand it and what decision it changes.
For an illustrative example, a contractor compares two estimates and finds that they count different scope. A product pitch explains an estimating feature. An editorial story explains why homeowners should compare what was counted before comparing the totals.
The evidence may support a practical article, an opinion piece or a reported story idea. Those formats ask different things of the author. A useful pack names the format instead of handing every editor the same generic announcement.
Commercial interest belongs near the argument. If the author builds estimating software, say so. The disclosure lets readers assess the author's vantage point without pretending the experience is independent research.
Check the publication before writing to its limit
An outlet's audience and current submission guidance shape the work. Record its geographic focus, preferred format, length, submission route, required materials and exclusivity terms. Use the outlet's own guidance when it is available.
These are changing operational details. A past pitch pack can demonstrate the method, but its old email address or word limit should not become a permanent instruction inside a skill. When guidance is inaccessible or conflicting, leave a verification note rather than silently choosing a convenient answer.
The pitch itself should make a few things easy to assess: the proposed story, why readers care, what evidence exists, why this author can contribute and the narrow question being asked of the editor.
A neighborhood publication may need a local person and consequence. A policy publication may need a statewide argument with primary sources. Reusing the evidence does not require reusing the same framing.
Keep the submission record as carefully as the draft
The pack should distinguish a proposed piece, a completed draft, a submitted article and an accepted article. Those states are easy to blur when several versions and outlets are involved.
Exclusivity also needs a real status. Offering the same article exclusively to multiple publications creates a problem a writing assistant should help prevent. A small record of version, target, submission date and current status is enough to make the next action clear.
For requested editor revisions, read the actual comment and current draft. Make the needed correction, preserve citations and verify the resulting text. The practical value is often in that narrow, careful follow-through.
The new Claude skill draft, build-editorial-pitch-pack, packages this workflow. It takes documented work, target readers and publication preferences. It produces tailored pitches, article drafts, source notes and a submission checklist. The earlier editorial pack demonstrates the method. This new Claude package still needs its own trial.
Try:
“Use build-editorial-pitch-pack to find two local editorial angles in this completed project. Verify current official submission rules for the proposed outlets. Draft one full article and tailored pitches, disclose my commercial interest, and keep everything unsent.”
Start with one piece of work you can explain and substantiate. The useful test is whether an editor can understand the story and evaluate its evidence without first sitting through your product demo.
Get the skill
build-editorial-pitch-pack is part of the free Soxoa Ops plugin for Claude. In Claude Code, add the marketplace with /plugin marketplace add johnarndt/soxoa-claude-plugins, then run /plugin install soxoa-ops@soxoa-plugins. You can read the skill on GitHub before installing it, or copy its folder into ~/.claude/skills/.