Software & appsBuild
Web application development
Web applications, client portals, dashboards, and admin tools built around how your business works.
Software that people sign in to and work with.
-
Web applications
Software that runs in the browser: people sign in, enter and change data, and complete tasks. A website mostly presents information; a web application is used to get work done.
-
Client portals
A private area where your clients sign in to see their own information, documents, or requests, instead of asking your team by email.
-
Dashboards
Screens that bring the numbers and statuses your team checks every day into one place.
-
Admin panels
Internal interfaces for managing records, users, and settings, with access limited by role.
-
APIs and integrations
Connections that let your application exchange data with other systems. Which integrations are needed is defined during discovery and in the scope.
-
Realtime features
Updates that appear without reloading the page, such as statuses or notifications, where the project needs them.
When custom software makes sense.
A custom web application makes sense when
- Your process doesn't fit the tools you can buy, or only fits with workarounds.
- Your team or clients need to sign in and work with shared data.
- Information has to move between systems you already use.
- You want software that follows your process and can change with it.
Understand the project before estimating it.
-
Step 1
Initial discovery call
A free conversation about the problem, the people who will use the software, and your current tools. You learn whether DEXVANE is a good fit and what the next step is.
-
Step 2
Paid discovery
For projects with significant uncertainty. It covers requirements, scope, architecture, integrations, and risks, and ends with an implementation plan and an estimate. Paid discovery costs $2,000, paid upfront.
Fixed scope, built in milestones.
Projects normally run with a fixed scope and agreed milestones. Projects with significant uncertainty go through paid discovery first. Timeline depends on project scope and requirements.
See how we workDiscover
The problem, the users, your current tools, and constraints.
Notes and next steps
Scope
Features, integrations, milestones, exclusions, timeline, and price, in writing.
Written scope and price
Design and build
Interface and architecture first, then development milestone by milestone, reviewed on staging where appropriate.
Revision rounds defined in the project scope
Test and launch
Code review and testing before production deployment, then go-live.
Working application and handover
Care
Support and changes after launch, as agreed.
Support, if you want it
Have a process that needs its own software?
Book a discovery callOwnership and rights.
Ownership and rights to project deliverables are defined in the project agreement. Client-owned accounts and access are used where appropriate. Open-source and third-party components remain subject to their own licenses.
A clear point of contact
Clients have a clear point of contact throughout the project, with written project updates. We work Monday–Friday, 9:00 AM–6:00 PM; communication with US clients is mostly asynchronous, with calls scheduled at an agreed time.
Reviewed and tested
Code review and testing before production deployment, including responsive behavior, key user flows, and basic accessibility checks. Where appropriate, changes are reviewed on staging first.
| Account | Owner |
|---|---|
| Code repository | You |
| Server or hosting | You |
| Domain | You |
| Application admin | You |
Every project gets a custom quote.
The initial discovery call is free. Paid discovery is for projects with significant uncertainty and is paid upfront.
The estimate follows discovery. You get a written price before work starts. Changes to scope are agreed in writing first.
What affects the price
- Features, screens, and user roles
- Integrations with other systems
- Data: how much exists, and whether it moves from another system
- Hosting and infrastructure requirements
- How much is still unknown at the start
Chosen for your project, documented for your team.
- Front end
- HTML, CSS, JavaScript, TypeScript, Vue.js, React
- Back end
- PHP, Laravel, Node.js, Go
- Databases
- MySQL, PostgreSQL
- Infrastructure
- Linux, Nginx, Docker, VPS
- Code
- Git, GitHub
Questions before you decide.
Do I own the code?
Ownership and rights to project deliverables are defined in the project agreement. Pre-existing code, reusable components, and libraries are covered separately in the agreement, and open-source and third-party components remain subject to their own licenses.
Why start with discovery?
An estimate is only as good as the understanding behind it. When much is still unknown, paid discovery defines the requirements, architecture, integrations, and risks first, so the implementation plan and estimate are based on facts.
How do you handle scope changes?
Changes to scope are agreed in writing first, with their effect on timeline and price.
How long does a project take?
Timeline depends on project scope and requirements. Milestones are agreed in the scope.
What happens after launch?
Post-launch support can be included or provided separately, depending on the project agreement. Server care is available through VPS & server management.
Fixed scope, built in milestones.
Tell us about the software you need.
We'll review your request and get back to you. Work starts after the scope and project terms are agreed in writing.