BlogMaker

Add a hosted blog to an existing website and maintain a focused publishing workflow.

Hosted publishing software + annual subscriptionsPublishing
Visit website
Reported revenue≥ $10,000ARR · Unspecified $Five-figure ARR stated in the January 22, 2026 founder interview. Stored 10,000 is only the lower bound of that five-figure range, not an exact amount; accounting cutoff unstated.Original disclosure
Business modelHosted publishing software + annual subscriptionsPublishing
Profile depthResearched profileProduct facts and editorial breakdown
Source checkedOct 20, 2026Observation date, not revenue cutoff

Business overview

Public positioning

Add a hosted blog to an existing website and maintain a focused publishing workflow. Val Sopi explicitly says he operates solo in the January 22, 2026 first-person interview. This supports a dated solo operating stage; present employee and contractor counts were not independently audited.

How it makes money

Annual plans differentiated by blog count, publishing tools and automation access.

Business breakdown

Researched Oct 20, 2026

Source-linked product facts, followed by MRRTrace analysis of the customer problem, workflow, trade-offs and questions to test.

The customer problem

The official product offers a hosted blog that can accompany an existing website. Editorial interpretation: the buyer may want a dependable publishing routine without making a full site migration the prerequisite. Observe how an actual customer prepares, approves and publishes one post, including who owns the domain and who can change hosting settings. A good first release might solve one recurring publishing obstacle rather than reproduce a complete content management system. Test whether the customer can complete a second post with less assistance before expanding the feature set.

Core workflow

  1. Choose a blog plan and decide how its public address fits the existing website and hosting setup.
  2. Prepare a post, inspect its preview and review content, links and metadata before publication.
  3. Publish, check the public page and any changed URLs, then use reader feedback and actual workflow friction to plan the next post.

What customers pay for

Editorial analysis: measure completed publishing sessions and the ongoing effort needed to maintain the customer setup. Keep search impressions and sales outcomes separate from successful publication because they depend on content, competition and distribution as well as tooling. An annual subscription collects cash on one schedule while support and infrastructure obligations continue throughout the year. Track renewal decisions and support effort for each plan before copying a low annual price. A useful experiment compares a narrow onboarding service against additional editor features using real time-to-publication and subsequent repeat use.

Distribution signals

Observed channels and entry points; their performance is not inferred.

  • Search-oriented content and product partnerships

    The January founder account describes search-focused publishing and a RightBlogger integration while acknowledging that dependable acquisition remains challenging. These are reported channel choices, not a controlled comparison or proof that the same articles or integration will produce equivalent revenue elsewhere.

    Evidence

Trade-offs

  • Editorial risk: fitting into an existing website reduces the scope of replacement but can make initial setup depend on another host and its operator. Test the supported connection path and recovery steps before promising a quick migration.
  • Editorial risk: inexpensive annual plans can make an initial purchase easy while creating a long service obligation from a small receipt. Measure renewal and support patterns rather than inferring sustainable economics from the advertised price.

Open questions

  • Which recurring publishing task makes a customer renew after the initial setup is complete?
  • What domain, migration or collaboration problem consumes the most support time per paying account?

A MRRTrace reading of public product material. Trade-offs and questions are editorial analysis.

Revenue evidence

Founder disclosure
≥ $10,000ARR · Unspecified $ · Five-figure ARR stated in the January 22, 2026 founder interview. Stored 10,000 is only the lower bound of that five-figure range, not an exact amount; accounting cutoff unstated.
Reporting period
Five-figure ARR stated in the January 22, 2026 founder interview. Stored 10,000 is only the lower bound of that five-figure range, not an exact amount; accounting cutoff unstated.
Figure as of
Not provided
Reporting method
Founder disclosure
Source checked
Oct 20, 2026
Source published
Jan 22, 2026

The first-person answer gives only five-figure ARR. Display a >=10,000 lower bound and retain the range wording; do not substitute the editorial >5K/month header, derive an MRR figure, or treat the future five-figure MRR goal as achieved. Current annual USD pricing does not establish the historical bare-dollar reporting currency. This unaudited historical run-rate disclosure is not current revenue or profit.

January 2026 original founder five-figure ARR statement
This historical disclosure is separate from any current Stripe connection shown on this page. MRRTrace has not audited the business. Revenue is not profit, and historical figures are not current earnings guarantees.

Current official annual plans: Starter USD 19/year, Expert USD 49/year and Advanced USD 99/year, renewing yearly. These current prices are separate from the January interview pricing history.

The source page may change its prices, limits, or offer after the recorded check date.

What founders can learn

Editorial notes

Study whether a focused hosted blog can reduce setup and recurring publishing work without rebuilding a customer entire website.

Before you build something similar

  • The disclosed ARR is a broad five-figure range; the stored threshold is deliberately not an exact revenue estimate.
  • Hosting and search features do not establish ranking improvements or customer sales outcomes.
  • Import scope, reverse-proxy support and redirects require planning; the product website does not prove a migration has succeeded.

These are MRRTrace observations, not statements by the founder or proof of a repeatable outcome.

Source material

4 sources
  1. January 2026 original founder interview Public source · Checked Oct 20, 2026
  2. Official product and publishing workflow Public source · Checked Oct 20, 2026
  3. Official current annual USD plans Public source · Checked Oct 20, 2026
  4. Official product and founder background Public source · Checked Oct 20, 2026