Skip to content
Valentir
Start a project

What we build

Four practices, one system.

We would rather be the best team you have used for a narrow set of work than an adequate one for everything. Below is exactly what each engagement covers, what it costs to start, and what you have at the end of it.

Start a projectSee pricing
01

Web

Websites that do more than look good.

Marketing sites, commerce and web applications built on Next.js — fast, indexable, and editable by your own team without calling us.

₹60,000

Starting price

6mo

Warranty

Read the detail

What we build

  • Marketing and brand sites
  • Commerce storefronts
  • Landing page systems
  • Content platforms

Technology

  • Next.js
  • TypeScript
  • CMS
  • SEO
  • Analytics

Plus the repository, credentials and hosting — in your name, at go-live.

02

Mobile

One product. Two platforms.

React Native applications shipped to the App Store and Play Store, with a release process your team can run after we leave.

₹1,50,000

Starting price

6mo

Warranty

Read the detail

What we build

  • Customer-facing apps
  • Field and operations apps
  • Marketplace apps
  • Store submission and release

Technology

  • React Native
  • Expo
  • APIs
  • Payments
  • Push

Plus the repository, credentials and hosting — in your name, at go-live.

03

Software

Internal systems built around your business.

Dashboards, CRMs, admin panels and operational software modelled on how your team actually works — with roles, approvals and an audit trail.

₹2,50,000

Starting price

6mo

Warranty

Read the detail

What we build

  • CRMs and pipelines
  • Admin and operations panels
  • Dashboards and reporting
  • Marketplaces

Technology

  • Node.js
  • NestJS
  • PostgreSQL
  • MongoDB
  • AWS

Plus the repository, credentials and hosting — in your name, at go-live.

04

Systems

The infrastructure connecting it all.

The layer most agencies skip: the APIs, integrations, deployments and data model that turn separate pieces into one system your business runs on.

Scoped

Per engagement

6mo

Warranty

Read the detail

What we build

  • API and data-model design
  • Third-party integrations
  • Deployment pipelines
  • Monitoring and runbooks

Technology

  • API design
  • Integrations
  • CI/CD
  • Infrastructure as code

Plus the repository, credentials and hosting — in your name, at go-live.

Technology with teeth

How a build actually runs.

Six stages. Each one has a condition that has to be true before the next begins, and those conditions are enforced in the system we run the studio on — which is the only reason they hold when a date gets close.

The full process

  1. Discover

    Understand the business.

    We work out what the software has to do for the business before we draw a screen. You leave with a written problem statement you can argue with.

    You receive

    A written problem statement

  2. Design

    Turn requirements into a system.

    Flows, data model and interface, designed together. Scope gets locked here — which is the only reason a fixed price and a fixed date can hold.

    You receive

    Locked scope, data model and screens

  3. Build

    Engineering begins.

    Two-week cycles, each ending in a working deploy on a real URL. No percentage-complete bars, no big reveal at the end.

    You receive

    A working deploy every two weeks

  4. Verify

    QA, performance and edge cases.

    Real devices, real data, and the states nobody demos: empty, offline, failed, and the two-hundredth record nobody drew.

    You receive

    A pass on real devices and real data

  5. Ship

    Production deployment.

    Your domain, your cloud account, your repository. Credentials transfer at go-live because the accounts were in your name from day one.

    You receive

    Domain, cloud and repository in your name

  6. Compound

    Every build makes the next one faster.

    Recurring problems become reusable components in our registry. That is why the timelines are honest rather than heroic.

    You receive

    Reusable components in the registry

DesignCodeTestCommitDeployLive
valentir.in

Every fortnight, this whole loop ends on a URL you can open.

Project to productWhy the next build starts further along
  1. Client problemSomething the business cannot do today
  2. ProjectDesigned, built, shipped, handed over
  3. Internal solutionThe pattern behind it, extracted
  4. Reusable componentVersioned, hash-addressed, editable
  5. Valentir productWhen it turns out everyone has the problem

Every project teaches us something. Recurring problems become reusable systems, and occasionally a product — which is how a fixed price and a short timeline stop being a contradiction.

The things people ask first.

If the awkward question is not here, send it. We would rather have the difficult conversation now than three weeks into a build.

Ask us directlyOne reply, from whoever would build it

8 answered in full

Yes, and it is part of every build rather than a separate line item. We design in components with real content and real edge cases — empty, loading, error, overflow — because those are the states that decide whether software is actually usable.

Usually, after a paid technical audit so we can tell you honestly what shape it is in. Sometimes the finding is that maintaining it costs more than replacing one part of it, and we would rather establish that up front than discover it three months in.

Always, and from the first commit rather than the last. We work inside your GitHub organisation and your cloud account. There is no licence, no proprietary platform and no clause that makes leaving expensive.

Six months of warranty on what we built, included in the price. That covers defects in our work; new features get quoted like any other work. After the warranty some clients move to a maintenance retainer and some never need one.

We set hosting up in your own account — Vercel, AWS or whatever fits — so the bill and the control are yours. We can manage it for you on a retainer, but you are never in a position where leaving us means losing your infrastructure.

Fifty per cent advance before the build starts, fifty per cent before go-live on your domain. Nothing starts before the advance clears — that is a gate in our own system rather than a policy we try to remember.

Yes, and we will sign yours rather than insisting on ours. We also work under DPAs where a project touches customer data, and access to your systems is time-boxed to the engagement and revoked at handover.

Six months on every build, included. If something we wrote is broken, we fix it at no cost for six months after go-live. That is in the statement of work, not a goodwill gesture.
Start here

Not sure which of these you need?

Often it is fewer than people expect. Describe the problem and we will tell you the smallest useful version of it — including when that is nothing at all.

Start a projecthello@valentir.in