2
4 Comments

My last product died from distribution, not engineering. This time I'm launching in public.

Two years ago I built AGENTS24X7 — an AI SEO-content agent with a WordPress plugin and a Shopify app. The engineering worked. We got exactly one paying user. Investors passed, my co-founder quit, and my brother (yes, my brother) cancelled too.

That failure taught me the only lesson that matters: distribution is the product. Nobody knew we existed.
So this time, I inverted everything.

The Problem We Kept Running Into

I run Codpal, a CTO-as-a-service company. For years, we walked into engineering departments needing to answer one question fast: how is delivery actually going?

The data lived scattered across four different tools — Jira, GitHub, GitLab, and Azure DevOps — and none of them spoke the same language. Commercial platforms exist, but they lock your engineering data behind five-figure enterprise paywalls.

So we built an internal cockpit. It consolidates git activity and issue tracking into one warehouse to surface DORA metrics, team focus, burnout risk, and CapEx vs. OpEx — the whole department’s operational story on a single dashboard. It let us sit with leadership on day one with hard data instead of guesses.

Then we open-sourced it. It’s called Deckgauge — self-hosted, single Docker deploy, FSL-1.1 (converts to Apache-2.0 in 2028).

Live demo: demo.deckgauge.com

GitHub: https://github.com/Codpal-Limited/deckgauge

The Part Builders Will Find Interesting

Deckgauge was largely built by a multi-agent workflow —The tool that measures engineering delivery is itself an experiment in AI-assisted software delivery. (Happy to do a deep-dive post on this setup if anyone wants it.)

What I’m Doing Differently This Time

Building in public: Show HN and Product Hunt launches queued up.

Founder-to-founder outreach: Personalized outreach to engineering leaders and creators rather than generic cold ads.

Open-source core: The self-hosted engine is free and transparent; monetization will live strictly in managed cloud and enterprise governance.

Zero vanity metrics: Documenting the real numbers, especially the ugly ones.

Where We Stand Today

⭐ GitHub stars: ~1 (my mother hasn’t starred it yet, so that’s an honest 1)

💰 Revenue: $0

👥 Design partners: 0

📦 Launch spend so far: $54 ($49 DevHunt + $5 AlternativeTo priority review)

Next post: the raw launch numbers, traffic sources, and conversion fallout — whatever they end up being.

Ask me anything. Especially the critical kind — last time nobody was around to give it.

on September 16, 2026
  1. 1

    Oof—this is a classic scenario: the product functions well “in a lab,” but there's no clear path to connect with buyers when it matters most.

    If your focus is on “distribution this time,” approach it like a pipeline with specific checkpoints rather than relying on a “launch and hope” strategy. What I’m currently building toward in Scaleblogger aligns with these strategies:

    1. Identify your audience by “buying trigger”
      Instead of targeting broad categories like “Shopify store owners,” choose specific triggers such as:
    • “Stores launching or redesigning that need rapid SEO pages”
    • “Agencies managing over 10 client sites”
    • “WP sites struggling with low organic traffic and inefficient content workflows”

    Craft a concise trigger statement and engage only with communities or platforms where this need is evident.

    1. Implement distribution experiments with short timelines
      Prolonged “marketing” efforts often stem from vague strategies. Be specific and measurable:
    • Partner angle: enlist 20 agencies or freelancers, offer a quick-install pilot, and track conversion rates post-initial use.
    • Content-led strategy: create specific pages for the buyer’s trigger (e.g., “SEO workflow for Shopify X”) and measure signups.
    • Template-driven landing pages: illustrate the deliverable (like a content calendar and reporting examples) and execute a focused outreach.

    Select one experiment, then iterate or pivot quickly.

    1. Treat the funnel like an engineering project
      You can't improve distribution without understanding failures. Monitor:
    • Source → install/signup → first key action (e.g., created + scheduled or published an asset)
    • % achieving that key action within 24–72 hours
    • Churn reasons: “couldn’t figure it out,” “quality issues,” or other potential roadblocks.

    Given your experience with AGENTS24X7, if you had only one paying customer, the issues may have centered around either the audience missing the “aha” moment or doubts about operational fit.

    1. Clarify the “first win”
      Ensure onboarding delivers tangible value quickly. For instance:
    • “Generate 5 pages tailored to your niche”
    • “Schedule them over the next 30 days”
    • “Provide clear next steps” (benchmarks, edits, and publishing guidance).

    If the first win exceeds 15–20 minutes or creates ambiguity, conversions will decline.

    1. Approach marketplaces cautiously
      While Shopify/WP plugin markets can succeed, they often progress slowly unless:
    • There’s existing demand in a niche
    • You achieve high install-to-activated-user conversion rates
    • You can generate positive reviews.

    It may be more effective to prioritize targeted distribution (through partnerships, communities, or direct outreach) before scaling into marketplaces.

    1. Create “distribution assets” centered on outcomes
      Buyers are drawn to results. For SEO tools, focus on concrete deliverables:
    • Examples from real niches
    • Before/after content strategies
    • Brief publishing plans
    • Reporting visuals that highlight successes.

    Even a single compelling case study can significantly enhance outbound conversions.

  2. 1

    The previous failure gives you a useful baseline. With Deckgauge, what signal will tell you that outreach is producing real engineering teams rather than just attention?

    1. 1

      The main change is in the budget. I make sure not to have monthly expenses, use free tools and free hosting as much as possible

      1. 1

        That helps explain the cost side. I’m more curious about the customer signal — what will tell you an outreach lead is actually a real engineering team worth pursuing?