Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Thoughts on Developing a Product (as a developer)

Sponsored · Ship Features Fearlessly Turn features on and off without deploys. Used by thousands of Ruby developers. →

Thoughts on Developing a Product (as a developer)

Avatar for Randy Schmidt

Randy Schmidt

July 11, 2013

Other Decks in Programming

Transcript

  1. How do you know Randy used to be a structural

    engineer? HE’LL TELL YOU Friday, July 12, 13
  2. How do you know Randy lost a bunch of weight?

    HE’LL TELL YOU Friday, July 12, 13
  3. Selling a Site • Tried selling LIOLI - shut it

    down • Sold DMS - paid off student loans • Huge pain in the ass • After DMS and LIOLI, I no longer think of it as a realistic “exit” • If you do, either make zero money (hard to value) or make a lot of money Friday, July 12, 13
  4. Subscriptions • Aligns costs and revenue • Collect CC info

    once and charge multiple times • DMS: $19/month * 50 * 12 = $11,400 • DMS made as much as LIOLI after six months • Basecamp: $20/month since 2006 Friday, July 12, 13
  5. Pricing Model • Subscriptions match expenses • One-off charges are

    ok if you don’t have infrastructure (iOS apps + iCloud) • Instapaper started as one-time cost for years of service, added subscriptions at some point • Advertising Friday, July 12, 13
  6. Making Money • Plan to make money from the start

    • It is easier to keep working on it if it at least breaks even • Feedbin - $3/month, no trial • Don’t fall back to dev when this gets hard • Revenue is a feature Friday, July 12, 13
  7. Criteria • Time to money • Hobby or business? •

    Does it fix a problem I have? • Am I excited about the project? • Does it make the world a better place? • Is it a muggle problem I’m intimately familiar with? Someone in my family? Friday, July 12, 13
  8. Design • Think outside-in - start with wireframes • Figure

    out the core problem and go from there • Save money to pay someone or find a partner that is a designer • Something pretty makes people happy and more willing to accept bugs Friday, July 12, 13
  9. Complexity • Devs looove complexity, cut it out • Used

    to programming languages - infinite flexibility • You’ll never ship if you try to support every feature request • I get overwhelmed by complexity which I think helps me Friday, July 12, 13
  10. Competitors • Seem like they are scary at first •

    Just look at all the time tracking, invoicing, to do and newsletter apps • Sucks that it seems like all competitors have to build the same 90% of a product • Don’t let them keep you from developing something you think is novel or better Friday, July 12, 13
  11. Choosing Features • Small set of features executed perfectly everywhere

    • Ship once you have solved the core problem • Each new feature needs to be supported • See Evernote and Wunderlist Friday, July 12, 13
  12. Lifestyle • Live cheaply + save money • LIOLI: took

    three weeks off and invested $15k up-front • DMS: invested $4,500 in design + hosting • Just took four weeks off to work on new project • I can take as much time off as I want Friday, July 12, 13
  13. Takeaways • Hobby or business • Have a small nut

    • Have a way to make money on launch • Invest in design - think outside-in • Watch complexity • Be careful not to fall back to development because development is “easy” Friday, July 12, 13