7 gaps in developing a new software product and how we handle those

Customers (whether they know what they want or not) drive new product visions. When we founded Adeptus, it was to address some of the clear gaps that startups and enterprises face in developing these new products. Startups and enterprises alike develop new products either as a ground up disruptive market force or as a constructive tool to effectively utilize an enterprises’  resources. Sometimes they aim to develop radically differentiated products and often times the need is to cater to the customer by enabling digital strategies like mobile, social, analytics and cloud.

Both challenge the status quo and take steps to go through with their vision. Both need a Minimum Viable Product (or whatever they call their initial prototype and way of approaching the base product with minimal yet essential features) and then funding / budgets, as the case may be, to be able to go attract the potential users.
There is a world of difference in the way software products are developed at a startup and at an enterprise. But it is the same eureka moment, that drives the individuals at both places, born of a felt technology or market need.

In either case and in our experience, the identifiable gaps were in:
  1. Validating their hypothesis with use cases
  2. Creating a architecture that the product would grow with in its infancy and then as it grows
  3. Conforming to the standards and practices of the specific technology or market
  4. Getting advise on a basic initial product roadmap, mockups, wireframes, Agile, Lean, etc.
  5. Making early stage decisions on how data would be generated, stored, analyzed and presented
  6. Using existing frameworks, existing solutions, interoperability, integration, interface development, etc
  7. Real world implications of these technology decisions in short, mid and long term

All this while when we worked with clients that were startups from accelerator / incubator program as well as Enterprises – we provided the most value in assisting with challenges towards:

  1. Selecting / validating a technology platform vis-à-vis the product roadmap
  2. Evaluating / recommending on what it would take to get to the respective product stage
  3. Creating / helping create a product development plan in line with expectations from their customers, investors and product owners
  4. Helping address the Mobile, Analytics and Cloud vision for the product

We understood the wish to keep IP in-house and the wish to keep engineering closer at home. Yet, the gap we help address continues to bring in broader as well as niche focus on how product development can be done in convenient ways that are unique & effective to each client, market and product.

What has been your experience? Any learnings? Any breakthroughs you care to share? Did it work out for you with outside expertise? Did getting outside assistance help see the product / development stages differently? …

connect (at) adeptus (dot) in


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s