Remove Customer Remove Development Team Review Remove Naming Remove Software Review
article thumbnail

53 Questions Developers Should Ask Innovators

TechEmpower

Even when they have talked to multiple developers or development firms, we’re often the first to ask basic questions like “Who are your customers?” ” or “Are you developing for desktop, tablet, mobile, or all three?” The innovator/developer relationship needs to be a conversation.

Developer 520
article thumbnail

9 Women Can’t Make a Baby in a Month

Both Sides of the Table

In the initial phases of any new market you’re developing a product (hopefully with a minimal set of features), getting feedback from customers, refining your product based on user feedback and then re-launching your product. Markets develop for a complex set of factors that are often beyond all of our control.

Insiders

Sign Up for our Newsletter

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

Trending Sources

article thumbnail

Guide to Create an Uber for Courier App

ReadWriteStart

User-friendly courier delivery apps ensure round-the-clock fulfillment of parcels to customers across different locations. . Without a doubt, the customers have to arrange for the courier delivery by themselves. . The tremendous growth in the on-demand economy has prompted customers to want same-day delivery of parcels.

article thumbnail

Startup Runway Length Depends on Your Burn Rate

Startup Professionals Musings

As a rule, you need to review your burn rate every month, and manage it every day. Another one to avoid cash burn for software development is a contract for percent of future revenue. Do you really need that full-time assistant, regular bookkeeper, and big-name attorney? The components are simple - expenses and income.

Burn Rate 232
article thumbnail

High Burn Rates Result in Short Startup Runways

Startup Professionals Musings

As a rule, you need to review your burn rate every month, and manage it every day. Another one to avoid cash burn for software development is a contract for percent of future revenue. Do you really need that full-time assistant, regular bookkeeper, and big-name attorney? The components are simple - expenses and income.

Burn Rate 231
article thumbnail

Lessons Learned: The engineering manager's lament

Startup Lessons Learned

He has a good team, and theyve shipped a working product to many customers. Hes working harder than ever, and so is his team. Even worse, when it comes time to "fix it right" the team gets pushback from the business leaders, who want more features. The current code is spaghetti, but the new code will be elegant.

article thumbnail

Lessons Learned: Work in small batches

Startup Lessons Learned

Lessons Learned by Eric Ries Friday, February 20, 2009 Work in small batches Software should be designed, written, and deployed in small batches. Its had tremendous impact in many areas: continuous deployment , just-in-time scalability , and even search engine marketing , to name a few. For software, the easiest batch to see is code.