Mentioned previously in part 2, the market picked for Lemmatic was the Wix App Marketplace. There's a few good reasons for this.
Wix has a prebuilt audience looking for products and integrations
They offer 100% of revenue share for the first year and handle payment processing
They bring the content, I don't have to go crawl or scrape it
Great docs and APIs
I was already on the SEO advisory board
Pitching Lemmatic
First, anyone can make an app for Wix. You don't have to pitch them. However, they do have a Strategic Integrations team who works to get high priority apps into the market. I wanted all the help I could get and to do that, I needed to pitch Lemmatic. Normally, they only work with existing products so it was important to make Lemmatic more real.
My first pitch deck was rough and ugly. But I think the hook was good. Content feedback tools are so helpful for SEO. So Wix requested a wireframe. My first wireframes weren’t pretty but they walked the team through my ideas and the basic need we could provide Wix users.
As I got deeper into the process, it became more like an enterprise project. It needed
A project spec
Wireframes
A user flow
A pitch deck
Overall, it made me plan the project in a very intentional way. I really appreciated being forced to think things out upfront.
User Flow Sneak Peek
Without setting this in concrete, here's the current user flow. Like I said, it's a bit strange to be creating a whole product on spec. User flows like this are important for making a speculative product more real.
We collect some basic data like competitors, keywords, and a goal word count per blog posts. Then we load in all the blog posts and process them with our NLP functions. Once processed, users can look at data and insights for each blog post. Keywords are manageable and linked to posts. Each post can have multiple target keywords. An analytics section will provide sitewide or post specific details on change history.
Part 6 coming soon!