Contribute a guide

Member guides sit in the library next to ours, with your name on them. If you’ve set up something with AI at work that saves real time, and you can explain it well enough that someone else could do it next week, we’d like to read it.

Start a guide when you’re ready. You’ll need an account, and drafts stay private until you send them for review.

What we publish

• Walkthroughs of work you’ve done: the task, the tools, the steps, and what you still check by hand.
• Writing for employees, founders, and small business owners. Assume the reader is smart and busy and may have never written a line of code.
• Pieces long enough to follow. The editor needs at least 1,500 characters (about 250 words), and most good guides run a lot longer.

We don’t publish announcements, product pitches, lists of tools without a workflow behind them, or anything that exists mainly to link somewhere.

How to write it

Write the way you’d explain it to a colleague across the table. Use contractions, short paragraphs, and examples from the actual work, like the gate code the bot kept forgetting or the Monday report you used to copy out of three systems.

• Name the tools you used. Grok Bot, Claude, ChatGPT, and others all show up in our guides, often together. Say what each one did well on your work, and skip rankings and takedowns.
• Leave out prices, percentages, and before-and-after numbers unless you measured them yourself and say how. Don’t invent results.
• If a story combines several real ones, say it’s a composite. If you build, sell, or get paid to promote something you mention, say that too.
• Use ## headings for the main steps, and end with the next thing the reader should do.
• Keep customer data, names, and anything confidential out of it, including screenshots. Images aren’t supported yet.

AI tools can help you draft. You’re still the author, and you’re responsible for every claim in the piece.

How review works

1. You send the guide for review. Editing pauses while it’s in the queue.
2. An editor reads it and either publishes it, asks for changes with a note, or explains why it isn’t a fit. You’ll see the reply on the guide’s page in your account.
3. Editors may tighten wording, fix formatting, adjust the title, and pick the section and related guides before publishing.
4. Once it’s live, it shows up in the guides list and on its topic pages with a link to your profile.

You can have 2 guides in review at a time. You can withdraw a guide whenever you like, including after it’s published.

Contributor agreement

Version 2026-10-01, effective October 1, 2026. When you send a guide for review, you agree to the following.

1. You wrote the guide, or you have the right to publish everything in it, and it doesn’t include anyone’s confidential or personal information.
2. You keep ownership of your guide and can publish it elsewhere.
3. You give ArcasyaAI, which runs OperateAgentic, a non-exclusive, worldwide, royalty-free license to edit, format, publish, and share the guide on OperateAgentic, including in excerpts, feeds, and links to it, for as long as it’s on the site.
4. Editors may change the guide before or after publishing to keep it accurate and in line with our guidelines, and may decline or unpublish it.
5. You can withdraw the guide at any time, and we’ll take it off the site. Copies that search engines or other sites made before then are outside our control.
6. Contributions are unpaid, and publishing a guide doesn’t make you an employee, partner, or representative of ArcasyaAI.

The terms of use and privacy page apply too. If we change this agreement, we’ll update the version and ask you to accept it again the next time you send a guide.