24 things to do, and 100 things *not* to do (yet) for building a MicroISV
I've been building another microIsv lately, and as such I've had to produce a new 'to-do' list to keep me focused. It steals a lot from the previous list but matches my current predicament more closely.
I've got 24 things to do, but 100 things I'm *not* going to do just yet. In TimeSnapper (a moderately successful Micro-ISV shared with my colleague Atli) we go well past the first 24 items, and far into the next 100.
Consider also the fractal nature of this work... each item can contain its own sublist of critical and non-critical action items... and so on. A length essay (or at least a series of links) could be provided for every item on the list.
(The worst thing is... even though I know that only the first 24 are needed for now... I so badly want to do the rest before I finished the first ones. It's killing me!)
i intend to complete items 1-24 before 'launch'. (Things already completed are shown in a lighter shade)
micro isv application:
Update: these are some pre-steps that come before everything else
- Come up with ideas
- Minimal market research
- Choose purchase model (e.g. trialware/feature limited)
And here's the list itself...
- build the simplest product imaginable
- fill it with particles of delight
- mark some features as 'paid'
- make it a standalone exe
- have an eula shown on first run
- have a form for registering the application
- call the registration webservice, store the result
- on startup, check if registered
- if registered, unlock the paid features & hide registration hooks
- naming, branding, logo to match url
micro isv website:
- get a url (technically, this step comes before step 10)
- choose your server-side technology stack
- purchase hosting
- choose website template
- index page (landing page)
- choose a price
- register with payment gateway
- purchase page
- handle payment notification from payment gateway
- send "registration code" email
- thank you page (show registration code)
- webservice to confirm registration code from client
- download link
- screenshots of app
i'll probably do these.
tax and legal protection
i may not get to these. i haven't bothered categorising them
Stay tuned of course.
'Nick Hodges' on Sat, 22 May 2010 03:56:40 GMT, sez:
For #4, Delphi is the way to go.
'Leon' on Sat, 22 May 2010 04:34:33 GMT, sez:
Yep, Delphi certainly excels at making standalone executables.
The 'standalone' exe I aim for is a bit less free-standing. I still require the .net framework, but i require no dll's, no config files, no other supporting files, just the vanilla framework (at the lowest version i can tolerate), plus the executable itself.
Where someone has skills in delphi, i would think it an excellent choice for a standalone win32 app.
'Alan' on Sat, 22 May 2010 09:22:34 GMT, sez:
Nice list, though with some repetition.
You left out the "make a profit" bit ;o)
'Leon' on Sun, 23 May 2010 13:09:52 GMT, sez:
Extra items/notes harvested from Business of Software forum:
-3. Come up with ideas
-2. Basic market research
-1. Choose product model (e.g. trialware/feature limited)
From hacker news (http://news.ycombinator.com/item?id=1372087) I learnt that:
Mac-based Micro-ISVs call themselves 'indie developers.' I'd heard the term before but never realised the mac vs ms nature of the two terms. I might need to use both terms to widen my readership ;-)
I also know for sure that no-one likes end user license agreements. I'm still gonna use one.
'delphi' on Sun, 23 May 2010 14:36:12 GMT, sez:
'Mr Grieves' on Sun, 23 May 2010 17:04:57 GMT, sez:
Awesome, I'd never heard the term microISV before despite being one. I guess I've had a very similar list to the initial steps in my head as I've been progressing but never actually formalized it. I'll be referring to this as I go, especially the latter ones as they are not all obvious.
'David H' on Sun, 23 May 2010 23:25:42 GMT, sez:
Yeah, #94 might count as an Epic.
You could break it down into:
#94.1 - Get funky hat
#94.2 - Learn hip colloquial phrase
#94.3 - Walk as if you've got one wooden leg (Note - Funky hat is prerequisite)
#94.4 - Find a restrained, yet 'unique', font to use.
#94.5 - Act evasive and disinterested when it comes to details about yourself
#94.6 - Ensure complete absence of any revenue model
'Micah' on Tue, 25 May 2010 13:48:18 GMT, sez:
Let me guess, World's Simplest List Builder?
'Scott' on Tue, 01 Jun 2010 21:21:21 GMT, sez:
You should use this to flush out and finish your articles "25 Steps for Building a Micro ISV" at: http://secretgeek.net/25steps.asp
'Leon' on Mon, 07 Jun 2010 01:53:31 GMT, sez:
@Scott re: 'flush out and finish your articles "25 Steps...'
I could do that, but it would just be procrastination about building the new business.
I'm going to write as much as I can about the decisions i'm making on this one, but I'm not going to over-promise on the meta-documentation front as I did in the past.
Writing the 25 steps articles would've been a lot of fun, but actually building the business was more important and a better source of material.
I really only get a couple of hours a week to do this stuff so i have to be very picky.
'Stephen' on Thu, 26 Aug 2010 22:40:59 GMT, sez:
How is software license keys managed and generated!
'Adrian' on Sun, 28 Nov 2010 23:06:42 GMT, sez:
Great list. There are many things to do and having a list like this will certainly focus the mind!
'wholesale dvd suppliers australia' on Sun, 29 Apr 2012 05:15:29 GMT, sez:
I have piles and piles of photos and boxes of scrapbooking items to scrap. Not sure where to start. Maybe this class will help get me in the mood…. Thank youfor the chance to win.