Define status categories

Choose a small number of labels with clear meanings, such as available, limited pilot, in implementation and planned. State the relevant customer or operating scope where availability is conditional. Ask the product and commercial owners to confirm the wording. Avoid labelling a feature live merely because a screen has been designed or a partner conversation has begun.

Keep the table maintained

Record the evidence date and a responsible owner for each row. Link major changes to an editorial update across the website, deck and sales materials. If a capability depends on another provider, describe the role and relevant conditions accurately. The table should make a sales or investment discussion easier by showing what can be demonstrated now and what still requires work. It is not a substitute for checking suitability for a particular customer.

Put the guide to work

Test the status table against a sales demonstration. If the team cannot show a capability labelled available, investigate the reason and narrow the scope where necessary. The evidence may support limited availability rather than a universal statement, which should be reflected in the published wording.

Imagine this

Hypothetical example

A platform’s introduction lists planned payment connectivity beside existing profile features. The team adds a status table separating current functionality from proposed integrations. Prospective partners can focus their questions on implementation dependencies without misunderstanding what customers can use today.

Make it practical.

Use this checklist as you read. Checks are not stored.

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.