- Write for us tech: same door, same guidelines
- 60-second technology guest post check
- What We're Looking For
- What We Don't Accept
- What You Get
- How to Submit
- Technology guest post topics: accepted or declined
- Write for us technology guest post: how to pitch
- What a strong technology pitch looks like
- Technology blog guest post guidelines
- Technology coverage on this site: what's done and what's still open
- Frequently asked questions
Yes, technology guest posts are accepted on this blog. Its readers are business owners, marketers and agencies who choose and live with technology every week, not enterprise IT departments. The accepted pieces carry specifics: the tool or system you picked, what it changed, what broke, and what you would do differently. Generic tech trend pieces get declined. Pitch a real technology decision with the outcome still attached.
Most technology writing describes what a tool could do. The posts that run here describe what it did once a real business switched it on. If you have chosen, switched or fixed technology inside a real business, our readers want the version with the outcome still attached.
I am Lilach Bullock. This blog reaches business owners, marketers and agencies who make technology decisions with real money and real teams behind them. They care about what a tool changed, what it broke, and what it took to make it work.
Write for us tech: same door, same guidelines
Write for us tech and write for us technology are the same door, with the same rules. Tech here covers the software choices, migrations, security lessons and automation listed under What We're Looking For. It's written for the business owner, not the IT department. The five-point check below is the quickest test of a pitch, and the table further down shows where common tech ideas land.
60-second technology guest post check
A strong submission can answer yes to all five points:
- The writer has directly chosen, built, switched, or fixed the technology being described.
- The pitch includes a specific result, number, test, failure, or lesson that cannot be copied from another article.
- The reader is a founder, business owner, marketer, or agency making a real technology decision.
- The article teaches before it promotes and is not vendor copy wearing an editorial byline.
- The writer has read the full contributor guidelines before submitting.
What We're Looking For
Content that helps a business owner make a decision they will not regret:
- A technology or software choice, with what happened after you made it
- A migration or switch, including what broke on the way
- Security or data protection lessons learned the hard way
- Automation and integration that moved a real number
- Technology for small teams that punched above its weight
- The tech decision you regret, and why
- Making old systems and new tools work together
If your post could be published by any vendor with the logo swapped, it is not for us.
Also accepting guest posts on SaaS, technology and AI.
What We Don't Accept
- Vendor marketing with a byline on it
- Content published elsewhere
- Trend pieces with no first-hand experience behind them
- Tool round-ups with no real testing
- Anything written purely for a link, with no value to the reader
One decline reason catches regret and migration pieces in particular: the contributor guidelines rule out anything inaccurate or directly critical of companies or individuals. Write about your decision and what you'd check next time, not about the vendor you left: "We picked a tool before we listed the integrations we needed" teaches something, "Vendor X is useless" doesn't.
What You Get
- Exposure to an engaged audience of business owners and marketers
- A quality backlink from an established domain
- Author bio with a link back to your website
- Social media promotion across our channels
How to Submit
All guest post submissions go through the main submission page. Please read the full guidelines first:
If you would like to reach a broader marketing audience, you can also write for us, or see the full list of blogs that accept guest posts.
Technology guest post topics: accepted or declined
If you're not sure where your idea sits, this is how I sort the tech pitches I get.
| Pitch type | Accepted? | Why |
|---|---|---|
| A software switch, with what broke and what improved | Yes | First-hand decision with the outcome attached |
| A security scare and what you changed after it | Yes | A lesson learned the hard way |
| An integration or automation that moved a real number | Yes | Gives the reader a result to test |
| The tech decision you regret | Yes | Honest failure helps readers avoid it |
| Top technology trends for business | No | No first-hand experience behind it |
| Tool round-up with no real testing | No | Nothing a reader can trust |
| Vendor marketing with a byline | No | Reads like a sales page |
Write for us technology guest post: how to pitch
A technology guest post here is one article about one technology decision inside a business, written by the person who made it. Use the table above to place your idea. The first four rows are the ones I accept. The bottom three rows are the ones I decline.
Got an idea that sits in no row? Pitch the decision behind it and the outcome attached, not the trend around it.
How a borderline tech pitch gets decided
When an idea sits between rows, three checks settle it:
- Tech, SaaS and AI each have their own guidelines page, and if your subject sits between two, pick the one closest to your reader, not your product. Writing for the reader is what gets a pitch read.
- The guidelines decline any subject already covered extensively on the blog, so check the coverage list further down first. A narrower angle on a covered topic can still work, as long as it answers a question the existing piece doesn't.
- Any quotes or photographs you use must be correctly attributed. If the post leans on a rule, standard or regulation, I'd want to see the public source named too, so a reader can check it for themselves.
What a strong technology pitch looks like
The pitches that get accepted here come from people who have made the decision, not people summarising what others have written about it.
A weak pitch says "I would like to write about the top technology trends for business." A strong one says "We moved our whole team off one project tool to another over a weekend. Two integrations broke, one workflow got faster, and here is the checklist I wish we had used first." One is a brochure. The other is worth reading.
Worked example (an illustration of the shape, not a published post): a six-person agency moves from one project tool to another between Friday evening and Monday morning. They export around 400 open tasks, archive the finished ones instead of moving them, and rebuild 12 recurring templates by hand. Monday shows what broke: the Slack channel that posted task updates goes quiet because the old integration was never reconnected, and Google Drive attachments arrive as links nobody outside the original owner can open. The fix takes an afternoon: reconnect Slack per project, change the Drive sharing settings, then re-test with one task each. The post built from that weekend is the checklist, in order: list every integration before you export, move only live work, test one task through each connection before the team logs in.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
The angles that get accepted fastest
- A software switch, with what broke and what improved
- A security scare and what you changed after it
- An integration that saved real time
- Technology that failed to deliver, honestly
- The setup a small team really runs on
Before you pitch, check you can answer each of these in a line or two:
- Your first line: the decision and its outcome in one sentence, such as "We moved six people to a new project tool over a weekend and two integrations broke."
- The topic, in the words a business owner would search for.
- Which problem does the post solve, and which single decision sits at its centre?
- Your role: did you choose it, build it, switch it or fix it?
- Anything that broke or underdelivered, plus what you changed.
- A reader takeaway they can act on the same week.
- One idea only. Two half-ideas in one pitch read as neither.
Before you pitch anywhere, it is worth checking the site with the free backlink checker, and the write for us finder will surface more sites in the same niche.
Technology blog guest post guidelines
If you write about technology in business and want a guest post here, these are the guidelines. Pitch a topic a business owner would search for, not a product announcement. The article needs to be 1,200 words or more, written for the owner rather than the developer, with a clear answer in the first paragraph and real steps or examples underneath. Links to your own tool are fine where they help the reader, and every link is do-follow. I edit for clarity and cut anything that reads like a sales page. Sponsored placements are handled through the write for me page, where you can also ask about product placement in a listicle.
For all guest post guidelines in one place, start at the write for us guidelines hub.
If your pitch crosses into design, see these web design blogs that accept guest posts. My lists of quality guest post sites and Australian guest posting sites cover more places to pitch.
Technology coverage on this site: what's done and what's still open
Before you pitch a technology piece, check it isn't already here. The site leans towards practical guides for business owners and everyday users, and these topics already have a home:
- Business owners have a plain piece on common technology adoption mistakes, including how AI assistants get rolled out badly.
- There's a step by step guide to connecting a Galaxy with DeX for a monitor, TV or PC.
- Developers and curious owners can read about Google Antigravity's app and CLI.
- Security readers have Project Glasswing explained, including who's in and the access routes.
- Site owners can check which AI crawlers to block and which to allow.
- Phone users have a guide to hiding apps with Private Space on Android.
What's still open is the business side of technology, especially security and risk. NIST gives a useful steer here: version 2.0 of its Cybersecurity Framework added emphasis on governance and on supply chains, along with quick-start guides for specific audiences. Small firms read that and want to know what it means for them on an ordinary Tuesday. The same NIST page says the framework now reaches beyond critical infrastructure to organisations in any sector, and lists quick-start guides for small businesses among its new resources. So tie your small-firm security story to one named part of it, such as who owns the security decision or which supplier is the risk, and cite NIST or the regulator directly, with the date of the guidance, rather than a vendor's summary. These angles aren't covered yet:
- Technical debt explained for non-engineers: what it is, how it shows up as missed deadlines and slow releases, and the questions an owner should ask their developers.
- Zero trust in plain English for a ten-person company: the few changes that matter at that size, and the ones that are overkill.
- An incident response plan for a small team covering the first 24 hours: who calls whom, what gets switched off and what gets written down.
- What a data breach notification rule asks of you, with the timeline and the people you have to tell, sourced to the regulator you're writing about.
- Digital twins outside factories: where the idea works for smaller firms and where it's still a slide deck idea.
As illustrations of the shape these pitches can take (example titles, not posts that already exist):
- Technical debt: the three questions to ask your developer at the next review
- Zero trust for ten people: what we changed and what we skipped
- Our first-24-hours incident checklist, written after a scare
- Which breach notification rules applied to us, and where the regulator says so
- Where a digital twin helped a small workshop, and where it didn't
Pick one, tie it to a decision a business owner has to make, and show the steps. I'd much rather publish a narrow piece that solves one problem than a broad trends round-up.
Frequently asked questions
Do you accept tech guest posts?
Yes. Tech guest posts are welcome from founders, marketers, developers and agency owners who have chosen, built, switched or fixed the technology they write about. I publish tech articles with a real decision and a real outcome attached, and decline trend roundups and vendor copy with a byline on it.
How long should a guest post be?
Long enough to answer the question in full and no longer. In practice that is usually 1,200 to 2,000 words. Depth matters far more than word count.
How long does a decision take?
We aim to come back to you within a few working days. If the pitch is specific and clearly written, that decision is much faster.
Can I include a backlink?
One contextual backlink to your own site or a relevant resource is fine in an editorial post. More than that reads as link-driven rather than reader-driven.
Do you accept information technology and tech business articles?
Yes, as long as they're written for the business owner rather than the developer or the IT department. Software choices, migrations, data protection and the setup a small team runs on all fit. Pure enterprise IT pieces usually don't.
Can I submit a tech guest post about a product I built?
Only if the post teaches first and the lesson stands without your product. The contributor guidelines say a post that only promotes a company won't be accepted as a guest post; if you want the tool itself covered, product placements, reviews and sponsorships are the separate routes for that.
I go much deeper on this in the content marketing guide.

