Application & portal pricing
Plan application investment around users, permissions, business rules, integrations and a focused first release.
Define the first useful release
Start with who uses the product and what they must achieve. Identify the smallest coherent release that delivers that outcome.
Screens alone do not describe the work. A simple-looking form can involve identity, approvals, integrations and sensitive data handling.
Make complexity visible
List user roles, permissions, records, business rules and connected systems. Include migration, reporting and support expectations.
Describe mobile and offline requirements explicitly. A responsive web application and a dedicated native application are different delivery decisions.
Questions before a quote
What is essential at launch, and what can wait? Who approves requirements and supplies test data?
Who will maintain the system, handle incidents and own the accounts? Clear answers make scope and operating costs easier to compare.
Explore applicationsCompare the whole proposal
Check what is included, who supplies content and which integrations or migrations are in scope. Confirm tax, third-party charges and ongoing care separately.
A useful comparison covers deliverables, responsibilities, acceptance criteria and ownership—not only the headline price.
Delivery processProject questionsPrepare a useful brief
Describe the outcome, users, existing systems and constraints. Separate the essential first release from later improvements.
The planner lets you download a brief for the next conversation, but the brief is not a binding quote. When approved adapters are configured, it can submit that brief and continue to real consultation availability; no receipt or booking is claimed without provider confirmation.
Prepare your briefExplore VTECH pricing