Write for Us
Know something we don't?
Our blog is written by the people who build the things we write about. If that describes you too, we'd like to publish you — here's exactly what we're looking for.
Pitch an articleWhat We Publish
Practical writing for people who ship software
Jaspero is a small software team in Osijek, Croatia. We build AI integrations, custom platforms and internal tools, mostly on Svelte, Angular and Firebase, and we write about the parts of that work that were harder than they looked. Our readers are developers, CTOs and technical founders who are about to make a similar decision.
That's the bar for a guest post too. We're far more interested in one honest account of how a migration went sideways than in a comprehensive overview of a framework. If you've done the work, you already have the article.
Working on something adjacent to these? Pitch it anyway. The list describes what we know, not what we're limited to.
The Criteria
What a submission has to meet
Every post we publish is held to these six things, including the ones we write ourselves.
Written from experience
Something you actually built, broke or fixed. We want the trade-offs you weighed and the decision you regretted, not a summary of the documentation.
1,200 – 2,500 words
Long enough to say something concrete, short enough to stay useful. If the idea needs 900 words, send 900 words rather than padding it.
Specific and technical
Code, configuration, architecture diagrams, real numbers. Claims about performance, cost or reliability should come with the measurement behind them.
Original and exclusive
Not published anywhere else, and it stays that way. You're welcome to link to it, quote from it, or republish an excerpt with a canonical link back.
Sourced
Statistics, benchmarks and quotes need a link to the primary source. If a number comes from your own work, tell us how you measured it.
Written by you
Use AI to research, outline or tighten your prose if it helps. An article generated wholesale by a model reads like one, and we will spot it.
What We Turn Down
Saving us both the time
We read every pitch, so it's only fair to be direct about what gets a no by default. None of this is personal — it just isn't what the blog is for.
- Link-building filler — posts written around an anchor text rather than around an idea.
- Product pitches in disguise, yours or a client’s.
- Content already published on your blog, Medium, dev.to or LinkedIn.
- Round-ups of tools you have not used, and "top 10" listicles.
- Unsourced statistics, invented case studies, or benchmarks that cannot be reproduced.
- Paid placements. We do not sell posts or links, at any price.
- Topics with no overlap with what we build — crypto promotion, gambling, SEO services.
What You Get
Worth your afternoon
A real edit
One of our engineers reads the draft and comes back with technical notes, not just copy edits. Most posts go through one or two rounds.
Your byline and bio
Full credit, a short author bio, and one followed link to your site or project. No ghostwriting, no house byline.
Distribution
We share every post through our LinkedIn and our own channels, and keep it in the blog rotation rather than letting it sink.
An honest answer, quickly
You hear back within five working days — including when the answer is no, and why.
The Process
From pitch to published
Send the pitch
Fill in the form below with your idea and an outline. A good outline is 200–300 words with the headings you plan to write under.
We reply within 5 working days
Either with a yes and an agreed angle, notes to sharpen the pitch, or a clear no. We will tell you if we already have something similar in the pipeline.
You write the draft
Two to three weeks is typical. Send it as a Google Doc or Markdown, with code in fenced blocks and images as separate files.
We edit together
We send comments, you respond. Nothing gets published without your sign-off on the final version.
It goes live
We handle formatting, images and SEO, publish it under your name, and send you the link before it hits our channels.
Pitch an Article
Tell us what you want to write
Pitch the idea before you write the article — it saves you writing something we've already got covered. One pitch per submission, please.
You'll hear back within five working days. If you'd rather email, we're at info@jaspero.co.
FAQ
The questions we always get
Do you pay for guest posts?
Not at the moment. What you get is a genuine technical edit, your byline, a followed link and distribution to our audience. If we ever commission a piece specifically, we will agree a fee up front.
Can I include a link to my product?
Yes, where it is relevant to the point you are making, plus one link in your author bio. What we will not run is an article whose structure exists to justify the link.
Can I republish it on my own blog?
After 30 days, yes — as long as the canonical URL points back to the version on jaspero.co. You can also post an excerpt with a link at any time.
How technical should it be?
Assume the reader is a developer, CTO or technical founder. You do not need to explain what an API is, but do explain anything specific to your stack or domain.
What if I have an idea but no outline yet?
Send the idea anyway and say so in the outline field. If it is a good fit we will help you shape it before you write anything.
Not sure it's a fit?
Read a few of the posts we've published recently. If yours would sit comfortably next to them, send it over.
Read the Blog