
Developing Software Requirements
6 Reasons Your Requirements Suck, And How to Fix It
After promoting the lead magnet via a combination of Facebook ads and Twitter - plus one email to my long-dormant email list of 1,500, offering an opportunity to opt in for my new list - I found myself with another offering that failed to generate even 1 opt-in.
Angry, humiliated and drained, I killed the offering entirely.
After the first two weeks of promotion, 4,000 people had seen my initial "cold audience" promo video. What was not happening, however, was people watching the next video in the series - the one that solicited an opt-in into the email interest list.
I didn't know why the breakdown was occurring, and since these people were not on an email list yet, I had no way to reach out and ask. I was completely in the dark, and had no data to use in helping me decide what to do next.
This is when I fell back on what I knew, and began to promote the offer on Twitter.
Like
Comment
A friend with a lot of experience in Facebook ads showed me how to set up different ads for cold, warm and hot audiences.
Never having used the platform before, I thought that maybe this could be the element that my previous offerings were missing.
Like
Comment
About
Many freelance devs have expressed difficulty in discovering a solid set of requirements for client projects. This book was meant to break that process down into a simple set of rubrics.

2 Comments
Hi, Rosie! I'm not looking to pick it apart now that I've already killed it. Thanks, though!
Maybe you can post the link for feedback here to the IH community? Get some insight/input as to why it didn't work.