Contact
Tell us what you’re trying to achieve
Share a little about your organisation and what you’d like to improve. We’ll review your enquiry and get in touch to talk it through.
Your project
Talk to us about your project
You don’t need a detailed specification to get in touch. A short description is plenty to start a useful conversation. If you can, it helps to tell us:
Please don’t include passwords, bank or card details, authentication codes or other sensitive personal information. The website’s forms and chat assistant do not ask for this information.
- Your current systemWhat software or processes you use today.
- The business problemWhat isn’t working, or what you’d like to improve.
- The number of usersRoughly how many people would use the system.
- The functionality you wantWhat the software should do.
- IntegrationsAny systems it needs to connect to, such as accounting software.
- TimeframeAny dates or deadlines you’re working towards.
- New or existing softwareWhether this is a new build or work on an existing system.
FAQ
Starting a project
How do we start a project with VC?
Send an enquiry using the form. We’ll review your enquiry and get in touch to arrange a conversation about your requirements. That conversation forms the start of the discovery (Understand) stage.
Do I need a detailed specification before contacting you?
No. Many projects start with a description of a problem rather than a specification. Part of our work is helping you define the requirements.
Can we start with a small part of a larger project?
Often, yes. Starting with a clearly defined first phase, such as one workflow, one integration or one report, can be a sensible way to deliver value early and build from there.
What information should I not send?
Please don’t include passwords, bank or card details, authentication codes or other sensitive personal information in the enquiry form or chat. The website’s forms and chat assistant do not ask for this information.
What happens during the discovery stage?
Discovery is the first stage of a project. The aim is to understand the organisation before any technology is designed. It typically covers how work currently flows, which systems are in use, where time is lost to manual steps or duplicated data, who needs access to what, and what a successful outcome would look like.
It is also where technical considerations are identified. Examples include whether existing systems provide APIs, the condition of any data to be migrated and how many people will use the system. The output is a clearer picture of the requirements and the potential scope, which can be used to agree sensible next steps. The depth of discovery depends on the size and complexity of the project.