Is there a feature list for each package?

Yes and no. Each package has a fixed list of what’s included, like design, a prototype, analytics and launch support. What your product actually does isn’t on a list, because no two products are the same. Discovery sets those features with you.

Two kinds of “feature”

It helps to separate two things people mean by “features”.

• What the package includes. The work and the deliverables: user experience mapping, custom design, an interactive prototype, infrastructure, analytics, launch training. These are fixed per tier.
• What your product does. The screens, journeys and functions your users touch: booking a delivery, logging a workout, approving an invoice. These are yours, and they’re set in Discovery.

The pricing page lists the first kind in full. The second kind can’t be listed in advance, because we haven’t met your users yet.

What every package includes

Every tier starts with Starter’s list and adds to it.

Prices exclude VAT. The things a build needs to run, like hosting and store accounts, sit inside that price too. Our answer on how much a LaunchPad build costs breaks the number down.

Why your product’s features aren’t pre-set

A pre-set feature list is how you end up with a template. It also tempts founders to buy features because they’re on the list, not because users need them. Nobody’s first customer ever said, “I’d have signed up if only it had a dark mode.”

We’d rather start from the problem. In Discovery we map who uses the product and the one thing they must be able to do. Then we decide what earns a place in the first launch. Everything else goes on a “later” list.

That list of features becomes the scope you’re building against. It’s written down, in plain English, before the build starts. You read it, question it and agree it before any code exists.

How the tier shapes what fits

The tier doesn’t dictate your features, but it does set the size of the box. A Starter build has two months and one product surface. It suits one main journey done well.

If Discovery shows your must-have features need an app and a website, or several integrations, they won’t fit Starter. We’ll say so plainly, and show you what moving tier would add. Our guide to which package is right for you covers that choice.

What to bring to Discovery

You don’t need a feature list to start. It helps more to bring evidence: who your users are, what they do today and where it hurts. A rough prototype or notes from customer conversations are worth more than a wish list.

If you want to shape the package itself, see whether you can customise what’s included. Still deciding what your first version should do? Our guide to validating an app idea helps you work it out before you spend anything.