I'd also add that you should find common requirements that customers have and build your solution around those.
Much better to have 100s of customers using a product with 1 feature, than 1000s of customers using a product with 1000s of features (with the corresponding overhead).
It would be great to see an example of a weekend location, itinerary & recommendations.
Also, would be useful to have a "couples" price.
And a different cadence (once every 2 months, once a quarter)
I have 2 children who need to take meds and would want to buy 2 x medmanager.
- Maybe allow customers to choose more than 1 of the same touchable type.
- Can these be mix/matched across multiple devices ? Can touchables pair with multiple clients ? Can you change the pairing ? More info would be useful
I have come to the conclusion, over many years, that microservices are simply a runtime solution to a compile-time problem. Why can we not develop code in a modular way (to separate concerns & isolate) , but deploy it in a monolithic way (to reduce latency/reliability concerns). This is what we did when OO was fashionable.
I understand that we shouldn't treat RPCs like local calls, but that doesn't mean we cannot do the reverse. If we design services properly we don't need to tie the design and the deployment.
I just can't see the purpose of making something permanently flaky at runtime for the sole purpose of keeping developers on track at design time.
"A failure to comply cancels the transaction. You can get your money back and keep the goods. If the sale was for a service or a digital download, the contract is cancelled and no further payments are due."
I would think that, under contract law, you get your money back and you return the goods - that would be cancelling the transaction. Likewise for digital downloads or services.
Can anyone explain why the provider would be penalized further ?
* Run a spell check over your blog entry. One or two are acceptable but there were so many that it detracted from what you were trying to say.
* I didn't understand what the product will do for me (as a product provider) and how I can use this to increase the number of people who buy my goods.
Nice story. Whilst there is a growing number of women in IT, there is still a noticeable lack in development roles. Only time and attitudes will change that.
We men are not that different. Last week our garden wall was damaged in the storms here in the UK - I had to Google for "the rounded stones on top of a brick wall" (coping btw) so I could sound knowledgeable enough to builders I called for repairs.
They knew I didn't know what I was talking about - and polite enough not to mention it.
> Considering that most businesses fail within 5 years
Business closure rates (at least here in the UK) are around 10% a year. So although your statement is technically true (it would reach 50% after 5 years) these are not necessarily "failures", just closures, and many businesses last 20 years or more. I started 1 business in 1992; have had 3 others that I closed after 6 months, 2 years, and 6 years respectively. 2 were unprofitable, 2 were highly profitable. How does that skew the figures?
Entrepreneurship has never been a young person's game until recently. Older people have more cash and fewer liabilities - children have left home and mortgages are paid off - so have more financial flexibility.
Investing 12K from savings is no big deal when you are older and actually have saving to invest. And as for paying yourself - you have a retirement income.
I've found meetups to be frequented by many different types, including those that think they are not very social. Don't be put off by that - you'll find your common interests help guide you through.
Or go with a friend if you feel awkward.
This experience relates to a startup in 2005 that folded during the credit crunch (2008). I am now working on a new product suite whilst continuing to consult.
The Mortgage Portal was an online marketplace for mortgage brokers to find appropriate products for their customers. It started with an idea that I spent a month building in my spare time. I worked with a colleague (both of us consulting in the mortgage technology arena) to bring it to market.
I started with a flexible mortgage that I drew salary against - so £0 capital. We then went around hawking the idea to the marketplace. We met a lot of resistance from established players (owned by the big banks, so no way we could disrupt the marketplace), and in the end pivoted into a platform for new lenders to get to market quickly. We helped a handful of banks launch new channels in a few months, which was a great selling point. Then came the downturn.
Our sales model was monthly fee + per transaction fee. It was never profitable.
We didn't look at grants/loans. There are some around, but my opinion is they are probably a distraction at this stage. If you're interested look at http://www.j4bgrants.co.uk/ - they have a wealth of information.
The most valuable thing we did was pivot. We didn't pivot fast enough which made things untenable.
We never scaled (started with two, ended with just me), and we failed for various reasons. I could blame the market - all our remaining customers either went bankrupt or closed within the space of a few days - but the reality was that the idea was just a starting point and we didn't move from that.
In my view, if you have an idea, your first step is to go out there and find a customer. Don't build anything (that is the easy bit) before you have someone willing to give you money. We should've done that - taken the idea and then asked what our customers wanted to do with it - rather than impose our views on them.
As for resources, there are many available and it will depend on what your trying to achieve and where you're located. If in London, I'd recommend the Google Campus (http://www.campuslondon.com/) as a good starting point. Then look for Meetups in your area.
I am interested to see how this grows.
There are many commercial sites available that provide this service, and there is certainly space for others if they focus on particular niches.
How do you intend to promote this? How can the community help to get the word out?
Much better to have 100s of customers using a product with 1 feature, than 1000s of customers using a product with 1000s of features (with the corresponding overhead).