Vanvora

No price list, and here is the honest reason why.

A number without scope would be dishonest, and a range wide enough to be true would tell you nothing useful. What we can commit to is the process, which is on this page in full.

Three shapes an engagement takes

Most clients start with the first and move to the second. The third is for businesses that want a partner rather than a project.

Where most people start

Automation audit

Anyone who suspects there is waste but cannot yet name it

A structured look at where your week goes, which of your tools are earning their keep, and what would pay off first. It ends in a written plan you can act on with us, with someone else, or on your own.

  • A working session covering your process end to end
  • A map of where work stalls, repeats or gets re-entered
  • A prioritised list of what to fix, in order of payback
  • An itemised quote for the first piece, if you want one

How it is priced

The first conversation and its written summary are free. A deeper assessment, for example a full data review before a migration, is quoted separately and stands on its own.

Book an automation audit

Fixed-scope build

A defined problem you want solved and handed over

We agree exactly what gets built and what it costs, then build it. The commonest shape: a first working version of a system covering your core record and the screens your day needs, delivered in usable pieces.

  • An approved scope with what is excluded named as clearly as what is included
  • A fixed written quote, itemised by module
  • Live progress visible in your portal throughout
  • Migration, training and a rehearsed cut-over
  • Source code and data handed over, documented

How it is priced

Quoted as a fixed price per module before work starts. The price only changes if you change the scope, and then only after a revised quote you approve.

Request a quote

Ongoing partner

Businesses improving continuously rather than once

A monthly arrangement covering support for what we have built plus an agreed amount of improvement work. Suits owners who want a technology partner on call rather than a project that ends.

  • Monitoring and support with an agreed response time
  • An agreed block of development time each month
  • Quarterly review of what to improve next
  • First call on our availability when something urgent lands

How it is priced

A flat monthly fee based on the support level and the block of time reserved. Not priced per user, and cancellable without losing your data or your code.

Talk about a retainer

What is always true, and what we will never do

These apply to every engagement regardless of size. They are the terms we would want if we were buying.

  • A free first conversation and a written summary you keep
  • A fixed written quote, itemised module by module, before work starts
  • A revised quote to approve before any scope change is billed
  • Your data exportable in a standard format, at any time
  • Documented source code handed over and owned by you
  • Running and hosting costs stated openly, not buried
  • Per-user licence fees that grow as your team grows
  • Lock-in through a proprietary format you cannot export
  • An invoice for work you did not approve in advance
  • A mandatory long-term support contract to keep what you paid for

What actually moves the number

If you want to estimate before speaking to us, these are the things that make a project bigger, in roughly the order they matter.

  1. 01

    How many distinct kinds of work the system handles

    One process done well is a small project. Five processes with different rules, owners and documents is five times the design work before any code exists.

  2. 02

    How much old data has to come across

    Clean data in one place is straightforward. A decade of history across three spreadsheets and a legacy system, with duplicates to resolve, is often the single largest line on a quote.

  3. 03

    How many other systems it must talk to

    Each integration is its own piece of work, and integrations with poorly documented or ageing software cost more than the licence of the tool they connect to.

  4. 04

    Whether people outside your team use it

    An internal tool has one set of users you can train. A client portal has strangers using it unsupervised, which raises the bar on security, clarity and error handling.

  5. 05

    How much of it needs to be configurable later

    Making a rule adjustable by you rather than fixed in code costs more up front and saves more over time. Worth it for the parts of your process that genuinely change.

The blueprint builder turns your answers to these into a phased module list, which is the same list we would quote from. It is the fastest way to get a real sense of scope without a meeting.

Questions about cost and commitment

Because a number without scope would be dishonest, and a range wide enough to be true would tell you nothing. What we can commit to is process: every engagement is quoted in writing, itemised by module, before any work starts. You approve the quote and the price does not move unless you change the scope, in which case you get a revised quote first.

No. A recurring per-user licence is exactly the model that punishes you for growing, and it is one of the reasons clients come to us. You pay for the build. Hosting and running costs are real and we are transparent about them, and ongoing support is optional and separate.

You keep everything. Your data is exportable at any time in a standard format, and the source code of what we built for you is yours, documented and handed over. We would rather earn the next piece of work than rely on you being unable to leave.

The first conversation and the written summary that follows it are free. If a deeper assessment is genuinely needed, for example a full data review before a migration, that is quoted separately and is useful on its own even if you go no further with us.

Get a real number for your actual situation.

Tell us what you are trying to fix and we will come back with an itemised written quote, or tell you honestly that you do not need us.