SignalStory / Build notes

Why I built SignalStory

This short blog goes over how I came up with the idea of SignalStory based off what I saw while working with the founder of an early-stage YC startup trying to grow our inbound content strategy to book more qualified demos and generate pipeline.

Background Story


I was working closely with an early-stage YC founder to build out our outbound GTM motion. Not inbound, but outbound. Then, suddenly the founder wanted to try out inbound marketing via blog posts. We started working with another company that had also went through the same YC batch which was helping startups generate pipeline by using AI agents to create SEO/GEO based content. These AI agents would scrape the web and analyze common keywords in our niche (similar to how a traditional SEO agency would do back in the day). Then, they’d create blogs to push out our startup’s content whenever people would search for certain keywords or phrases in the space.



All common stuff so far. However, it didn’t work out too well. At surface level, the blogs looked fine - but when we looked at the analytics, no one spent much time reading it and the whole process (which lasted a couple months in total) didn’t convert much more than a few booked meetings one random week.


After a few months with not much results, we churned out of this other company’s service. Then, the founder I was working with tried creating a stitch-up solution using Claude Code to fill in company context and “use claude to passively create good-quality blogs”. This yielded in similar results as well.

All in all, we tried inbound marketing via blog content, but it didn’t see much benefit. Rule of thumb is creating content for inbound marketing won’t be able to generate pipeline consistently in the beginning (unlike our outbound engine which was booking in a regular flow of demos via cold email and LinkedIn), but it is still important for startups to create and post content (especially text-based content) on platforms

like LinkedIn, X, and blogs on your company website so that you can slowly, but surely build your brand voice as a company and eventually start generating pipeline consistently.


So what exactly went wrong?

Founders and teams are posting text-based content on LinkedIn, X, and blogs to build their company’s brand and eventually drive pipeline via inbound - but it’s not low-quality, super generic content that just relates to something within your niche. Instead real quality content comes from signals or actions within your company, that - up until now - only the founders and team would know. For example, onboarding a new enterprise company, doing a case study interview with a top customer, shipping a new feature, etc.


SignalStory is an end-to-end system that lives within your company. It connects to your CRM, project management tool, Github, or literally any tool possible you can connect via webhook. That way, SignalStory has founder-level knowledge on your company. This is the main key differentiator between SignalStory and every other AI copywriting agency. Most other ones start with the writing first, while SignalStory connects to you every single tool your company uses, builds a knowledge-graph on all the information giving it

founder-level context & insights on your company and only then, starts filtering out signals (kind of like an inbound lead scoring mechanism), then writes quality content with all its context and filtering, and finally runs it through an anti-slop gate (we all hate generic AI slop posts that mean absolutely nothing).


The final output is quality thought-leadership content that founders and teams need to be posting in order to grow their brand. If you see the value in SignalStory, please give it a try (completely free for first couple pieces of content) and any feedback would be greatly appreciated!


Thanks for reading!