Ten SEO-ready articles for B2B SaaS devtools companies. Fourteen days. Two thousand dollars flat. If articles one and two miss, full refund — no invoice, no argument.
project slots open for april →
You raised. You announced it. The blog went up for the announcement post and then stopped. That was four months ago.
You know content compounds — that's why it's been on the roadmap since day one. But your engineers are shipping product. Your marketer is running campaigns. Nobody is writing.
Agencies quote eight thousand a month and want a three-month commitment before they'll look at your sitemap. Freelancers take six weeks for two articles and still don't understand your product. Neither makes sense when you just need the blog alive again.
That's the gap Arcwrite fills. Not a retainer. Not a relationship. A project: ten articles, fourteen days, done.
You see real output before the week is out. All ten delivered by day fourteen. No drip-feed, no 'we're still in the strategy phase.'
If the first two articles don't clear your bar, the project stops and every dollar comes back. No forms. No negotiation. The work speaks or it doesn't.
One intake form. One shared Google Drive folder. Review whenever you have time. You'll forget Arcwrite exists until the articles land in your inbox.
$ arcwrite --exclude
✗no retainers
✗no strategy decks
✗no kickoff calls
✗no weekly standups
✗no content calendars
✗no "let's circle back"
✗no enterprise sales process
One ten-minute form: your brand voice, target keywords, competitor URLs, topics to avoid. That's the entire brief.
Articles one and two land in your shared folder. Read them whenever. If something's off, leave a comment — no call needed.
All ten articles, formatted for your CMS. Meta descriptions, keyword targets, and internal linking suggestions included. Publish-ready.
all prices in usd. payment via wise or stripe. invoiced on project start.
First project? Start with Starter. Five articles is enough to know if this works.
How a two-person devtools startup can rank on Google without a marketing hire. Covers keyword research, programmatic pages, and link acquisition — with real examples, not theory.
~2,400 words · 8 min readThe Langfuse acquisition changed the LLM observability landscape overnight. An analysis of what it means for Traceloop, Helicone, Arize, and every team running evals in production.
~2,200 words · 7 min readA cost model for engineering teams deciding between building custom incident tooling and paying for Rootly, FireHydrant, or incident.io. Includes a worked spreadsheet you can fork.
~2,600 words · 9 min readOne intake form. Fourteen days. Ten articles that rank. Full refund if the first two don't.