What people ask us before they hire us

Send us a short description through the contact form, or email info@v6cube.com. The steps above show what happens after that.

Start with the problem you want to solve, who will use the software, and any deadline or budget limit. Screenshots help, and so does a list of the systems it must connect to or products you admire. Don't worry about the rest. We work that out with you during discovery.

That's common, and it's a perfectly good place to start. Discovery turns your idea into a list of features, users and technical needs before anyone commits to a budget.

Usually within one to two weeks of you agreeing the plan.

Yes. We're happy to sign a confidentiality agreement, often called an NDA (non disclosure agreement), before you share anything sensitive.

Yes. We work with young businesses building their first product and with established organisations modernising older systems. We size the team to fit the work, not the other way round.

It depends on how many features and types of user you need, what it connects to, which platforms it runs on (web, iOS, Android), your security needs and the size of the team. After discovery, you get a fixed written estimate. Our guide on how much custom software costs walks through each of these.

With a fixed price, you pay one agreed cost for an agreed scope. That works well when the project is clearly defined. With time and materials, you pay for the time actually spent. That suits work where priorities shift, and it's how dedicated teams are usually billed. Our page on software development engagement models compares them in detail.

Yes, for the scope we agree. If you want something beyond it, we estimate that separately and agree it with you before any extra work starts.

Yes. The first consultation costs nothing, and you're under no obligation to carry on afterwards.

That's fine. Choose "not sure yet" on our contact form and we'll suggest realistic options, such as starting with a smaller first version.

No. A fixed project contract lasts as long as the project does. Dedicated teams and support plans carry on over time, but they come with regular review points, so you're never locked in for years.

It depends on the scope, the systems it connects to and the platforms it runs on. You get a realistic timeline along with your fixed estimate. We build in sprints (two week cycles), so you see working software early on. Our software development process page walks through each stage.

Our teams cover 24 time zones, so the people on your project share working hours with you. Meetings happen during your day and written updates fill the gaps. Every sprint ends with a demo, so you can see progress for yourself.

Your delivery lead. They look after the plan, the schedule and the reporting, with the engineers, designers and testers on your project behind them.

Usually a few hours a week for demos, check ins and decisions. It helps to have one person on your side who can make the call when a decision is needed.

Yes. You can reorder priorities at the start of each sprint. If a change adds to the scope, we cost it and agree it with you first.

We stick to proven, widely used tools. Most often that means React for the screens, Node.js for servers and APIs (the connections that let systems share data), PostgreSQL for databases, and AWS or Azure for hosting. If you already have tools you like, we can work with those instead.

You do. All the code and designs belong to you, and you get full access to the version control repository (a store that records every change ever made).

Only your project team gets access, and each person's permissions match their role (this is called role based access). Your data is encrypted at rest (when stored) and in transit (when sent). Where we can, we test with sample data instead of the real thing.

Yes. Every change is reviewed and checked against the OWASP Top 10, a widely used list of the most common web security risks. If you need deeper checks, look at our application security services, including penetration testing.

Yes, whenever you like. You own the code, and we document the system as we build it, so another team can pick it up without starting from scratch.

We never sell or rent it, and we use it only to deliver your project. A few service providers handle some of it for us, such as our web host, Google Analytics if you accept it, and WhatsApp if you message us there. Our privacy policy has the full details.

Yours. Hosting, domain and app store accounts sit in your company's name, or we work inside the ones you already have, and you hold the logins. Nothing is left in our name, so you can move on whenever you choose.

Yes. Most clients move on to a care and support plan once they launch. Our software maintenance and support service page explains what a plan includes.

We monitor your software, fix bugs, apply security patches, keep libraries and frameworks up to date and make small improvements. Each month you get a summary of what we did.

We reply within one business day, and urgent problems on a live system go to the front of the queue.

Often, yes. First we look over the code, the hosting and whatever documentation exists. Then we agree an honest plan with you.

Yes. We review plans regularly, so the level of care keeps pace with your users. If you also want new features built, a dedicated development team may suit you better.

Yes. We start by reading through the code, the tests and how it's hosted. Then we tell you plainly whether to build on it or rewrite the parts that hold it back, and you get a plan and an estimate before we change anything. Custom software development covers the build from there.