Tasks for a new startup – Radioki.com and Startup Weekend SF
Posted by shannonclark on April 5, 2009
Saturday was a busy day. Spent at Startup Weekend SF.
Today will be an even crazier day as in less than 24 hours I will be taking 4 pages of notes sketching out a whole application and putting together a mess of parts and web services into what will be a compelling and useful service for many people. After I post this, my evening (well early morning) will be reading API and data format specifications and working out how to build out our first functional pieces.
However just having a great working application is not all of the tasks that a modern, web 2.0, 2009 edition company needs to do to be successful. Here for my own use (and my teams) as well as I hope for many other entrepreneurs is a checklist of tasks we also will have to try to do this weekend. Please add anything I have missed in the comments below!
[and before you mention it – legal structure & incorporation, partnership agreements etc are indeed important and if as we hope it does Radioki takes off we will complete them, we are building this in the context of pre-existing friendships as well as the Startupweekend open & collaborative ethos]
- Register your new brand domain. We did this Saturday afternoon. Nothing at Radioki.com yet, but that will change rapidly.
- Sign up for Twitter for your new brand. I’ve set up @radioki follow us to get updates on our progress, access first and we hope a few other surprises.
- Set up an internal tool for documentation and collaboration. We chose the very simple and easy to sign up for and use PB Wiki as a repository for our team notes, drafts, pseudo code, internally important data etc.
- Establish a simple version control system. Even if you have just one developer, work with a version control system everywhere you can (which is pretty much most things). A wiki for internal team documentation gives you version controls & who made what change data tracking inherently (assuming you as I would suggest use a private tool for that collaboration)
- Establish early on (as in before we launch) customer support & feedback channels. Almost certainly in our case this means that we will create and set up a GetSatisfaction for Radioki (using the free version first until we have a business model to support more) – note, when we complete the next task, we have to go back to sites such as Twitter and GetSatisfaction and upload our logo there as well.
- Design a logo and pick a basic design pattern. Be comfortable with this being basic and expect it to change, but to launch quickly create a simple (even text only) logo to use at your avatar image across the web, to use on your home page, and along with it a basic color palette and design style for your overall web presence. Expect to change this but spending a few minutes early on in the process helps you create a clean, consistent look across web services and sites.
- Set up corporate email addresses. Even if all you do is have them auto-forward to your regular email, yourname@newcompany is useful and is used as proof of employee status by some sites such as GetSatisfaction.
- Join the appropriate networks as the new corporation. In the case of Radioki this means Facebook but because we have a strong Music component also means active engagement with Myspace.com (and especially MySpace Music).
- Update the personal sites and network profiles of all founders. When you launch your personal site and blogs should note this and the profiles of all of the founders (and early employees if you have any) should be updated to reflect involvement with the new company. This is a signal for people who follow you on each network or who read your blogs that you are working on something new.
- Link back to and thank publically as well as privately all the services your new company uses and works with. Besides being just common politeness everyone who builds any service wants to see it used and welcome thanks and updates about how their solutions are being deployed. Also many API providers offer directories of applications using each API. Building relationships with each company your solution relies upon and works with can also lead to lots of helpful advice, guidance, updates about new features and opportunities for promotion.
- Remember to add contact information and background to your new company site. Yes, focus on getting the service built and launched, but also remember to include who you are who are building the company as well as how to reach you and who to reach out to for any media who might want to contact you. Photos of the core founding team are great as are short bios. All serve to humanize what can often be a dehumanizing process (web applications for example). And yes, real names and a corporate mailing address do combine to give lawyers someplace to send stuff – but it also gives journalists, bloggers, investors and future business partners someone to talk with as well.
- Build logging and analytics into your site and application from the beginning. Deploy Google Analytics or another similar product on your new domain from before you share the URL with anyone (hmm we’ve broken this one so have to fix this quickly) For your main application make sure that user actions are logged so you build up a history of interactions. In our case this means ensuring that every search query entered is captured. Ideally you also log what output (or if something failed what error messages) resulted from that interaction.
- Reach out to your friends. A new project whether big or small is perhaps the best excuse to catch up with your friends old and new. In fact I love it nearly every time a friend sends me an update about new projects or companies. Often these updates are the first time I’ve heard from someone.
- But don’t forget to also reach out to the media. Start with the media who are also your friends. If you friends also covers your space then reach out to them on a personal level. Don’t send your friends mass, blast emails if you can avoid it – if not, then follow up (or send in advance as well) a personalized note. Do not rely on your friends having your contact details handy – include a direct phone (cell phones are great) as well as your personal email address.
And those are just the relatively simple, basic stuff. When a new company is launched a whole additional set of tasks get added nearly immediately. A few things to think about relatively soon.
- Corporate banking relationship. This will require legal incorporation in some form (or will require initially to work off a founder’s personal accounts – opening up reams of tax/legal complications. However such a relationship is a key part of being a real business – it gives you a way to sell to people via giving you a means of depositing checks.
- Corporate legal relationship. Establishing a legal relationship, even if a relatively simple and low cost relationship is another part of being prepared to be a real business. A lawyer may early on be called upon to help with incorporation, reviewing various agreements and you hope reviewing customer contracts or investment documents (or best case both).
- Building out the non-functional parts of your new site. What I mean here is collecting excerpts of blog posts and news articles & embedding audio or video coverage. This also includes keeping a new corporate blog up-to-date and continued use of the corporate Twitter account etc.
- An ongoing PR relationship. Of course with a firm who knows your business area, with whom you can work closely and who gets your product as well as process. Great PR firms add incrediable value.
- Telling a clear, updated and ongoing story. If you (or co-founders or early employees) are not great storytellers or public speakers then likely your PR firm (and perhaps other advisers) will need to help with this but especially early on it is vital to have a clear story about the company and your new, emergent brand. This story should be short and clear (oh and compelling)
- Have a business model (or two or three or four). You do not have to implement the business model immediately, nor do you need to share it with anyone (though your co-founders should also know). But having a business model in mind can be exceptionally helpful as you evaluate what to use/not use, what to build/not build, what to track/not track
And yes, this list is long and incomplete.
I skipped over raising money, I skipped over legal incorporation (rarely a good reason not to just incorporate as a Delaware C corporation). i skipped entirely over office space. Until an income is generated a large number of boring but important tasks are delayed (salaries and benefits for example).
For now, sleep then back to work.