Lessons from Kickstarter Part 1: Don’t go off half-cocked

by Suw on November 30, 2011

The last 18 months has taught me a lot about Kickstarter and putting together my own self-publishing project. This is the first of a series of blog posts in which I’ll go through what I’ve learnt, partly in case it’s of interest to anyone else but also to codify it in my own head so that, hopefully, I won’t make the same mistakes again. So, herewith Part 1!

If there was one overarching lesson that I’ve learnt doing Argleton, one thing that I really wish I’d thought of 18 months ago, it would be this:

Don’t go off half-cocked

Whilst there’s some truth to the idea that ignorance is bliss and that if I’d known what I was taking on I perhaps wouldn’t have done so, I think there’s more truth in the idea that I would have saved myself a lot of pain if I’d planned things better. Instead I bouncily assumed that it couldn’t possibly be that much work and that I’d have the whole thing done by the end of the summer. In 2010. Whoops.

So here are a few thoughts on how to make sure you’re fully prepared before you launch your Kickstarter project.

1. Finish as much of your project as possible
I naïvely thought that I could finish writing and editing Argleton whilst the Kickstarter fundraiser was underway, but promoting the campaign took more effort than I had anticipated, leaving me not much time to write. This had serious knock-on effects: Because I didn’t know how long the story was going to be, I couldn’t get accurate quotes for printing and so my rewards were priced by roughly guessing. I’ll go into budgeting issues in another post, but suffice it to say that guessing is a Very Bad Idea.

Another impact of having not finished up as much as I could was that it lengthened the time between people pledging support and my delivering my book to them. My ‘deadline’ for sending out the books just kept slipping and whilst most people were very patient, a couple sent me rather sharp messages questioning my commitment. I have to say that stung, but I could have avoided it if I hadn’t gone off half-cocked.

I should have had the book finished, critiqued, edited, typeset and converted into multiple digital formats, with all my rewards properly designed and fulfilment planned before I even considered launching my Kickstarter project.

2. Understand how much of your project remains
You can’t always finish everything up front. Had I hired someone to design my cover, for example, I would not have been in a position to do that until the Kickstarter money came in. That’s fair enough, but make sure that you know exactly what tasks are outstanding, how you are going to complete them and how long they are going to take. This allows you to be up front with your supporters about what’s left to do and how long they’ll have to wait for the finished thing.

3. Complete the design and prototyping of your rewards
Another really time-consuming part of the project was designing and prototyping my rewards, the books. Whilst they were easy to describe in text, they turned out to be difficult to turn into a reality. I learnt that I am not a natural graphic designer and that my ideas about what would work as a cover in print and in silk were very difficult for me to realise. The silk cover in particular went through about nine prototypes all together.

Had I gone through that process before launching my Kickstarter project, I would have learnt early on that I needed the help of a designer and I could have worked that into the project costs. I also would have realised how difficult the silk cover would turn out to be to actually make and just how long each one would take. I might still have gone ahead, but it would have been with eyes open.

4. Get your suppliers lined up
This is important not just for budgeting, but also to save you time when it comes to getting everything done and sent out. The first printer I looked at turned out to be incapable of doing the job in the way that I wanted: They didn’t have experience making books and didn’t have the right kind of binding technique which meant that when you opened the book, the pages fell out. Not really the result I was aiming for.

Finding a new printer, briefing them, and going through more prototypes was time consuming and set me back by months. In the end Oldacres did an amazing job, and I will be using them again on my next project so the relationship I formed with them is important, but I could have got there sooner. (Especially as they were actually the first recommendation I had had. :/ )

5. Understand your incompetencies
Obviously, I like to think I’m a half-decent writer, so the task of finishing and editing the story was easily doable. I’m also quite good at typesetting, having done that professionally in a different incarnation. But what I hadn’t really banked on was the fact that I’m a shit graphic designer and an even worse puzzle writer.

Not only did my weaknesses slow the project down (I’m still finishing of the puzzle, for example), they also made everything unnecessarily difficult. Had I looked at the puzzle before I launched, I would have realised how much effort it was going to be and might even have questioned whether it was even needed. In retrospect, I think the inclusion of the puzzle or geogame was more a statement of my own lack of confidence than a genuine contribution to the project.

6. Understand your dependencies
I hate to say it, but I should have Gantt-charted the project and thought hard about what was dependent on what. I wasn’t always clear on what could be done in parallel and what had to be done in order, and so I often defaulted to doing things in serial, thus delaying the project further. Partly that was a psychological thing: It felt easier to deal with one set of related problems at a time, rather than trying to solve issues on multiple fronts simultaneously. There’s no doubt at all that drastically slowed me down.

Had I sat down and worked out my dependencies, I would have been able to prioritise my to do list better. I would also have known when I needed to make educated assumptions, and what I would have to find out in order for those assumptions to hold water.

One good example is calculating postage. I hadn’t finished the story, so didn’t know how long it was, so didn’t know how many pages it would be, so couldn’t figure out the weight or find the packaging and so couldn’t make even a vaguely informed calculation as to the likely cost of postage. As it was, it cost a lot more than I had anticipated, as did the printing come to think of it, and I was lucky that I had raised more than I needed so didn’t actually lose money.

7. Don’t overcomplicate things
As I mentioned above, the geogame in the end turned out to be more of a gimmick that I hoped would get people interested rather than integral to the storytelling. Whilst I have done my best to produce something that is enjoyable, the fact that it has only now reached the testing stage shows just how difficult I have found it. I could have done without it and, if I had, I don’t think the project would have suffered at all.

Whilst most of the rest of the Argleton project was relatively simple, if time consuming, I did apply this rule to what was going to be my next project – a story told through the medium of a newspaper, complete with fictional character profiles, classifieds and sports page. I still love the idea, but during the planning process I realised that it was actually a very complicated project that would require collaboration with a number of people. I’m not ready to do that yet, although I will definitely be keeping that on my list of projects to look into when I’ve got a better flow of money coming in from my ebooks.

My aim in all of this is to produce a small but growing body of work, both electronic and in various physical media, which can give me an income. To this end I need to ensure that future projects are doable in a much, much shorter timespan than Argleton. Taking two years to do a novelette is not sustainable, so future projects will be much, much simpler and will hopefully complete more quickly.

Queen of the May

Every year, on May Day, a young woman is stolen away by the faeries to become their Queen for a year. This year, though, the faeries have bitten off more than they can chew. Shakti Nayar will do whatever it takes to get her own life as a botanist back. As she struggles to work out how to get home, she uncovers Faerie’s dark secret and finds that she is not the only human who needs saving.

The Lacemaker

All the threads looked the same to the innocent eye, but Maude could see the black heart running up through one strand as it wove its way through the lace roundel. She busied herself with tidying her bobbins as a customer browsed the lace mats on her stall.

“I’ll take this one,” the woman said, holding up a square piece, twelve inches across. Maude winced, picked up the piece she had just completed and held it out to the woman for her consideration.

Argleton

Matt is fascinated by the story of Argleton, the unreal town that appeared on GeoMaps but which doesn’t actually exist. When he and his friend and flatmate Charlie are standing at the exact longitude and latitude that defines Argleton, Matt sets in motion a chain of events that will take him places he didn’t know existed… and which perhaps don’t.

Subscribe to my newsletter

Meta

A Passion for Science

From the identification of the Horsehead Nebula to the creation of the computer program, from the development of in vitro fertilisation to the detection of pulsars, A Passion for Science: Stories of Discovery and Invention brings together inspiring stories of how we achieved some of the most important breakthroughs in science and technology.