Remove Open Source Remove Product Development Remove SEM
article thumbnail

Lessons Learned: SEM on five dollars a day

Startup Lessons Learned

Lessons Learned by Eric Ries Saturday, September 13, 2008 SEM on five dollars a day How do you build a new product with constant customer feedback while simultaneously staying under the radar? SEM is a simple idea. In a mature company with a mature product, the goal is to pay for lots of people to come to your website.

SEM 164
article thumbnail

Lessons Learned: What does a startup CTO actually do?

Startup Lessons Learned

If not, whos going to insist we switch to free and open source software? Labels: product development 15comments: mukund said. For example, how are you going to explain that component drive architecture like.NET isn't going to work for cross platform open open source business models?

CTO 168
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Lessons Learned: The three drivers of growth for your business.

Startup Lessons Learned

Paid - if your product monetizes customers better than your competitors, you have the opportunity to use your lifetime value advantage to drive growth. In this model, you take some fraction of the lifetime value of each customer and plow that back into paid acquisition through SEM, banner ads, PR, affiliates, etc.

article thumbnail

Lessons Learned: The lean startup

Startup Lessons Learned

But by taking advantage of open source, agile software, and iterative development, lean startups can operate with much less waste. I am heavily indebted to earlier theorists, and highly recommend the books Lean Thinking and Lean Software Development. (So The lean startup is an application of Lean Thinking.

Lean 168
article thumbnail

Lessons Learned: Great open source scalability tools from Danga

Startup Lessons Learned

Lessons Learned by Eric Ries Friday, September 5, 2008 Great open source scalability tools from Danga If you are trying to build a scalable LAMP service, its always best to start with the original and still quite relevant presentation, from Brad Fitzpatrick when he was at LiveJournal. You can find the 2005 version here.

article thumbnail

Lessons Learned: A new version of the Joel Test (draft)

Startup Lessons Learned

I am convinced one of Joel Spolskys lasting contributions to the field of managing software teams will turn out to be the Joel Test , a checklist of 12 essential practices that you could use to rate the effectiveness of a software product development team. Thoughts on scientific product development Lo, my 5 subscribers, who are you?

article thumbnail

Lessons Learned: The one line split-test, or how to A/B all the time

Startup Lessons Learned

This gets me into trouble, because it conjures up for some the idea that product development is simply a rote mechanical exercise of linear optimization. You just constantly test little micro-changes and follow a hill-climbing algorithm to build your product. How to listen to customers, and not just the loud.