TechOvelpo

One price for a defined scope

Fixed-Price Software Projects

When the scope is clear, you should know the cost before work starts. Our fixed-price projects are built from units you can count: screens, pages and APIs, each with a published starting price.

per UI/UX design screen
from ₹370per UI/UX design screen
per mobile app screen
from ₹1540per mobile app screen
per web page
from ₹1000per web page
per API
from ₹1180per API

What a fixed-price project is

A fixed-price project is a piece of software built for an agreed scope at an agreed price. You pay for the outcome, not the hours. At TechOvelpo the price is calculated from units you can count and check: UI screens, app screens, web pages and APIs, each with a published starting price.

This model suits you when you can describe what you want built and can stop describing it once the work starts. It does not suit a product whose requirements will keep changing; the section on when a fixed price is a bad idea explains why.

How per-unit pricing works

Each unit has three tiers that follow complexity. The prices below are the starting price for each tier, as published on /pricing.

Unit Tier (simple, moderate, complex) Starting price
UI/UX design, per screen Foundation, Innovation, Artistry from ₹370, ₹550, ₹820 per screen
Mobile app development, per screen Clarity, Depth, Excellence from ₹1540, ₹2530, ₹3610 per screen
Web development, per page Essential, Professional, Advanced from ₹1000, ₹1630, ₹2530 per page
Backend API, per API Core, Dynamic, Enterprise from ₹1180, ₹1630, ₹2530 per API

In plain terms:

  • UI/UX design is priced per screen. Foundation covers minimalist screens and straightforward layouts, Innovation adds visual appeal and interactivity, and Artistry covers advanced applications with intricate layouts.
  • Mobile app development is priced per screen. Clarity is for clean, efficient screens, Depth for richer visuals with moderate interactivity, and Excellence for complex UI with intricate components.
  • Web development is priced per page, with packages from affordable, quick-to-launch websites (Essential) to high-performance sites with advanced features (Professional and Advanced).
  • APIs are priced per API. Core means simple CRUD APIs, Dynamic means moderate APIs optimised for performance, and Enterprise means complex APIs for high-demand applications.

The word "from" is deliberate. The starting price is the floor of a tier, and the quote you receive is for your specific screens and endpoints. The published prices do not state whether GST is included, so we confirm tax treatment in the written quote; our monthly developer prices, by contrast, exclude 18% GST.

How scope is defined

The quality of a fixed-price project is decided before it starts, in the scope document. A good one contains:

  1. A list of units. Every screen, page and API named, with its tier. "User profile, mobile, Depth" is a line item; "profile stuff" is not.
  2. What each unit does. One or two sentences, plus any rules that matter, such as roles, validations and integrations.
  3. What is not included. Items you might assume are covered but are not, for example content writing, third-party account setup, app-store listing or load testing.
  4. Your obligations. What you will provide and by when: brand assets, API credentials, copy, decisions. Delays on your side move the schedule, not the price.
  5. Acceptance criteria. How you will decide a unit is done: it matches the design, it passes the agreed flows, it is deployed to a test environment.

We would rather spend a couple of calls tightening the scope than discover a gap at milestone three. If the scope cannot be written down in this form, that is itself useful information: it tells you a monthly team is the better route.

Change requests

Changes are normal; the point is that they are visible and priced before they happen.

  • Within scope: a different label, spacing, copy, or small behaviour that fits the agreed description. No charge.
  • Change request: a new screen, a new API, or a change that alters a delivered unit. We describe it, price it using the same per-unit rates and tiers, and wait for your approval.
  • Re-tiering: if a screen turns out to need more complexity than its tier, we tell you and agree the new tier before continuing, not afterwards.

Nothing is billed without your approval. This is the part of fixed-price work most worth reading in the contract, so read it.

Milestones and payments

Payments are milestone-based: the project is divided into stages, and each stage has agreed deliverables. You review each stage against the acceptance criteria before the corresponding payment is due. We agree the milestones and the payment schedule in writing before kickoff. We sign an NDA before work starts, and all code and IP are assigned to you.

Fixed price vs time and material

Fixed price Time and material (monthly team)
Cost certainty High, if scope holds Predictable per month, total depends on duration
Flexibility Low: changes are priced High: re-prioritise every sprint
Best when Scope is known and stable Scope is evolving or ongoing
Your management load Light: review at milestones Heavier: you set priorities each sprint
Risk of overrun Mostly on us, within scope Mostly on you
Risk of building the wrong thing On you, if the scope was wrong Lower, you can redirect early
Typical examples Marketing site, design system, clearly specified app or API set Product development, ongoing improvements
Commitment Until the agreed scope is delivered One month minimum, 2 weeks' notice

Monthly work is covered on the pages about Staff Augmentation and Dedicated Team.

When a fixed price is a bad idea

We will tell you when you are looking at the wrong model.

  • You are still discovering the product. If you expect users to change your mind, fixed scope will fight you. A monthly team lets you adapt without renegotiating.
  • The scope is vague. A price on a vague scope is a guess. One of you will absorb the error, and it will cost goodwill.
  • You want to keep adding features continuously. Each addition is a change request. A team on a monthly plan is cheaper and simpler.
  • The system is deeply entangled with one you have not documented. Unknown legacy behaviour is the common cause of overruns. Start with a short paid discovery or a small team to map it first.
  • You want maximum control over how it is built. Fixed price means we make the technical decisions within your acceptance criteria. If you want to make them yourself, staff augmentation fits better.

A common healthy pattern is a fixed-price first version, followed by a monthly team once there are real users and real feedback.

Preparing to ask for a quote

You will get a faster and more accurate quote if you bring four things: a list of the screens or pages you can already picture (a sketch or a competitor's screenshots is enough), a list of the data and actions behind them, any systems the project must connect to, and the date by which you need something live. If you have none of these, say so; we can start with design screens at the UI/UX tier prices, which gives you a concrete artefact to price the build against.

A useful habit is to design first and build second. UI/UX screens priced from ₹370 each are far cheaper to change than built screens priced from ₹1540 each, so settling what you want on paper before development removes most of the surprises that make fixed-price work go wrong.

Next step

Send us your list of screens, pages and APIs, even if rough. We will return a written quote that names each unit and its tier. If you want to check ballpark figures first, the full tier descriptions are on /pricing, and what we build is outlined on /services.

Frequently asked questions

What does 'from ₹370 per screen' actually mean?

It is the starting price for the simplest tier of UI/UX design, a minimalist screen with a straightforward layout. More interactive and intricate screens move into higher tiers. The tier is agreed per screen before work starts, so the quote is a number, not a range.

Do the published prices include GST?

The published per-unit prices do not say whether GST is included. We state tax treatment in the written quote, so confirm it with us when you request one. Our monthly developer prices exclude 18% GST.

What happens if I want to change something midway?

Small clarifications within the agreed screens are absorbed. A new screen, a new API or a change that alters an agreed one is a change request, priced with the same per-unit rates and approved by you before we start it.

How do you decide which tier a screen belongs to?

By its complexity: layout, number of components, interactivity and the logic behind it. We tag each screen in the scope document so you can see the tier next to every line item, and you can challenge it before signing.

Is a fixed price always cheaper than hiring monthly?

No. It is cheaper when the scope is truly settled. If requirements are still moving, you will either pay for change requests or get something built to a spec you have outgrown, and a monthly team is the better fit.

Can I move from a fixed-price build to a dedicated team?

Yes, and many clients do. The engineers who built the first version can continue on a monthly plan. Nothing needs to be rebuilt.