This is the first year-end retrospective for Dangercorn Enterprises. I'm writing it in April because our fiscal year is weird and because I want to write it while the lessons are still fresh, not while I'm waiting for numbers to fit a calendar.

Some of what's here will be revisited in another year-end post. Some of it will look obvious in hindsight. Some of it is probably wrong and I don't know it yet. I'm writing it anyway because the exercise of honest self-assessment is worth more than waiting for a cleaner narrative.

What Got Built

In rough quantitative terms:

Revenue is small. The MRR across the catalog is in the low four figures. The revenue curve is moving up, slowly. It's not sustainable yet as a family business.

What Worked

Three things clearly worked.

The template. Going from idea to shipped vertical in a weekend is the foundation of everything else. Without the template, 220 apps is literally impossible. With it, it's a grind but a tractable one. Anything that invests in reusable infrastructure in year one pays back dramatically.

The self-host tier. The free GitHub repos are what drove virtually all of the organic traffic, SEO, and community momentum. Self-host users who become paying customers are rare but existent. More importantly, self-host users who talk about the repos drive more signal than any marketing we paid for.

The blog. The blog (which you're reading) has become the primary asset for narrative. Every post is a piece of the thesis. Cumulatively, they sell Dangercorn better than any landing page could. Writing them has also clarified my own thinking on what we're doing and why.

What Didn't Work

Also three.

Cold email. 375 emails, 4 human replies, 0 closed deals. Covered in the retrospective. The channel isn't dead for everyone, but it's dead for our current product mix and audience. We've pivoted away.

Some verticals. We've archived 6 verticals that didn't find audiences. See the pruning post. Not catastrophic — 6 out of 220 is an acceptable kill rate — but it's a signal that we're not perfectly calibrated on which markets are real.

Time management. This is the biggest. Trying to ship 220 apps, maintain an agent fleet, run outreach, write blog posts, build trading systems, and have a family simultaneously has not always gone well. The tradeoff has sometimes been family time, and that's the wrong answer. Year two's top priority is better work-life structure.

The Strategic Bet, Revisited

The 220-app thesis was: the marginal cost of shipping a vertical has collapsed; build for niches that are too small for anyone large to care about; let the catalog compound.

A year in, the thesis holds up. Marginal cost of a new vertical is genuinely in the 1-3 day range. Niches are genuinely untouched by larger competitors. The catalog is genuinely compounding in SEO and community terms.

What the thesis didn't account for: distribution is still hard. Shipping a vertical at low cost doesn't solve the problem of getting that vertical in front of its audience. We're still figuring out distribution. The TikTok thesis is the current bet, but it's unproven.

The Honest Financial Picture

Year-one Dangercorn revenue is thousands, not tens of thousands, per month. Expenses are modest (CI ~$100/month, Anthropic API ~$50/month, hosting ~$80/month, domain registrations ~$20/month, various other small line items). We're cash-flow positive on a monthly basis, but not by enough to replace either of our prior income streams.

Jess continues to operate Dangercorn Crafts, which generates its own income. I continue to consult on the side. Dangercorn Enterprises is the main bet, but it's not yet the main income. That's honest.

What I'd Do Differently

Five things, in order of importance:

1. Lead with distribution from day one. I spent 9 months building the catalog before seriously testing distribution. In retrospect, 3 months of template + 20 verticals + serious distribution testing would have revealed what worked faster.

2. Test video earlier. Short-form video seems like the right channel for our catalog. We should have tested this in month 3, not month 12.

3. Write the blog earlier. The blog is retroactively one of the most important things we built. It should have started at month 1, not month 8.

4. Price more aggressively on Hosted Pro. Several verticals are underpriced. $29 when $49 would be accepted leaves money on the table at a scale where any revenue matters.

5. Better family-time structure. Working evenings on the fleet while the kids are awake is not a trade I should have been making. The fleet can wait; the kids can't.

What Year Two Looks Like

Not committing to a ship target. Committing to:

If year two ends with $20K/month in MRR, I'll consider it a clear win. If it ends at $5K/month with stable growth, I'll consider it a qualified win. Anything below that means I have to seriously reassess whether the thesis is wrong or whether I am.

The Thing I'm Most Proud Of

Not the count of apps. Not the fleet. Not the template. What I'm most proud of is that we did this as a family, on our terms, with our values intact. Jess and I are still married, still co-parenting, still enjoying each other's company. The work has been intense and the income hasn't been great, but the relationship has improved. That's the real asset.

The business is a means to an end. The end is a life that's ours. Year one didn't deliver the financial piece yet. It did deliver the structural piece — the life is genuinely ours in a way it wasn't before. That's worth a lot.

The Open Question

I genuinely don't know if year two will turn this into a sustainable family business. The thesis is intact, the execution is improving, the catalog is growing. None of which guarantees the revenue catches up to the work.

What I do know is that we're better positioned than we were 12 months ago. The infrastructure exists. The brand exists. The catalog exists. The blog exists. The content compounds. The Hosted Pro customers we have like the products. The self-host community is small but active. The pieces that matter are in place; the next 12 months are about whether they aggregate into enough revenue to call this work.

If they don't, I'll write that retro too. The whole experiment is in public. If it works, the lessons are useful to other founders trying something similar. If it doesn't, the post-mortem is even more useful. Either way, the writing continues.

Year one doesn't get you where you want to be. Year one gets you to where year two is possible. If year one was survivable and the direction was right, that's the full year-one goal.

Related

The 220-app thesis. Why we're not raising. The economics going forward. The pruning we'll continue. The distribution bet for year two.