6 min read
This is the brief story of and reflection on me and a friend's idea for a startup. We went from product idea, to super minimal prototype to finding out our product probably wasn't going to make money all in a week. This is what happened.
A good friend of mine, Nick Budden, had an idea for a product, and after talking about it over the course of a few days we decided to build it. The product would be a unified solution to many of the problems we face as freelance developers. Problems may be the wrong word actually, more like annoyances. The parts of our job that just serve to get in the way and take up valuable time that could be spent creating cool new things. Let's call the combined sum of these annoyances “Freelance Minutia.”
Here was our initial definition of Freelance Minutia, and thus the problems we wanted to solve:
Our big idea was to create a freelance dashboard that would automate all the annoying aspects of our job.
It sounded great at first. In my own day-to-day work as a freelancer I most often encounter points (1) and (3) above. Finding work sucks, not because it's necessarily difficult but because it usually takes a bit of time, say two weeks to land a new client I didn't know at all beforehand. Then once I landed a client, I would need to keep track of all the various emails we sent back and forth. This is a hassle. Even with separate work and personal email accounts it's easy for emails to get lost in the mix when you have more than one client, or are working on more than one project for the same client.
There are currently no shortage of ‘solutions' to either of these problems in the market. The first problem can be solved to some degree with online job boards. This is after all where me and Nick have both found a significant portion of our past work. But all those various job boards aren't centralized, which makes it a hassle to sift through them all. The other friction point is that far too many of the jobs are complete and utter crap. I could write a whole post on what makes a ‘crap' job listing, so I'll try to stay focused on the post at hand.
Then in the realm of the second problem mentioned above, client management, there are endless software & services that pitch themselves as project management software. Basecamp is possibly the most prominent example of such competition.
The issue with Basecamp-esque project management software in my opinion is that it introduces new friction into one's workflow. As the developer, I must enter new clients in the system, and new clients need to sign up for an account before we can collaborate and discuss the project. If there is anything I have found that clients truly hate, it's changing the way they already work. So introducing this new friction into a projects workflow isn't ideal. The exception is of course clients that already use some sort of software solution, but in my experience they are the exception.
Given what we knew so far, we figured our ideal solution would be divided into a number of ‘modules', each providing different functionality in the end product. The modules were as follows:
So, with our product idea relatively clear in our heads and our belief that the competition was missing something we set out to build a prototype. There's no point building this thing if no one wants it after all. We gave ourselves a one-week timebox to get something out to a group of ten beta testers. So we created the ‘initial version', if you can even call it that, which was prototype of the Job Board. This was actually just a simple Rails app that would display job titles, how to apply, and a brief job description. All the jobs were added by hand by me and Nick. We created this initial version and sent it out to our testers in three days.
The feedback on this first part wasn't great. It was all very constructive, but it wasn't overly positive. The recurring theme we kept on hearing was that other people found the majority of their work offline, usually at networking events or by referral. This meant that to them the job board was all but useless. The feedback wasn't all negative, but it wasn't positive enough for us to spend a ton of time creating a scraper and algorithm to find jobs and bring them into our dashboard. This would have to wait.
Now that we knew the Job Board module wasn't as important as we initially thought, it was time to focus on the Client Feeds / Inbox module. This time, to save even more time spent coding we decided it would be best to just mock it up and send out images of what the finished product would look like. So for the next two days Nick created the mockups while I read up on Rails (neither of us new anything about Rails before starting this project). We sent out the mockups and waited for responses.
This morning, we reviewed that feedback and came to the conclusion that we need to reconsider the whole project. All of our beta testers gave long, insightful feedback and suggestions as to how we might move forward along with features they thought would be useful. However, one theme was consistent across all testers: They wouldn't pay for this — Not yet at least. Since what they had seen in the mockups was pretty much what we imagined the finished product looking like, this was a big hit to the validity of our idea. So, as I said before, we've decided to go in a different direction.
All things considered, we are both very happy with the past week and what we accomplished. We may not have a valid SaaS product yet, but we know that our initial idea wasn't going to work and it took us only a week to figure this out. It would have been very easy to spend a month or two actually creating this product only to find out no one wanted to use it, so spending a week to come to this conclusion is good time in my mind.
Furthermore, I learned Rails this past week. This is an excellent side-effect of actually trying to build something with a new technology. Unlike tutorials which take you step by step through a process and assume you will be able to replicate it later, actually building something forces you to think through a problem, consult documentation, implement and revise. I may not yet be an expert in Rails but I can already tell it will become the mainstay of my back-end development from here on out.
We accomplished all of this while keeping up with our individual client projects as well.
In the end, I both don't feel surprised by our testers' responses but I also feel there is value in our original idea. My problems that I mentioned in the beginning of this post haven't yet been solved, so there's clearly room for value to be created. I think the Client Inbox module discussed above hold great promise, and I still intend to build some version of it for my own use if nothing else.
As for me and Nick as a team, we have decided to take this week for ourselves. We both have more client work to finish up, and I personally have something I want to build before moving on the next project. We have an idea of the next big product we want to create, but if you want to know more about that I recommend checking out Nick's post about this experience.
Cheers from Taiwan, Ian