Sign inBook a demo

Pricing

Pricing shaped by your application landscape.

No two configurations are alike, so we quote after a short call about the scope you want documented. Here is how a proposal is built.

How pricing works

Three parts, each priced for what it covers.

  • One-time

    Setup

    Templates configured for your application objects and your standards, and the first documentation set generated and reviewed with your team.

  • Recurring

    Subscription

    The platform: extractions, regeneration, version and environment comparison, Ask your documentation, and user access for the period.

  • When needed

    Version upgrades

    Documentation updated around a version upgrade, with the baseline and the comparison your impact analysis needs.

What shapes a quote

Four questions we ask on the first call.

They are the same inputs the savings calculator uses, so you can prepare them in advance.

Open the savings calculator
  1. How many templates?

    One per kind of configuration you want documented: workflows, authorizations, data model, interfaces.

  2. Which environments?

    PROD alone, or PROD with UAT, pre-production and development.

  3. How many releases a year?

    Each release is a regeneration and a comparison.

  4. For how long?

    The subscription period that fits your programme.

From call to kick-off

How a proposal comes together.

  1. 01

    Discovery call

    Thirty minutes on your application landscape and what you need documented.

  2. 02

    Scope note

    A written summary of templates, environments and releases, for you to correct.

  3. 03

    Tailored proposal

    Setup, subscription and upgrade options, each priced separately.

  4. 04

    Kick-off

    Read-only access granted, templates configured, first documents generated.

Questions

Before you ask.

Why is setup priced separately?
Setup is the one-time work of fitting templates to your configuration and standards. Keeping it apart keeps the subscription a predictable, recurring cost.
Can we start with one template or one environment?
Yes. You can start with workflows on PROD, for example, and extend the scope at the next release.
Do you work alongside our integrator?
Yes. Docuvara gives your integrator and your internal team the same documentation to work from.

Get a proposal for your scope.

Tell us about your applications and their environments. We reply with a time for the discovery call.

Choose which cookies we may use. Essential cookies are always on: the site does not work without them.