Clear answers.
Before you commit.

Our main focus is established small and midsize businesses improving their operations. We also help founders define and build a practical first release. Our experience spans finance, retail, services, and manufacturing.

No. Describe what happens today, what is difficult, and what you want to improve. We help work out whether to buy, configure, connect, automate, or build.

Yes, when it fits the need. Custom software should earn its cost through a clear business benefit. We compare the practical alternatives, including improving a process without a new system.

Yes. It starts the conversation and helps identify the problem. A preliminary estimate is not a binding quote. If detailed planning is needed, we explain the paid proposal, price, and deliverables before you decide.

Once we agree the deliverables, your implementation price is fixed. If the agreed work takes us longer than expected, we absorb that delivery overrun. Additional requirements are discussed and approved separately.

We agree together what information, access, and feedback the project needs, and when. If something is delayed, we explain the impact, keep unaffected work moving where possible, and agree revised dates. Any additional work or cost needs your approval.

Yes. We can often trade priorities within the agreed scope. If a change adds work, we explain the cost and schedule impact before you decide. Fixing work that fails the agreed acceptance criteria is our responsibility.

It is a reviewed planning deliverable: requirements, recommended options, a delivery approach, assumptions, and estimates. The implementation credit and its conditions are set out before purchase. Buying a proposal does not commit you to implementation.

Your quote separates the implementation price from hosting, subscriptions, AI usage, and optional ongoing support. It also states included warranty and handover terms, currency, taxes, and payment milestones.

We agree a schedule after understanding the scope, dependencies, and available capacity. Working increments let you give feedback along the way. We do not promise the same delivery time for every project.

Most work happens through written questions, shared briefs, and progress updates. You can review and reply on your schedule, and decisions remain easy to find. If a conversation is useful, we agree it together and confirm the outcome in writing.

DVM remains responsible for the work. We use automation to assist analysis and delivery; a responsible person approves scope, commercial commitments, and release. Automated output is not customer approval.

Start with a high-level description. We can arrange an NDA before sharing sensitive details, and agree what information and access the work needs. Do not include passwords, credentials, or confidential records in an initial inquiry.

Yes. Tell us about those requirements early so we can agree suitable tools, access, and data handling before the work starts. Restrictions may change the delivery approach and quote.

You own your project data. Your working solution and agreed documentation are included, while DVM retains its software intellectual property. Source code is an optional, separately priced handover package, with licence rights to modify the solution, work with other developers, and commercialize it. Your quote explains the source option, applicable third-party licences, hosting, support, and handover before you commit.

We agree handover, warranty, maintenance, and support responsibilities before implementation. You can choose a defined ongoing service or a handover arrangement that fits your team and licence.