How a WavX Project Runs: First Call to Launch

Description

Company How a WavX project runs, from first call to launch

A WavX project starts with a free consultation and a written quote, then runs in four stages: discovery, design, development, and launch and support. You see wireframes and a Figma prototype before code is written, and regular demos while it is built. The client owns the source code and IP WavX ships.

Talk to a technology expert Last updated 2 October 2026

Before the project: consultation and quote

The first conversation is a free consultation. After it, WavX sends a customised quote with fixed-price, time-and-materials or hybrid options. The engagement models page explains when each one fits, and the pricing page explains how the numbers are reached.

The consultation goes faster if you send a short brief first. The project brief template lists what to include. A Figma design, a sketch or a reference website is also a good starting point.

The four stages

Stage

What happens

What you see

1. Discovery

WavX maps your goals, users, workflow and constraints

A defined scope, an architecture and a roadmap

2. Design

Screens are designed before any code is written

Wireframes and an interactive Figma prototype you can review and shape

3. Development

The software is built in short cycles, with continuous integration and quality checks

Regular demos of working software

4. Launch and support

The software is deployed on cloud infrastructure

A live product, then monitoring, maintenance and further iterations

Discovery is where the scope is fixed. WavX maps how your business works today, who will use the software and what limits apply, then writes down the scope, the architecture and the roadmap. Everything later is measured against this, so it is worth your time to read it closely and correct it.

You see the product as wireframes and an interactive Figma prototype before a line of code is written. This is the cheapest point at which to change your mind. If you already have a Figma design, WavX builds from it.

The build runs in agile cycles with continuous integration, quality checks and regular demos. A team of engineers, designers and strategists works on the project. Larger builds run to milestone-based timelines, so you can see whether the project is on schedule without having to ask.

WavX deploys on AWS, Google Cloud or Azure. After go-live the work continues as monitoring, maintenance and new features. See support and maintenance for what that includes.

Typical timelines

These are the timelines WavX publishes. The quote for your project states its own.

Project

Typical duration

Simple website

4–6 weeks, or as little as 7 days for a focused build

Mobile app

2–4 months

Complex e-commerce or ERP/CRM platform

3–6 months

WavX does not publish a fixed duration for each stage, because the split depends on the project. A build that starts from a finished Figma file spends little time in design; a business system with many workflows spends more in discovery.

What is set in your proposal, not on this page

Some terms differ by project and are written into the proposal, not published here:

the payment schedule

how a change to the agreed scope is handled and priced

who your point of contact is, and how often demos happen

what support covers after launch

If any of these is missing from a proposal you receive, ask for it before you sign.

What stays the same on every project

You own 100% of the source code and intellectual property WavX ships.

WavX is reachable Monday to Saturday, 10:00 AM to 7:00 PM IST.

Work is custom-built in the stack WavX uses , not on templates.

When this process is more than you need

A one-page site or a standard online store on a hosted platform does not need discovery and a prototype. A site builder or a ready-made theme is cheaper and faster, and that is the right choice when your requirements are standard. This process pays for itself when the software has to match how your business works, hold your data, or connect to other systems.

Frequently asked questions

How long does a project take?

A simple website typically takes 4–6 weeks, or as little as 7 days for a focused build. Mobile apps take 2–4 months, and complex e-commerce or ERP/CRM platforms 3–6 months, depending on requirements. Your quote states the timeline for your scope.

Can you start from my Figma design or a reference website?

Yes. If you have a Figma file, a sketch or a reference website, we build from that and reproduce it in production code. Share it before the consultation so the quote reflects it.

Will I see the product before it is finished?

Yes. The design stage produces wireframes and an interactive Figma prototype before any code is written, and the development stage includes regular demos.

Who owns the code at the end?

You do. The client owns 100% of the source code and intellectual property WavX ships.

What happens after launch?

We offer post-launch support: performance monitoring, security updates, feature enhancements and emergency assistance. The support and maintenance page explains what that covers and what it costs as a planning range.

Related

How WavX prices a project

Fixed price, time and materials, or hybrid

Support and maintenance after launch

The technology WavX builds with

Build your own software — your way, your pricing.

WavX Solutions is here to create your own software in a fully custom way, built exactly how you work — with a pricing model that fits your business. Connect now and let's build it.

Contact Now helpwavx@gmail.com