My startup is a Service-Based, B2B company. Instead of a "Minimum Viable Product", what considerations should I take into account when I roll out my "Minimum Viable SERVICE"?

Since 2011, this is what I have been doing full time - discovery/validation of a B2B service delivery business. Here's what I've learned: Customer interviews to find product (or service) / market fit is the same whether you're planning to do a product or service Customers don't care whether you are doing a product or service. They only care about the pain you could remove or the value you could create MVP is just one way to in/validate assumptions in your business model. You could learn a lot from customer interviews and test sales. My best "MVP" has been getting paid by a couple of companies continuously for months. Next to that is a proposal template. Finding product / market fit is actually the easy part. Finding a repeatable and scalable way to get customers is harder. Building products is hard but scaling it is easy (eg, AWS or manufacture in China). Building services is easy but scaling its delivery is hard (all sorts of hiring, training and operations management challenges - luckily, these are the challenges I enjoy solving). This book is the closest thing I've encountered to a service version of Lean Startup. My #1 take-away: always create something tangible to represent the value of your service. http://thisisservicedesignthinking.com/

In my experience, a service can also be 'productized' i.e. you can package a service so that it really has attributes of a product. Products are simpler to sell because of the 'tangibility' factor - the customer knows pretty much what to expect when he/ she buys the product. They understand what they are paying for with relative certainty. With a service, much of that is unknown until the service is actually delivered. Therein lies the source of hesitation when trying to convert a customer and make a sale. I run a services company called WagePoint (http://www.wagepoint.com) and I have found that a few things have to be pretty clear when selling services. To productize the serivce you need 5 things to be highly visible: 1) How much (price) 2) What (what the customer gets) 3) How it works 4) What happens if the customer is not satisfied 5) Who uses the service currently (even if they are not paying yet) If you build your MVService with these guidelines, you should be able to test variables like price or 'what the customer gets' through A/B split testing. This will help you iterate your MVService and deliver something of value.

I think provided the magic word. You minimum viable service should be productized. Productizing allows your services to be neatly and cleanly understood before your or the client commits resources to the new project. When they say yes, they know exactly what they are saying yes to (and so do you). Because your delivery is systemized, it easy to see what is working well (or poorly) and make adjustments according. If you do it right, productized services can completely shift the speed and agility of your company. I created a full write-up on this subject containing 32 different examples of productized services. Get it here - http://covetedconsultant.com/productized-service-examples/.

In addition to both the good answers already posted I would simply suggest this: Create a short description of the service you'd like to offer and start pitching it now.  Generally startups find their first idea needs at least some tweaks if not major renovation before it is a viable offering.