Process
How we work
Every step ends with something you can review. Work starts after the scope and project terms are agreed in writing.
From the first call to care after launch.
Timeline depends on project scope and requirements.
Discover
Goals, current setup, constraints.
Notes and next steps
Scope
Deliverables, timeline, and price.
Written scope
Design and build
Reviewed on staging, where appropriate.
Review link
Test and launch
Testing, go-live, and handover.
Handover notes
Care
Maintenance, support, and growth.
Care plan, if you want one
Understand the project before estimating it.
-
Every project
Initial discovery call
A free conversation about what you need and how things work today. You learn whether DEXVANE is a good fit and what the next step is.
-
When much is still unknown
Paid discovery
For projects with significant uncertainty, such as web applications. It covers requirements, scope, architecture, integrations, and risks, and ends with an implementation plan and an estimate.
Agreed in writing before work starts.
Changes to scope are agreed in writing first. Revision rounds are defined in the project scope.
Written agreement
A written agreement is in place before paid work begins.
Project scope
Each project has its own scope: deliverables, technology, milestones, price, payment terms, timeline, revisions, client responsibilities, and acceptance criteria.
NDA
NDA available on request.
Practices you can check before you sign.
Written into the scope and contract on every project.
Clear scope
Deliverables, exclusions, timeline, and price in writing before work starts.
Ownership and access
Ownership and rights to project deliverables are defined in the project agreement. Client-owned accounts and access are used where appropriate.
One point of contact
A clear point of contact throughout the project, and written project updates.
Documented work
Handover notes, access lists, and a record of what changed.
Reviewed and tested
Code review and testing before production deployment. Where appropriate, changes are reviewed on staging first.
Support after launch
Post-launch support can be included or provided separately, depending on the project agreement.
Reviewed and tested before launch.
Before production deployment
- Code review
- Responsive behavior on phones, tablets, and desktops
- Main user flows
- Basic accessibility checks
- Errors and critical issues
Along the way
- Where appropriate, changes are reviewed on a staging environment before production deployment.
- Accessibility is considered during design and development.
- Accessibility checks are performed against relevant WCAG guidance.
Remote-first, with a clear point of contact.
Working hours: Monday–Friday, 9:00 AM–6:00 PM.
One point of contact
Clients have a clear point of contact throughout the project.
Written updates
Written project updates throughout the project.
Across time zones
Communication with US clients is mostly asynchronous, with calls scheduled at an agreed time.
New requests
We'll review your request and get back to you.
You get a written price before work starts.
The model depends on the service. Published starting prices and plan prices are on each service page; the final price is set in the written scope.
-
Fixed-scope projects
Websites, redesigns, and web applications run with a written scope and price; web applications are usually built in agreed milestones. See custom websites and web applications.
-
Fixed-scope services
A defined result with a price agreed before work starts, such as a technical SEO audit or a website migration.
-
Monthly plans
Plans for website maintenance and server management, with support during business hours.
-
Ongoing growth work
Monthly SEO and Google Ads management based on an agreed scope. No one can guarantee rankings or leads.
-
Paid discovery
For projects with significant uncertainty: requirements, architecture, integrations, and risks first, then an implementation plan and an estimate.
What you receive at handover.
Handover notes, access lists, and a record of what changed. What exactly is handed over is defined in the project agreement.
- Source code repositoryAccess as defined in the project agreement.
- Accounts and accessClient-owned accounts and access are used where appropriate.
- Access listAn access list and notes your team or any developer can use.
- Handover documentationHow to edit, what was built, and what changed.
- Post-launch supportIncluded or provided separately, depending on the project agreement.
Launch is the start, not the finish.
Post-launch support can be included or provided separately, depending on the project agreement.
- LaunchHandover as defined in the project agreement.
- MaintenanceUpdates, daily backups, monitoring.
- SupportFixes, changes, migrations, servers.
- GrowthSEO and Google Ads, in client-owned accounts where appropriate.
Support hours: Monday–Friday, 9:00 AM–6:00 PM. We don't offer an emergency or out-of-hours service. See plans
Questions before you decide.
Do I own the code?
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.
Do you sign an NDA?
NDA available on request.
How long will my project take?
Timeline depends on project scope and requirements. It is part of the written scope you agree before work starts.
How do you work across time zones?
We are remote-first and work Monday–Friday, during DEXVANE business hours. Communication with US clients is mostly asynchronous, with calls scheduled at an agreed time. You have a clear point of contact throughout the project and written project updates.
Is support included after launch?
Post-launch support can be included or provided separately, depending on the project agreement. Ongoing care is available under a maintenance plan.
Agreed in writing before work starts.
Tell us about your project.
We'll review your request and get back to you. Work starts after the scope and project terms are agreed in writing.