Day-day running
Day-day running
Evaluating when it’s best to do something in-house and when to outsource it is invaluable -especially in the case of a developer, the temptation to develop all your internal applications is great. Sometimes it’s better to outlay £500 rather than spending many hours not getting paid by clients.
Assuming you will have a website, create a secure section that has at least a Corporate Risks & Issues Log, so that all authorised staff can be made aware of the ongoing position of the company.
Duncan C. Ion
If you’re starting up with more than one person, having some form of blog is a useful method of conveying this information as it means people can easily subscribe to the RSS feeds and keep up-to-date with the latest information with minimum effort. If you use blog software such as DasBlog [www.dasblog.net] you are also able to have different authors on one portal.
While on the subject of blogs, I would recommend setting up a company blog, or at least a personal blog with plenty of references to your main website. These back links will increase your visibility and hence ranking on Google but it will also increase your company’s profile.
I would advise reading my other posts [The Scourge of Google and Public Facing Blogs and Blogging And Competition] which overviews what I see as the pros and cons of blogging. As you’re here reading this, it’s evidence enough as to why you should blog IMHO.
Processes and procedures
Write down the internal processes you need to carry out in order to provide the deliverables. This includes a definition of your development & PM method as well as your sales process. Ensure that you have a set of terms & conditions that form part of your contract with your client base. This should relate to the PM method, defined deliverables and the payment for these – so typically, you might produce design documents for the solution, [get paid], develop & deliver for user testing [get paid] then a final payment on user acceptance. Be clear about the clients’ payment profile. I have clients who pay in 5 days, others who pay in 60 days.
Duncan C. Ion
Depending on your background, you may not be too interested in the management side of business but it is very important to have a number of management processes in place, you won’t necessarily be able to set these up before you start but as you learn your business, get them in place ASAP.
What sort of processes am I referring to?
- Have a client sign an agreement that outlines the responsibilities of both parties (what you’re going to do for them and what they’re going to do in return –e.g. pay) before you start work for them. Make sure you’re as clear as possible so you can charge for additional services without the client quarrelling with you.
- Depending on the size of the company have the client provide you with a purchase order number. It’s best you ask whatever size the company is as it portrays the image that you’re dealing with larger organisations but the worst they can do is ask you what you mean. A purchase order number is basically a reference in the clients purchase database letting their accounting department know your invoice is on the way in. In many situations it also speeds up payment. When dealing with larger invoices it’s a must because it’s the loosest form of guarantee the person you’re dealing with has informed their accounts department and had the amount authorised.
- After you’ve had a meeting with a client follow it up a few days later with an email/phone call thanking them for their time, make it relevant to the meeting if you can and word it so it requires some form of response from the client. Making this post-meeting contact can be the difference between getting the work and not –in the same way making contact with a recruiting company after your interview thanking them for their time can make the final decision sway your way.
- Have a dedicated admin day. Initially this can be something you do once a month but as your business grows you’ll most likely need to increase this to once a week, as outlined in my previous blog post about setting your rates [Pricing your work] you’ll probably find around two days a week are taken up with adminy type work. People are forever moaning about how boring doing a years accounts is however, if you do break it down to say 2-3hours a week it’s a lot easier It’s important to remain strict with yourself as there’s always something more interesting available ;).
- Invoice regularly! Sounds obvious but it’s important. Depending on your business model, I would recommend setting a day aside every month which is solely for invoicing. I’m not just talking about sending out invoicing, I also mean chasing invoices as you’re bound to have plenty of clients who will delay paying until you really bug them!
- Log payments and receipts –this should be part of your admin day but it’s worth mentioning again. If you log all your receipts and any payments on a weekly basis it should dramatically save that end of year rush trying to find all your receipts for the accountant, if you do it really well it should also save you a few quid!
Team structure
You've got to have someone who is (or can be) a suit rather than a geek (I'm generalising a bit) - the dev side is "easy" the problem is finding clients, selling to them and getting them to pay the invoices (for that matter, for developers, there's often an issue getting to the point where you do invoice them).
James Murphy
As stated earlier, you need to clearly identify how the final decisions are made. Make sure everybody understands these rules. Write them down [Articles of Association]. Define team roles and responsibilities. You need, at the very least, Sales person(s), Project Manager(s), Developers. Some or all of you can take on some or all roles. Be clear about personal capabilities.
Duncan C. Ion
Having someone who’s able to carefully put people in their place and ensure the company is moving in the right direction is important, it’s even more important when friendships are involved. If one of you can’t cut the niceties and point out the obvious you’re more likely to fail from the start.
Having someone who is presentable and can communicate well is intrinsic to getting new business, everyone operates differently but if your new client can’t relate to your representative you’re unlikely to retain them for very long. As James said, if you can’t at the same time tell them to cough up, you’ll probably find yourself with a very low cash flow very quickly.
Getting Employees
This is something that I’m approaching at the moment, so it’s probably best to add in an article later however there is a very good series of articles on Joel on Software [www.joelonsoftware.com] about Finding Great Developers which is a good start [http://www.joelonsoftware.com/articles/FindingGreatDevelopers.html].
The hardest thing you’ll face (if you’re anything like me that is) is loosening that tight grip you’ve got on your business. It’s taken me 3 years but I’m finally allowing Stacey to take over some of the admin work for The Site Doctor in an effort to lighten my work-load (admittedly I should be blogging less too but hey). Accepting that other people work in different ways is a surprisingly hard thing to accept when it’s your own business. I’ve already accepted that if I want my business to grow, I’ll have to put up with someone else’s coding style until we’ve found common ground.
One final point I’ll make here though is (again depending on your business model) you will need to get employees at some point so make some form of provision for them. If you don’t get an employee and try to do all the work yourself forever your business is capped and you’ll more than likely burn out. Someone once told me the perfect business is one that can easily be converted into a franchise.
Business Management
When it comes to business work with your head and not your heart (I'm not saying...be cruel. I'm saying be smart about your business). He mentioned this for techies. A Client/Business is not worried how innovative coding you do, how fantastic n-tier architecture you have, all the latest technologies you use. All he is interested in, is finishing the project as quick as possible so they could earn loads of money. Remember, clients always want the project yesterday. The quicker you can turn around things, the quicker you can earn money. That doesn't mean you gotta rush and give them total pile of crap. The real keyword is "Don't over do or don't get carried away with technologies".
Sunny
Lots of people will give you advice, you can go on many business courses, and read many books, but bottom line is it's your money and livelihood. You are the "pig", the others the chicken (see http://scrumforteamsystem.com/ProcessGuidance/Roles/Roles.html) so if a decision needs to be made, take enough advice, sleep on it then go with your gut instinct. If you get it wrong, learn from the experience and move on. (This strategy once cost me £10k directly but I have made much more from the good decisions over the years, and I won't make that £10k baddun again!)
Ian Blackburn
Well put, you need to be able to fall off your bike and get back on again so to speak, you will make mistakes and if you don’t I doubt you’re taking enough risks and so will just end up ticking over, there’s nothing wrong with making mistakes as long as you can learn from them and move on. Listen to your gut instinct and as soon as it turns sour pull out!
Taking an all -or- nothing approach to things, giving it everything you can/need to until the point that your instinct says enough and then cut it off straight away is important.
Specific advise, be careful about discussing new projects, I once tried to raise venture capital, and found the venture capital guys I went to ask for funding, set up the idea themselves a year and a half later. So just because they've got a suit and fancy office don’t trust them and if you're looking at any new projects cover your IP well.
Mickey Puri
Be careful, but don’t let your project or company suffer as a result of being prudent. If you’re going to talk to someone that’s in the position to do what you’re proposing (i.e. they have the skills or can buy them) at the very least have them sign an non-disclosure agreement to give you a little backup. If you’re really worried, prepare your material so it gives them the minimum amount of information required for their input and explain your reasons for doing so.
Either way, if you ever discuss a project with someone else (even internal employees) there’s a chance it’ll get stolen. The best advice here is learn from it and move on. If you want to pursue the matter in the courts weigh up whether it will be at the cost of the detriment of your company and/or image.
When I first set out, I had to take a client to court and cutting a long story short settled out of court because I calculated the rest of the time I would spend preparing for court would cost me more than I would be awarded. It’s also worth noting that if the amount is below a threshold (IIRC £5000) you can go through the Small Claims courts which saves you a lot of expense and agro.
Action pack or Empower
Easy, action pack you can have more or less forever 'til ms changes its mind and includes SBS Premium which is handy - if you're a multi person business based on MS products its more or less a no brainer (you get 10 licenses for Office for a start).
The empower stuff is rather different - you have to be looking to produce a product and it only lasts two years max (from memory) - of course its a full (or damn near) MSDN sub so its highly desirable as a pro sub is £800 every two years and has nowhere near as many goodies (though most come with the action pack as above).
Equally DO spend the money on things you need - dev hardware, licenses for tools a decent server and printer. I worry about telephony too (this is something we're struggling with because we keep putting off solving it properly...)
James Murphy
Well - I'd say empower leading to certified (and maybe gold partner) - many benefits, great value. Empower requires you to sell an off-the-shelf package from your site within-two years, so can't be a bespoke web app, but you could probably write some small game/utility and sell that from your site to qualify...They don't vet the app at all AFAIK, it just needs to have been "announced"
We have had good success with this route (though we do have a real product), and are currently experiencing some good leads from MS as a result, and have some good relationships that are starting to bring real value to the business.
So I guess it's whether you just want a quick way to cheap licenses or want to build a partner relationship with MS.
Ian Blackburn
Liked this post? Got a suggestion? Leave a comment