building an open source consulting company
DESCRIPTION
Lessons learned from a successful open source consulting company. This talk is geared towards the open source developer who is considering starting his/her own business, and the entrepreneur who wants to grow the business by leveraging open source development methodologies.TRANSCRIPT
Building an open sourceconsulting company
Nate Aunewww.jazkarta.com
Open Source Bridge ConferencePortland, ORJune 17, 2009
1
/me
• First experience with Linux in 1994
• Founded Jazkarta in 2004 in Boston
• Now 3 full-time staff and 10 subcontractors
• Specialize in Plone and Python
2
Topics for exploration
• Marketing
• Pricing
• Contracts
• Project Management
• Services
• Recruiting
• Finances
• Open Source citizen
• your topics?
3
Marketing
4
Marketing & getting work
• Speaking
• Blogging
• Sponsoring
• User group / consultants group
• Networking
5
Pricing
6
Pricing / rates
• How much do you want to make?
• What are your costs?
• What will the market bear?
7
$100,000 / yr$100,000/yr % 50 wks/yr % 20 hrs/wk
=
$100/hr
8
Costs of doing business(overhead)
• Self-employment tax
• Legal fees
• Accounting / bookkeeping
• Office space
• Hardware
• Subcontractors
• Telephone
9
Market rates
• What are your competitors charging?
• How much will your customers pay?
• How does the economy affect your bill rate?
10
When to raise rates?
• When your customers don't blink an eye when you tell them your rate
• When you have more work than you can handle
• When you have an in-demand skill
11
Contracts
12
Contracts
• Get legal advice - don't do it by yourself
• Optional scope contracts
• Tools: EchoSign for digital signatures
13
Traditional vs. Timeboxed
Optional scope contracts:
14
Project management
15
Project management
• Agile is aligned with open source development
• 2 week iterations
• 3 person teams (PM, dev, design)
• Tools: ClueMapper, Google Docs, Dropbox
16
Resource planning
17
Global Team
18
Global team strategies
• Group team members in same or close timezones
• Make sure everyone is on IRC and uses it
• Set up a mailing list for each new project
• Skype calls every week to touch base
• Issue tracker (ClueMapper/Trac)
• Version control (Subversion/Bazaar)
19
Pros/cons of subcontractors
• Pros
• Only pay them when you have work
• Can find top talent, specialists
• Cons
• More expensive
• Can be difficult to retain if not enough work
20
Services
21
Services
• Development
• Training
• Support
• HostingRecurring revenue
22
Training
• Private onsite training
• Public training
• Training as part of a conference
• Online training
23
Support
• Open source = no guarantees
• Retainer = insurance policy
• Keeps the conversation going
• Upsell support before the project is complete
24
Hosting
• Easier to support if on servers you control
• Distribute benefits across all customers
• Upselling opportunities
• Steady source of recurring revenue
25
Recruiting
26
Recruiting
• Read blogs
• Attend sprints
• Elastic staff
• User groups
• Internships
27
Finances
28
Finances
• Get a good bookkeeper
• Seek next project while still on first project
• Find sponsors to fund open source dev
• Tools: Quickbooks
29
Open source citizen
30
Open source citizen
• writing documentation
• contributing code
• serving on board
• sponsoring sprints
• organizing user group
31
Thanks! Questions?32
Stay in touch
• Email: natea (at) jazkarta (dot) com
• Twitter: twitter.com/natea
• Blog: blog.jazkarta.com
• IRC: irc.freenode.net/natea
33
Books & Resources
• e-Myth Revisited by Michael Gerber
• Manage It! by Johanna Rothman
• Ship It! by Richardson/Gwaltney
• Art of Agile Development by Shore & Walden
• Making Things Happen by Scott Berkun
• Computer Consultant's Guide by Janet Ruhl
34