Dirstarter

A Next.js source-code starter kit for building directory websites.

One-time software license purchasesDeveloper tools
Visit website
Reported revenue≈ $5,000Monthly revenue · Unspecified $Monthly amount reported in the February 5, 2026 founder interview; exact measurement cutoff unstatedOriginal disclosure
Business modelOne-time software license purchasesDeveloper tools
Profile depthResearched profileProduct facts and editorial breakdown
Source checkedOct 20, 2026Observation date, not revenue cutoff

Business overview

Public positioning

A Next.js source-code starter kit for building directory websites. In the March 3, 2026 original Q&A, Piotr describes himself as a solo founder, names both OpenAlternative and Dirstarter, and states that he has no co-founders or employees. This is a dated founder statement; later headcount and contractor use were not independently audited.

How it makes money

One-time software license purchases

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

Dirstarter sells a source-code starting point for directory websites. Its official documentation assumes familiarity with the underlying development tools. Editorial analysis: the customer is buying reduced setup work, not a guaranteed business. Before offering a similar template, observe repeated tasks across several real projects and determine which decisions customers want to control. A template is more useful when its boundaries are clear: the buyer should know what is included, which integrations need configuration, and which operating costs remain outside the purchase. A demonstrable working product can help explain those boundaries.

Core workflow

  1. Review the demo, documentation and license to check whether the starter fits the intended directory and the buyer's technical ability.
  2. Obtain the licensed code, configure the required services and customize the content structure and presentation.
  3. Test essential flows, deploy the directory and maintain its code, listings and operating services.

What customers pay for

The original interview separates monthly receipts from one-time Dirstarter purchases from the recurring income of the founder's directory. Editorial analysis: evaluate this model through successful customer launches and the support required for each sale. A lifetime-access offer collects money once while potentially creating future maintenance obligations. Track the time spent resolving installation problems, upgrading dependencies and maintaining documentation. Compare those costs against net receipts after refunds and affiliate fees. None of those margins is established by the disclosed top-line figure, so a new builder should measure them before treating the model as inexpensive passive income.

Distribution signals

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

  • An existing working directory as a product demonstration

    The original founder Q&A identifies OpenAlternative as a source of Dirstarter customers. Editorial analysis: a public working example may demonstrate practical value better than screenshots alone, but its audience overlap must be tested for a new template.

    Evidence

Trade-offs

  • A one-time license lowers ongoing purchase friction but leaves future update and support costs to be funded from later sales.
  • Reusable code can shorten setup work while leaving customers responsible for differentiation, distribution, hosting and ongoing maintenance.

Open questions

  • Which repeated customer request demonstrates willingness to pay for the implementation rather than merely admire the finished website?
  • How much support and maintenance can each one-time sale fund without depending on unproven future sales?

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

Revenue evidence

Founder disclosure
≈ $5,000Monthly revenue · Unspecified $ · Monthly amount reported in the February 5, 2026 founder interview; exact measurement cutoff unstated
Reporting period
Monthly amount reported in the February 5, 2026 founder interview; exact measurement cutoff unstated
Figure as of
Not provided
Reporting method
Founder disclosure
Source checked
Oct 20, 2026
Source published
Feb 5, 2026

Approximately 5,000 per month in one-time purchases, explicitly separated in the original interview. This is monthly revenue, not MRR or ARR. It excludes OpenAlternative, other directories and portfolio affiliate income. No profit or post-fee figure was disclosed.

Piotr Kulpinski, first-person Indie Hackers interview
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.

Official page displays Basic $120 and Pro $160 as promotional lifetime-access prices, alongside $150/$200 reference prices; dollar currency code unstated.

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

What founders can learn

Editorial notes

Productize a reusable implementation only after a working example reveals repeated customer demand for the underlying setup.

Before you build something similar

  • Historical self-report, not payment-provider verification. Dollar currency code and exact measurement cutoff are unstated. Current commercial pages do not establish current revenue.

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

Source material

5 sources
  1. February 2026 original income interview Public source · Checked Oct 20, 2026
  2. March 2026 original founder/team Q&A Public source · Checked Oct 20, 2026
  3. Official product and current price Public source · Checked Oct 20, 2026
  4. Official setup documentation Public source · Checked Oct 20, 2026
  5. Official license scope Public source · Checked Oct 20, 2026