Product Specification

Define product specifications and get input from stakeholders.


Product Specification


  • Status: In progress

  • Stakeholders:

This project aims to increase conversion by introducing a live chat in our app as a 5-week experiment.



Test if live chat can profitably increase conversion.


  1. Free-to-paid conversion rate is too low (~5%). Comparable services achieve 8-10% (source).

  2. Prior support tickets and survey results show that unanswered questions and lack of clarity on certain pricing aspects may be partially responsible.

  3. Adding a link to the FAQ section made no significant difference to the conversion rate.

Out of scope

  1. Major UX changes.

  2. Non-English chat support.


Nuclino Tip

You can easily embed designs directly into Nuclino. Here's an example – use Figma to create and embed your own designs.

→ Details in: Design Document: Live Chat.

User experience

  1. Button: Label it “Chat with us” and put it in the bottom-right corner of the app.

  2. Behavior: On click, show the support agent’s name and profile picture, and display the first message “How can we help you today?”.

  3. No auto-popup: We may try this later.

Tasks and timeline

Live Preview

About this template


A product specification document defines the product you are about to build and acts as a central source of truth for your team. It forces the stakeholders to plan a feature release up front, increasing accountability, lowering the risk of delays, and adding transparency to communication. To put it simply: It helps you ship the right product with higher quality, speed, and predictability.

A product spec focuses on the "What", "Why", and "How" of the product you are building – namely its purpose, functionalities, and behavior. This includes your assumptions, hypotheses, user stories, design concepts, and so on.

We have put together an example of a product specification which can be copied and used as a template to gather specifications and get input from your team.

How to write a product specification

There are many possible ways to structure a product specification document, but you must always address the following five things:

  1. The problem
  2. Measurable goals
  3. Context
  4. Proposed solution
  5. Timeline

You can use this example as a template for writing your own, adding or removing sections as you see fit. Here are some pro-tips for writing an effective product spec:

Related templates

Character illustration