This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
We spent time out in the marketplace talking with customers, looking at their solutions, comparing ourselves with our competition and then squirreling ourselves away in our offices designing our next set of features. Our sales guys were on the front line and heard what they needed to win deals. Tim started to change our processes.
Both programmers, the two reconnected after doing stints as customdevelopers during and after college, and then when they were developing tools for their families’ businesses as residential contractors in the Los Angeles suburb of Glendale. These kinds of technologies, unlike AI, don’t automate away workers.
I’ll publish the final post in this series this week and then move on to my next series – sales & marketing. I’ll be covering my PUCCKA sales methodology. When I first met the team in San Diego they had only been working on their software for 5 months. It will be controversial – I know.
Those with their ideas selected were out on the prowl, looking to recruit the top designer or developer in the room. Teams reconvened Saturday morning at 9:00 AM and continued to code and build their startup throughout the day. By 10:00 PM, teams were working away into the night. Coffee is for closers!” making this their first SWLA.
That died with waterfall softwaredevelopment. Do you really want to spent $100k building a product to discover through CustomerDevelopment that the market is too small? Ditto for enterprise software companies. It’s “lifetime value&# of a customer. Each quarter you should review your model.
5 Lessons from 150 startup pitches - A Smart Bear: Startups and Marketing for Geeks , July 11, 2010 I just reviewed several hundred startup pitches for Capital Factory. Between this blog and reviewing applications to Capital Factory I see hundreds of pitches a year. Customer Validation needs to have the CEO actively involved.
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content