Question 1

What does Vebryx do?

Accepted Answer

We design and build digital products: MVPs, custom platforms, web and mobile apps, and the brand and interface around them. Most of our work is taking an idea to something real people can use.

Question 2

How do I start a project with you?

Accepted Answer

Book the free 30-minute strategy call. We'll talk through your idea, what you're trying to prove and what it would take to build, and you'll leave with a plan whether or not you work with us.

Question 3

What happens on the first call?

Accepted Answer

Questions, mostly ours. We want the problem, the people you're building for and the outcome you need. If we're a fit, we follow up with scope, cost and a timeline.

Question 4

Do I need a finished spec before we talk?

Accepted Answer

No. A paragraph and a rough idea of who it's for is enough. Turning that into a scope is part of what we do.

Question 5

Do you work with non-technical founders?

Accepted Answer

Most of our clients are non-technical. We explain trade-offs in plain terms and never ask you to pick a database.

Question 6

Can you take over a product someone else started?

Accepted Answer

Often, yes. We'll review what exists first and tell you honestly whether it's better to continue it or rebuild the parts that are holding you back.

Question 7

Do you work with clients outside the UK?

Accepted Answer

Yes. We're based in Glasgow and work with founders elsewhere over calls and shared documents; the process doesn't change.

Question 8

How do I know whether to build an MVP or the full product?

Accepted Answer

If any important assumption is still a guess, build the MVP. If the demand is proven and you're solving a known problem, going straight to the full build can be the cheaper route.

Question 9

How much does an MVP cost?

Accepted Answer

It depends on the features, the platforms and the pace. The MVP cost calculator gives you a range in a couple of minutes, and the call turns that into a firm number.

Question 10

How accurate is the cost calculator?

Accepted Answer

It's a planning range, not a quote. It's built from what we've charged for similar work, but the final figure comes after we've scoped your project properly.

Question 11

Why do estimates vary so much between agencies?

Accepted Answer

Mostly scope and seniority. A cheap quote usually means fewer features, less testing or a junior team; ask anyone quoting you what's excluded.

Question 12

What's included in the price?

Accepted Answer

Design, development, testing and launch of the scope we agree. Third-party costs like hosting, payment processing or paid AI usage sit outside it.

Question 13

Do you charge fixed price or by the hour?

Accepted Answer

We price the agreed scope, so you know the figure before we start rather than watching a meter run.

Question 14

How are payments scheduled?

Accepted Answer

Payment terms are set out in the proposal and tied to milestones, so nothing is due before you've seen progress against it.

Question 15

What happens if the scope changes mid-project?

Accepted Answer

We tell you what it costs in time and money before anything is built, and you decide. Small changes usually absorb; new features are quoted.

Question 16

Are there ongoing costs after launch?

Accepted Answer

Hosting, domains and any paid services your product uses are billed by those providers. Ongoing development or support is optional and agreed separately.

Question 17

Do you offer payment plans?

Accepted Answer

Milestone payments already spread the cost across the project. If you need something different, raise it on the call and we'll tell you straight whether it works.

Question 18

How quickly can you launch?

Accepted Answer

A validation MVP takes 2–4 weeks. Larger platforms are usually around 8 weeks, depending on scope.

Question 19

What are the stages of a project?

Accepted Answer

Eight: Ignition, Compass, Pillar, Canvas, Forge, Bridge, Sentinel and Everest — idea and research, then planning, design, build, integrations, QA and launch.

Question 20

What do you need from me during the build?

Accepted Answer

Decisions, quickly, and access to anyone who knows your users. An hour a week of your time is typical; slow decisions are the usual cause of slow projects.

Question 21

How often will I hear from you?

Accepted Answer

Weekly at minimum, with something to look at rather than a status update. You'll have a direct line to the people building it.

Question 22

Can you work to a fixed launch date?

Accepted Answer

Yes, provided the scope can move. Fixed date and fixed scope at the same time is where projects go wrong.

Question 23

What if I need it faster?

Accepted Answer

We can put more people on it, which costs more per week but shortens the calendar. The calculator's pace options show the effect.

Question 24

Do you work in sprints?

Accepted Answer

We build in short cycles with something reviewable at the end of each one, so you're never waiting weeks to see where the project is.

Question 25

What usually slows a project down?

Accepted Answer

Waiting on content, waiting on access to a third-party system, and mid-build changes of direction. We flag all three early.

Question 26

Can we start before everything is decided?

Accepted Answer

Yes. We start with the parts we're sure of and design the rest so that later decisions don't force a rebuild.

Question 27

What exactly is an MVP?

Accepted Answer

The smallest version of your product that tests the assumption your business depends on. Not a demo, not half a product — something real users can complete a real task with.

Question 28

How do you decide what goes into the first version?

Accepted Answer

We work back from the assumption you need to test. Anything that doesn't help prove or disprove it waits for version two.

Question 29

What if the idea doesn't validate?

Accepted Answer

Then you've saved the cost of building it. That's the point: we'd rather kill a bad idea in week two than bill you for six months of it.

Question 30

Do you do research before building?

Accepted Answer

Yes. Understanding the users and the existing alternatives is part of the early stages, not an optional extra.

Question 31

Can you help us get the first users?

Accepted Answer

We've run waitlist and launch campaigns alongside builds — Infinite Running League had over 1,000 sign-ups before any code was written.

Question 32

Is MVP code throwaway?

Accepted Answer

Not the way we build it. It's a smaller product, not a worse one, and it's built so the next version extends it rather than replaces it.

