Number of Seats/Users: d.velop process studio offers discounts based on the number of users or seats. A higher volume typically leads to a better discount structure, especially for enterprise-level usage.

Commitment to a Long-Term Contract: Discounts are often provided to companies that commit to using the service for a longer period (e.g., 1-year or 3-year contracts). A longer commitment shows d.velop process studio that the company is serious and willing to invest in the platform long-term.

No Active Discounts: Companies that are not already receiving other active discounts may have a better chance of qualifying for additional discounts from d.velop process studio. d.velop process studio reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: d.velop process studio offers discounts if you agree to a minimum amount of usage or transaction volume. This could be based on data storage, transactions, or other metrics tied to how much you will use the platform.

Enterprise-Level Negotiation: Companies that qualify as “enterprise” due to their size or complexity (e.g., having large teams, multiple departments, or geographical presence) may be eligible for additional discounts from d.velop process studio. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: d.velop process studio often offers discounts if you renew early or prepay for the entire contract period. This is a common approach to securing a lower price.

Here at Spendbase our internal data shows that d.velop process studio is seen by our clients as a powerful and evolving automation platform, with a few usability gaps that matter for adoption and training budgets.

Key positives our Spendbase clients highlight:

• Strong fit with existing d.velop stack
• Direct integration with d.velop documents is a major win.

• Can also be used without d.velop documents, which increases flexibility.

• High flexibility and automation potential

• Clients report they can “basically build almost anything” they imagine in terms of workflows.
• Good coverage of end‑to‑end process automation, from form capture to storage.

• Clear potential to increase automation level and reduce manual work.

• Accessible no/low‑code approach

• Form creation is described as much more user‑friendly than older tools (e.g., decs.forms, flow manager).
• Non‑IT staff can now build modern forms and processes, at least with some guidance.

At the same time, our internal data shows recurring friction points that can impact time‑to‑value and training costs:

• Learning curve and usability
• Steep learning curve, especially for non‑technical users.
• Not yet at true “citizen developer” level; many settings feel unintuitive.

• Some clients are only at the start of their journey and expect a longer onboarding phase.

• Missing or immature features

• No or limited event-based triggers for starting processes (though clients see this on the roadmap).
• Lack of version control for processes and scripts.

• No way to organize/sort topics and scripts, which becomes painful at scale.

• Troubleshooting and error handling

• Error diagnostics in workflows are seen as weak.
• When something breaks, it is hard to see where and why.
• Small UX issues (e.g., auto-scroll after saving a script) slow down daily work.

Overall sentiment from Spendbase clients:

• Product is rated positively, often 4–5 stars, with clear recognition that it is improving over time.
• Clients are optimistic about the roadmap and expect many current gaps to be closed.
• For budgeting and discount discussions, this means:
• Strong long‑term value if you commit to using it broadly.
• You should factor in initial training, governance, and possible need for power users.
• There is a good case to negotiate based on the missing enterprise features (versioning, organization, debugging) if those are critical for your use case.