Minimum Viable Product · Terms and conditions

Terms and conditions for a MVP?

Ana Burman Founder at Rhea m-Health

June 10th, 2015

Hi there! I am starting an user validation exercise and would be very grateful if anyone has a template / sample for a terms and conditions. Many thanks, Ana

Reuven Granot Corporate Strategic and Scientific Officer at Perlis Ltd

June 11th, 2015

I suggest you should read "The Startup Owner's Manuel" The Step bu Step Guide for Building a Great Company by Steve Blank and Bob Dorf.

It's all about your problem and I strongly recommend it to all who still did not read it.

Clynton Caines SharePoint Developer at Discover Technologies

June 10th, 2015

It's probably best to outline your specific need so that others know how  to respond. I take it that you require something in the Health Care arena (but I'm just guessing).

Here's my take on the generic question. It's important to know your audience and what you're trying to protect - ex: do you care about privacy/confidentiality? Are you in stealth mode and want to protect certain IP? Are you worried about being sued and need really tight legalese? Is the scientific community your target - who will expect "big words" in the T & C or the general public who would appreciate straight talk? Here's one I created that covers all the bases - written for general users: http://1gifapp.com/policy.html On the other hand, I've used others that read more like dissertations on NDAs for nuclear physicists... It all depends.

Karl Schulmeisters CTO ClearRoadmap

June 10th, 2015

Terms and Conditions? As Clynton points out, it sounds like you are in stealth mode. But here's the thing - while it makes sense to be in stealth mode from the big players - if you are worried about your customer base "stealing" your idea and executing on it better than you can, you probably need a new idea. Because if its that easy to do, even if you launch first, someone else will copy it and you will have competition.

This is particularly true in healthcare where if you are doing a device of somesort, the whole 510k Predicate process is designed to encourage such copying

BTW if this is you http://rhea-mhealth.co.uk/  and you plan on taking this idea to the USA - you probably want to consider taking a look at https://ClearRoadmap.com. (yes it is our product but this is less about a pitch to you and more about the fact that you are stepping into some potentially murky regulatory waters since even though all you do is connect women to "experts"  in doing so, you are holding, tracking, and potentially revealing personal medical information.  And that is regulated in the USA).

David Schwartz Multi-Platform (Desktop+Mobile) Rapid Prototyping + Dev, Tool Dev

June 10th, 2015

It's not clear what you're asking for. T&C for an MVP is nonsensical.

Are you asking about writing a REQUIREMENTS DOCUMENT?

Or are you asking about some kind of ACCEPTANCE TESTING CRITERIA?

It would be most helpful for you to lay out a few bullet items of whatever it is that you've got in mind to give people a hint as to what you're looking for. You should be able to come up with at least a half-dozen fairly quickly.

Alper Cakir

June 10th, 2015

I just used this as a temp solution:


https://termsfeed.com

Ana Burman Founder at Rhea m-Health

June 11th, 2015

Thank you very much guys! I really appreciate your comments and knowledge sharing.

In response to David's point, what I am trying to do is to set the expectations so the users know what they can and what they can't expect of the product at this point in time. 

Thanks for your comments Karl. At this point we are not planning on going to America, but I am aware that there are a number of regulations to address. Your product will be very helpful when that time comes. I would like to keep in touch with you.

I am in kind of stealth mode, more to validate the concept than worried about competition at this point Clynton. Because of the nature of the product I need to make sure that people have the right expectation. 

Thanks again. Hopefully all will go well with this experiment and we can continue build an awesome product.

Cheers,
Ana

Clynton Caines SharePoint Developer at Discover Technologies

June 11th, 2015

K. I'm no marketer, but that sounds more like a benefits/features list + roadmap. But I'm no woman either - so your write-up might need to be completely different from what I'm thinking. LOL

Karl Schulmeisters CTO ClearRoadmap

June 11th, 2015

ok - so that helps.  I full well understand how important that "first impression" is in healthcare arena.  So what I would do is set up a non-public site (ie one that does not have your domain name mapped to it)  and then identify a handful of users you trust and approach them about giving you feedback.   And if they say yes - email them the URL with the explicit and clear caveat that this is a temporary URL for feedback purposes only.


Then after getting the feedback you can just take down the site, or close access to it while you finish developing it.  Once you are ready to re-open it, you attack the correct domain name to it and roll it out to great fan fare

David Schwartz Multi-Platform (Desktop+Mobile) Rapid Prototyping + Dev, Tool Dev

June 11th, 2015

"In response to David's point, what I am trying to do is to set the expectations so the users know what they can and what they can't expect of the product at this point in time. "

These are called "requirements" internally, and would be grouped into product releases or versions.  They're expressed externally in a "feature/benefit matrix". You could have multiple releases scheduled that outline how different features/benefits are planned to be added over time.