Question 33

What is “Kill my idea”?

Accepted Answer

A free stress test. You describe the idea, we aim at the customer, the alternatives, the differentiation, the scope and the risks, and tell you what to validate first.

Question 34

Do you design as well as build?

Accepted Answer

Yes. UI/UX design and prototyping are part of the process, and we also do brand and identity work when a product needs one.

Question 35

Will I see designs before development starts?

Accepted Answer

Always. You get a clickable prototype to walk through, so changes happen in design where they're cheap.

Question 36

Do you follow our brand or create one?

Accepted Answer

Either. If you have brand guidelines we work inside them; if you don't, we can create the identity alongside the product.

Question 37

Can you test the design with real users?

Accepted Answer

Yes, that's what the prototype is for. Watching a handful of people use it before we build is the cheapest research there is.

Question 38

What do you design in?

Accepted Answer

Figma, with Framer and Maze alongside it for prototyping and testing.

Question 39

Is the product accessible?

Accepted Answer

We build to sensible accessibility standards — contrast, keyboard use, screen-reader labelling — as a default, and we can go further if you're held to a specific standard.

Question 40

Do we get the design files?

Accepted Answer

Yes. The design files are yours along with the rest of the work.

Question 41

What do you build with?

Accepted Answer

React and Next.js on the front end, Node, Python or .NET on the back end, PostgreSQL or MongoDB for data, hosted on AWS, Google Cloud, Azure or Vercel. Flutter and React Native for mobile.

Question 42

Who chooses the stack?

Accepted Answer

We recommend, you decide. The choice follows what the product needs and what your team can maintain, not what's fashionable.

Question 43

Do you build mobile apps?

Accepted Answer

Yes, for iOS and Android. Whether you need one on day one is a different question, and often the answer is no.

Question 44

Web app or mobile app first?

Accepted Answer

Web first, usually. It's faster to build, easier to change and there's no app store review between you and your users.

Question 45

When do you use low-code or no-code?

Accepted Answer

When speed matters more than a custom build — internal tools, simple marketplaces, storefronts. We use Shopify, Webflow, Bubble, Softr and automation tools like Zapier, Make and n8n, and we'll tell you when custom code is the better call.

Question 46

Can you integrate with the systems we already use?

Accepted Answer

Yes. Payments, CRMs, email, maps, analytics and internal APIs are routine; integrations are a stage of our process, not an afterthought.

Question 47

How do you handle security?

Accepted Answer

Roles and permissions, sensible authentication, encrypted connections, and access limited to what each user needs. If you're handling sensitive data, tell us early so it shapes the architecture.

Question 48

How do you test?

Accepted Answer

Quality assurance is its own stage: we test across devices and browsers, and fix what we find before launch rather than after.

Question 49

Will it handle growth?

Accepted Answer

We build the foundation to scale from the start, so the first version doesn't have to be thrown away when traffic arrives.

Question 50

What can you actually build with AI?

Accepted Answer

Assistants that answer from your own content, generated copy and images, document and data extraction, search that understands intent, and automations that remove manual steps.

Question 51

Can you add AI to our existing product?

Accepted Answer

Yes. That's most of this work: integrating models into a product that already exists rather than starting again.

Question 52

Which models do you use?

Accepted Answer

Whichever fits the job — Claude, OpenAI and Gemini models, with LangChain and Hugging Face tooling around them. We'll weigh accuracy, speed and cost per use before recommending one.

Question 53

Is our data used to train someone else's model?

Accepted Answer

Not with the enterprise and API arrangements we build on, where training on your data is off by default. We confirm the terms of whichever provider you choose before we wire it in.

Question 54

How do you keep AI answers accurate?

Accepted Answer

Ground them in your own content, constrain what the model is allowed to answer, and show sources where it matters. We also test the awkward questions, not just the easy ones.

Question 55

What does an AI feature add to the cost?

Accepted Answer

The build cost is in the calculator; the running cost depends on usage and the model you pick. We'll size both before you commit.

Question 56

Should my MVP have AI in it?

Accepted Answer

Only if it's doing real work for the user. AI that's there to be mentioned in the pitch deck adds cost and risk without adding value.

Question 57

What happens at launch?

Accepted Answer

We deploy, monitor it, and stay close for the first stretch of real usage — that's the Everest stage of our process.

Question 58

Do you provide hosting?

Accepted Answer

We set it up and can manage it for you. The hosting itself is billed by the provider, so you keep ownership of the account.

Question 59

What if we find a bug after launch?

Accepted Answer

Tell us. If it's something we built and it isn't doing what we agreed, we fix it.

Question 60

Do you offer ongoing support?

Accepted Answer

Yes, as an ongoing arrangement agreed separately. Plenty of clients keep us for a few days a month; others take it in-house.

Question 61

Can our own developers take it over?

Accepted Answer

Yes. We hand over the code, the accounts and the documentation, and we'll walk your team through it.

Question 62

Do we get the source code?

Accepted Answer

Yes. The product and the code we write for it are yours.

Question 63

Can you keep building after launch?

Accepted Answer

That's usually the plan. The first version teaches you what to build next, and we'll keep going for as long as it's useful.

Question 64

Where are you based?

Accepted Answer

Glasgow, at 40 Plantation Square. We work with clients across the UK and beyond, and we're happy to meet in person if you're nearby.

Questions,answered straight.

Getting started

Pricing & payments

Timelines & process

MVPs & validation

Design & brand

Development & technology

AI

Launch, support & handover

Working together

Industries & fit

Still have a question?