Most pitches I receive for “technology write for us” posts get instantly rejected within the first thirty seconds. Writers have actual writing skills, so that is not the reason. The actual issue is that they treat Techisane as a link drop, and don’t treat us as a publication with actual readers.
I single handedly manage and run this site, and I personally edit all of the submissions. I reject about four out of five submissions that I receive everyday. This page is here to save you the trouble of why I reject your submission, and not the trouble of wasting your time.
TL;DR. Techisane is open to original, and unpublished submissions, that are tech articles at a doctor, editor, or clinician level that cover the areas of AI, Cybersecurity, Enterprise Tech, IT Infrastructure, and Software. AI generated filler write ups that are a waste of time to submit will also be rejected. Having a high domain authority on your own site will not get you accepted. Submissions that take time to review and have depth and accuracy to address the core issues will be considered.
Who I Am and Why This Page Exists
As someone who has spent 8 years working in the fields of technology having an understanding of this field helps to ensure that a bad infrastructure decision does cost a company a time extensive process, and help to solve after breaches that started with an unpatched VPN appliance.
Techisane is my platform to talk about that work, and the reality of it. When I opened the doors to outside contributors, the flood began. That is why I set the standards page. This is a must read for contributors.
Common Interpretation of "Technology Write For Us"
Most people who see "technology write for us" think it is a write-only opportunity with no other purpose other than posting a backlink in the article. I, however, think of it as an opportunity for people who have gone through a technology-related issue and have the ability to detail this issue in the form of a narrative for an intelligent individual who is in a position to influence the outcome of the issue.
Hence, a guest post for Techisane involves much more than a summary article of a technology-related issue. It has to provide a solution or answer to a issue or challenge that an individual can't readily find in Google.
Subjects Accepted
I have a specific focus area and I would prefer if all contributing authors were equally as focused. I write about the following issues:
- The practical sides of using Artificial Intelligence such as how to effectively integrate a Large Language Model into an existing workflow, as well as the challenges of cost and efficiency of using AI.
- Understanding specific cyber threats and attacks such as Ransomware, Phishing, and the Supply Chain attack, as well as the tools to defend against or mitigate these threats.
- The challenges of using business technology platforms, for example, a platform’s Enterprise Resource Planning (ERP) system and the gaps between what a platform claims to do and what it actually can do at its fullest capacity and what a platform may purposely hide.
- Understanding the costs and trade-offs between having an IT system in the Cloud versus one that is on-premises versus on the internet, and having true recovery plans in place for disruptions.
- The evaluation of different tools to enhance software development and using software that has been compared and evaluated to have a specific worthwhile feature.
If your pitch sits outside these five, I'll decline it regardless of quality. A brilliant piece on crypto trading or gadget unboxings has no home here.
Here are the submission requirements
- Word count: 1,800 to 2,000 words.
- Original and Unpublished: We will not accept a version of an article that exists anywhere else, not even on your own blog.
- No AI or Filler: Wasting space will make your article dead on arrival.
- Be Specific: We require a data point or a specific occurrence to support each claim you make.
- Author Bio: Include a 50 to 80 word author bio. We want to see a legitimate source for your credentials.
- No Duplicate Content: Do not restate the same point in different ways to fill space.
- Link Spam Policy: The article cannot be solely for the purpose of an anchor link.
Google's own spam policy is clear that content created mainly to manipulate rankings, including guest posts with optimized anchor links, counts as link spam. I qualify outbound author links accordingly. If a backlink is your only goal, this isn't the right place.
Accepted vs. Rejected Content: A Side-by-Side
The difference between what I publish and what I bin usually comes down to intent and depth. Here's the honest breakdown.
What Gets Accepted vs. What Gets Rejected at Techisane
Factor | Accepted | Rejected |
|---|---|---|
Angle | Specific problem with a clear point of view | Generic "ultimate guide" overview |
Evidence | Cited stats, tested benchmarks, real incidents | Unsupported claims, invented anecdotes |
Depth | Explains tradeoffs and failure modes | Lists features without saying which matters |
Originality | Unpublished, first-person expertise | Rewritten or AI-spun from ranking articles |
Links | One relevant, qualified author link | Multiple keyword-stuffed commercial links |
Voice | Practitioner explaining to a smart reader | Marketing copy dressed as an article |
What most submitters get wrong
The domain authority of your site will not influence our decision to accept your article.
It's always the same from the agencies. "We will publish from a DA 60 profile." Quite frankly, I do not care. DA stands for Domain Authority, a third-party metric that does not correlate to whether your writing will actually help my readers. I have rejected pitches from Digital Referrals with a 70 score and have accepted pitches from those with no domain at all, simply because the first-timer actually had experience in running the infrastructure that they were writing about.
Google demoted the guest posting for authority scheme a long time ago and site reputation abuse policies target exactly the "borrow someone else's ranking" play. What remains is the writing that captures readers and the content that is finished and shared. For that reason, I have a greater respect for your demonstrated expertise, rather than any authority score you provide.
Where Pitches Fail
Having received a large number of pitches, I have become sensitive to the ways in which a pitch tends to fail. The majority of rejections are a result of one of the following.The pitch is a topic, not an angle
Pitches that simply state "I will write about AI in business" provide no value. Every basic article will address that. A pitch that provides an angle will identify a specific issue. For example, "why most retrieval-augmented generation systems fail at document chunking and what retrieval settings no one checks." When a pitch is specific, it conveys that research has been conducted.
The draft summarizes, not instructs
A substantial number of submissions have that glossy, finished look, but do not provide any information that a reader would not find as their first search result. They stop at stating definitions and benefits. Experience with production is often conveyed through explanations of tradeoffs and caveats. If a draft does not include the phrase "this breaks when," it likely is not finished.
The links reveal the game
You've spammed commercial links in your draft's unrelated sentences. We instantly decline drafts with this link spam.
The word count is artificially inflated
We are able to identify the instances when an author submits 1,200 words of substance that has been distorted to 2,000 words, with unnecessary repetitions, restated introductions, and distracting transitions. Writing that is concise at 1,800 words is always better than writing that is bloated at 2,000 words.
It is obvious that an AI wrote the draft
AI drafts have a distinct texture: even lengths, no specificity, no stakes, hedging. There's a place for AI in a writing process, but I draw the line when no human effort is applied to the AI-generated final product.
What a successful pitch looks like
You do not need to give a long email. Send me your:
- Working title with a unique angle
- One core argument paragraph.
- Your credentials in this field (one sentence).
- The one data point (or example).
If I see strong points with the above, I'll request your draft. Weak points mean no draft will improve the pitch.
My Honest Advice Before You Submit
Here's what I'd actually do if I were pitching a technology blog cold, based on both sides of the inbox.
Pick the narrowest topic you have real authority on. Not "cybersecurity trends" but "what actually happens in the first hour of a ransomware incident, from someone who's run the response." Narrow and deep beats broad and shallow on every submission I've reviewed.
Then write what you needed to see when you were answering this question. Mention the number you had to scrape to find. Identify the failed tool and recognize the successful one. State what you got wrong the first time. This particular piece of information, that minutiae, the piece that all the generic articles fail to include, means the difference between a submission that gets published, and one that gets rejected.
Also, before you pitch, read 3 of the published articles on the target site. It takes 10 minutes and avoids the most common error: accidentally proposing an article that already exists or is a terrible fit.
How to Submit
Pitches must be sent to our email Id mentioned on the contact page. Use the subject line "Technology Guest Post - [Your Angle]." I read all the submissions personally. You will receive a response in under a week. I will give a one sentence explanation if I decline, to help you with your future attempts.If you have valid technology expertise, I want to hear from you. Start with the angle, lead with the evidence, and skip the link request.
Frequently Asked Questions
For a guest post, do I receive a backlink?
You receive a single qualified author link in your bio. In terms of Google's outbound link policy, Techisane is not a commercial backlink farm. The submission will not pass review if authorial intent is to manipulate search rankings. This is what Google’s link spam policy is in place for.
What is the ideal length of a guest post?
On Techisane, the ideal length is 1,800 to 2,000 words. This length covers trade-offs and failure modes without excessive padding. Submissions shorter than this range tend to summarize the content instead of teaching it, while submissions longer than this range tend to be repetitive.
Does you allow for the submission of AI-generated content?
You are allowed to draft content using AI, but submissions that are purely AI-spun will be rejected. I look for specific data, real examples, named tools, and a point of view that no model generates. Utilize your expertise, or do not submit.