<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Skobarev</title><description>Building micro-SaaS in public.</description><link>https://skobarev.com/</link><item><title>Twelve platforms, three hours</title><link>https://skobarev.com/blog/autoposter-scope/</link><guid isPermaLink="true">https://skobarev.com/blog/autoposter-scope/</guid><description>I was about to spend ten days automating posts to twelve platforms.</description><pubDate>Wed, 16 Sep 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;I was about to spend ten days automating posts to twelve platforms.&lt;/p&gt;
&lt;p&gt;The estimate was honest. LinkedIn needs manual re-authorization every 60 days:
refresh tokens go only to approved partners. X rotates its refresh token, so if
you don’t persist the new one on every refresh, everything silently stops.
Bluesky wants link offsets in UTF-8 bytes rather than characters, which is its
own kind of fun once Cyrillic enters the picture.&lt;/p&gt;
&lt;p&gt;Seven to ten days of work before I’d trust it on a cron job.&lt;/p&gt;
&lt;p&gt;Those are ten days I’d have nothing to post about. The tool for making content
would eat the time I had for content.&lt;/p&gt;
&lt;p&gt;So I built the boring version instead: a skill that splits one draft into
per-platform files. Three hours. I post them by hand.&lt;/p&gt;
&lt;p&gt;In two weeks I’ll look at where I actually posted, and automate only those.
My guess is that three of the twelve survive.&lt;/p&gt;
</content:encoded></item><item><title>Twelve products in a year: how I kill ideas</title><link>https://skobarev.com/blog/twelve-products/</link><guid isPermaLink="true">https://skobarev.com/blog/twelve-products/</guid><description>I have evenings and weekends for this challenge: ten to twelve hours a week. Over a year that is about 550 hours. Split across twelve products, each one gets…</description><pubDate>Wed, 16 Sep 2026 00:00:00 GMT</pubDate><content:encoded>&lt;p&gt;I have evenings and weekends for this challenge: ten to twelve hours a week.
Over a year that is about 550 hours. Split across twelve products, each one gets
under fifty hours, and that includes the idea, the build, the landing page and
whatever attempt I make at telling people it exists.&lt;/p&gt;
&lt;h2 id=&quot;where-the-number-comes-from&quot;&gt;Where the number comes from&lt;/h2&gt;
&lt;p&gt;I am Alexander. I have been writing backends in Python and C# for over ten
years, all of it employed. I tried freelancing and it did not stick: the same
work for a client, except now there are several of them and they pay less.&lt;/p&gt;
&lt;p&gt;I wanted something of my own. You cannot guess demand in advance, you can only
test it. Spending a year on one idea and being wrong costs a year.&lt;/p&gt;
&lt;p&gt;While reading about micro-SaaS I came across Pieter Levels, who set himself
twelve startups in twelve months back in 2014. Launching has got an order of
magnitude cheaper since, and with AI on hand the number looks reachable. I like
challenges, so I am in.&lt;/p&gt;
&lt;p&gt;To be upfront: I have never launched a product and I have no ad budget. I plan
to talk about the products on social platforms and niche communities. I am
keeping my job. This site is the log: what I built, what broke, what the
numbers were.&lt;/p&gt;
&lt;h2 id=&quot;hard-filters-one-no-and-the-idea-is-out&quot;&gt;Hard filters: one “no” and the idea is out&lt;/h2&gt;
&lt;p&gt;Binary questions. They cut ideas that do not fit “one person, fifty hours,
zero ad spend”.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;1. The MVP fits in 50 hours.&lt;/strong&gt; Three screens and one button, and that is
enough for someone to pay. If the first version needs a month, the idea is fine
but not for this challenge.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;2. Useful to the first user on day one.&lt;/strong&gt; He arrives alone, with no
accumulated content and no community around the product. So anything two-sided
drops out here: marketplaces, job boards, “find a specialist” services. You
cannot launch those alone and unfunded.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;3. The audience already pays for tools.&lt;/strong&gt; Right now, to someone, for something
similar: small businesses, freelancers, agencies, developers with a company
card. An audience with no habit of paying will not acquire one for my product.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;4. There is a place where the audience is already gathered.&lt;/strong&gt; A subreddit, a
chat, a forum, something with a name. Without an ad budget, distribution means
going where people already sit. If no such place exists, there is nobody to show
the product to.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;5. No one else’s money and no one else’s documents.&lt;/strong&gt; Payments inside the
product, healthcare, passports, HR records: compliance and support eat more time
than the product itself.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;6. Cost per user close to zero.&lt;/strong&gt; No heavy models on my own hardware and no
manual steps inside. Otherwise every free user becomes a line item.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;7. No single external dependency.&lt;/strong&gt; If the whole product is a wrapper around
one API, its owner changes the pricing or the rules whenever they like, or
closes the door altogether.&lt;/p&gt;
&lt;h2 id=&quot;soft-criteria-comparing-the-survivors&quot;&gt;Soft criteria: comparing the survivors&lt;/h2&gt;
&lt;p&gt;When three or four ideas make it through the hard filters, I pick with these.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Explains itself in one sentence.&lt;/strong&gt; If the landing page needs an intro
paragraph, the product is unclear, and I will be explaining it to every user
in person.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;One pain, minimum features.&lt;/strong&gt; The product does one thing. Anything that can
be cut from the first version gets cut.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;I can find ten users myself in a week.&lt;/strong&gt; That means a list of ten actual
people I will message. No list, no build.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;I still care in six months.&lt;/strong&gt; Support outlasts launch. A product that bored
me in week two will not get fixed in month three.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;what-is-deliberately-missing&quot;&gt;What is deliberately missing&lt;/h2&gt;
&lt;p&gt;No “market size”. At my scale the difference between a hundred-million market
and a five-million one means nothing: the first hundred customers come by hand
either way.&lt;/p&gt;
&lt;p&gt;No “no competitors”. Missing competitors usually means missing demand.
Competitors with paying customers confirm that people pay for this.&lt;/p&gt;
&lt;h2 id=&quot;what-is-next&quot;&gt;What is next&lt;/h2&gt;
&lt;p&gt;These seven filters are a hypothesis, not a method. They were written before the
first launch and some of them will turn out to be nonsense. After two or three
products I will come back and rewrite the list, noting which filter actually
caught something and which one let through an idea I should not have taken.&lt;/p&gt;
&lt;p&gt;Next post is about where ideas come from: where I looked, how many each source
produced and how good they were.&lt;/p&gt;
&lt;p&gt;If your list has a filter mine does not, tell me. Right now I am most interested
in what I have missed.&lt;/p&gt;
</content:encoded></item></channel></rss>