Why Write for Us?

Amosii reaches 250,000+ monthly readers hungry for honest tech insights. When you write for us:
✅ Reach builders, not bystanders: Our audience is engineers, founders, and productivity nerds.
✅ Boost your authority: Link to your project/product (if genuinely useful).
✅ No fluff, just impact: We reject 70% of pitches. Yours should sting with insight.

What We Want

Pitch topics that make us lean forward:

The Brutally Specific Version)

We seek actionable, evidence-packed stories that make engineers lean in and hype merchants sweat. If your piece doesn’t expose a truth or transform workflows, it’s not for us.

🔬 1. “Tested-Not-Hyped” Autopsies

What: Forensic breakdowns of tools you’ve stress-tested in real projects.
Examples:

“We Migrated 10K Users to Slack Alternatives: Here’s What Actually Worked (and Burned)”
“Figma’s New AI Feature Test: 47 Design Tasks Timed, 3 Failed Spectacularly”
Require:

  • Data logs (e.g., time savings, error rates, cost comparisons)
  • Screenshots/videos of tests in action
  • Failure chronicles (What broke? Why?)

⚡ 2. Workflow Grenades

What: Tactical blueprints that obliterate inefficiency.
Examples:

*“How We Cut Daily Standups to 4 Minutes Using ChatGPT + Notion”*
*“The 57-Second Zapier Hack That Automated $8K/Mo Client Onboarding”*
Require:

  • Step-by-step scripts (e.g., exact prompts, settings, code snippets)
  • Before/after metrics (e.g., “Saved 23 hrs/week,” “Reduced errors by 81%”)
  • Tool stack diagrams (how pieces connect)

🤖 3. AI Tool Dissections

What: Surgical analysis of AI tools beyond marketing fluff.
Examples:

“Midjourney’s Hidden ‘Style Vault’: How Top Artists Bypass Paywalls”
*“ChatGPT API vs. Fine-Tuning: Cost Breakdown for Scaling to 1M Requests”*
Require:

  • Comparative testing (e.g., 5 tools benchmarked on 10 tasks)
  • Token-level cost audits (show your math)
  • Real output samples (great vs. garbage)

🚨 4. Hype-Busting Exposés

What: Investigations that debunk overpromised tools.
Examples:

“Viral ‘SEO AI’ Tool Tested: 97% of Output Was Plagiarized or Gibberish”
*“Why ‘No-Code’ Platforms Secretly Require 200 Hours of Dev Work”*
Require:

  • Smoking-gun evidence (e.g., leaked performance reports, API failures)
  • Vendor contradictions (their claims vs. your tests)
  • Ethical implications (privacy risks, hidden costs)

🚫 What We Instantly Reject

  • “Ultimate Lists” without personal testing of every tool.
  • Theoretical musings (e.g., “How Blockchain Might Change SaaS” → unless you built it).
  • Stealth product pitches (e.g., “Why My Tool Solves Everything”).
  • Reheated takes (e.g., “ChatGPT Tips You Haven’t Seen” → unless you prove novelty).

Hard Requirements

  1. Originality: Never published elsewhere. We check.
  2. Evidence: Back claims with screenshots, data, or code snippets.
  3. Depth: 1,500+ words. Surprise us.
  4. Voice: Write like a human. No jargon monologues.
  5. Visuals: Include charts, GIFs, or custom diagrams.

Submission Rules

Step 1: Pitch First
→ Email pitches@amosii.com with:

  • Working title (e.g., “Figma Killed My Design Team—Here’s How We Survived”)
  • 3 key takeaways (bullet points)
  • Why only you can write this (your creds)
  • Sample paragraph (show your voice)

Step 2: If approved, you’ll get:

  • Deadline (usually 2 weeks)
  • Style guide (fonts, tone, formatting)
  • Feedback within 48 hrs of draft

Step 3: We publish → You share widely.

What You Get

  • 💬 Byline + Bio: Link to your site/LinkedIn.
  • 🔗 Eternal Backlink: From a DR 52 site.
  • ✨ No Editing Without Consent: We suggest; you approve.

Legal Bits

  • You own your ideas. We own the published piece.
  • We fact-check ruthlessly. Prepare for edits.

Pitch Checklist

Before hitting “send,” ask:
☑️ Does this solve a real pain point?
☑️ Would I pay to read this?
☑️ Did I test/work with these tools firsthand?
☑️ Does it align with “Tested-Not-Hyped”?

“Good writing is true writing.” — Hemingway (if he debugged code)

Ready to write hard and clear?
→ info@amosii.com