How we work
Every engagement starts with a diagnosis.
A 30-minute conversation about your product. If we’re the wrong fit, we’ll say so.
We’ll remember your birthday. And your launch date. And your tech debt.
Working with us should feel like adding a few very senior people to your team, not hiring a vendor. We join your channels and your rituals, and we celebrate the small wins with you.
-
“There was a genuine trust between our team and the VGV team. I speak for everybody; we did not think there was a VGV and a Nav team. There was one team.”
Head of Product, Nav Zain Kahn -
“Our teams bonded in a way I’ve never seen with an outside agency.”
Director of Engineering, Slickdeals Christopher Gulliver -
“VGV is very adaptable. They do things we don’t even ask. Their team says ‘Here is some value we can provide, can we do this?’ and it’s great.”
Director of Global Product Management, Universal Destinations & Experiences Mikal Wessel -
“The VGV team created an unprecedented experience for Hamilton fans and has been a trusted partner since 2017. There’s no better team to help us give our fans incredible ways to connect with the show.”
CEO, Marathon Digital & Hamilton Marketing Mike Karns
You’ll leave every meeting knowing exactly what happens next.
Before we recommend an architecture, a migration, or a generative screen, we find out what decision is on your desk and what it costs if nothing changes. Sometimes the honest answer is that you don’t need us yet. We’ll tell you that too.
- Today
A reply from a person
One of our unicorns reads your message and picks a time with you, usually the same day.
- Week 0
A 30-minute call
Bring the app, the repo, or just the idea, and tell us if a launch date is coming. We’ll ask about your roadmap and your team. You’ll leave knowing whether we’re the right team.
- After the call
A written recommendation
What we heard, what we’d do first, who from our side would do it, and how the work would be priced. One recommendation, not a menu. If we’re not the right fit, it says so and names who might be.
- The first weeks
Pick a starting point
Once the first piece of work is in your hands, you get our recommendation for what comes next: what to build, who on our team would build it, and how it would be priced. If we’re the wrong team for it, we’ll say so.
A few things we do on every engagement.
We write these down as policy so you don’t have to negotiate them.
- 01 The price is agreed before we start, and it’s tied to the outcome, not the time it takes.
- 02 The scope is written down and signed by both sides. If it has to change, we tell you before any work starts.
- 03 Every engagement has a named senior owner, and you’ll always know who to call.
- 04 You get the project tracker, repo access, and a written record of every architecture decision.
- 05 We recommend one option and tell you why.
- 06 You own everything we build, including code, designs, and documentation.
Everything your procurement team will ask for, on one page.
Send this page to whoever needs to approve it. That’s what it’s for.
- Security
- SOC 2 Type II. The report is available under NDA. Security & IP
- IP
- You own the code and the IP from the first commit.
- AI in delivery
- AI tooling runs inside your repository and under your access controls.
- Pricing
- Scope and price agreed before kickoff, based on the work, not hours.
- Proof
- Real clients, in their own numbers. Outcomes
What teams ask before the first call.
Short answers to what most people ask first. Anything else, bring it to the call.
01 Do we need to share our code before the first call?
No. Bring the repo if you can share it. If you can’t yet, bring the app, and tell us if a launch date is coming.
02 When do we see a price?
In the written recommendation that follows the call. It sets out what we would do first, who would do it, and how it would be priced.
03 What if VGV is the wrong team for this?
Then the recommendation says so and names who might be the right one.
04 Who is accountable on your side once work starts?
A named senior owner. Every engagement has one.
05 Can we start with a single piece of work?
Yes. Design Systems and the AI & Strategy Workshops each stand on their own.
06 How long do the first weeks run?
On a Flutter migration, the first step runs three weeks and puts a running Flutter slice inside your native app.
We’ll care about your success as much as you do.
Our unicorns read every message and reply, usually the same day.
Start the conversationA 30-minute call about what you’re building.