Skip to content
Start a project
DeliveryHow we workSoftware for business1 Nov 20263 min read

How long a software build takes, and what moves the date

Our published planning windows, why they are ranges, and the factors that push a date later. An honest note from a studio with no delivery history to quote.

Valentir Engineering Desk

Architecture diagram: How long a software build takes, and what moves the date

As a planning range, a marketing site takes three to six weeks, a mobile app eight to fourteen, and custom software ten to twenty. Business systems and integration work is scoped per engagement, so it has no published window. These are the ranges in the FAQ, and they are planning ranges, not promises. The process page shows how a project moves between them.

Where the ranges come from#

Honestly: from the way we plan, not from an average of delivered projects. The studio was founded in 2026 and this site does not publish a delivery history, so there is no median of past builds to quote. The price list also gives no weeks. The windows are the site's own planning model, shown as a note and never as a charge.

What you do get is a date in the proposal. If it is ever at risk, we renegotiate it early instead of missing it quietly.

What moves the date#

The same model sits behind the estimator. Each of these adds time:

  • the number of screens, which is the largest single factor;
  • the number of kinds of user, because each is a separate set of screens and permissions;
  • a mobile app on top of a web one;
  • payments;
  • how many other systems it must talk to, such as WhatsApp, an accounting package, a shipping provider or an existing ERP;
  • an admin panel;
  • AI features.

The estimator asks only what is being built, how big and how soon, and works out the rest from those answers. Each "not sure yet" widens the range, because uncertainty about scope is the first thing that moves a date.

Dates follow events, not the calendar#

Payments in a package fall due on events, not on dates: the deal is signed, the design is approved, the build is delivered for testing, acceptance is signed. A date on a project therefore depends on how quickly those reviews happen as much as on how fast the build goes. A design waiting a fortnight for approval is a fortnight on the date.

MVP or full build#

These are different questions, not two sizes of the same answer. An MVP exists to test the riskiest assumption with the least built: core features only. A full build assumes the assumption has already been tested. The packages on the pricing page are named for that difference.

If you are not sure which you need, say so. Our FAQ answer to "Do you work with startups?" is that we will not take a cheque for a full build when the honest answer is a landing page and some customer conversations first. The cost guide goes through what drives the price.

What this does not tell you#

It cannot tell you how long your project will take. That needs a written scope. A note on how the estimator is built explains why its ranges are wide on purpose. Valentir Technologies LLP is a software studio in Noida, and the contact page is where a scope starts.

Get our notes by email

We email our notes when we publish something worth your time.

We use your email only to send these notes, when we publish something worth your time. How we handle it is on our privacy page.

Search on Google and want more notes like this in your results? Add Valentir as a preferred source on Google.

If you want to argue with any of this, that is what hello@valentir.in is for.

Start here

Tell us what you want to build.

One call, a deterministic technical scope, and a 100% fixed price. From architecture to launch, we engineer software that drives real business results.

Contact UsChat on WhatsApp