Skip to content
Valentir
Start a project

Process

The whole thing, drawn out.

Most agencies describe their process in adjectives. Ours is a set of stages with conditions between them, enforced by the system we run the studio on — so we can just show you.

24h

Reply to every enquiry

14

Weeks, typical build

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.

You do not need another website.

You need software that moves the business forward. A site that does not feed the next link in the chain is a brochure with better typography.

Where a website actually sitsSix links. Most agencies build one.

  1. Website

    Attention

  2. Leads

    Captured, not lost

  3. CRM

    One pipeline

  4. Operations

    The actual work

  5. Payments

    Money in

  6. Analytics

    What to do next

A site that does not feed the next link is a brochure. We build the chain, not the first box.

The swap

From scattered workflows to one system.

What custom software replaces is almost never a competitor's product. It is three WhatsApp groups, a spreadsheet with a version number in the filename, and one person who knows how it all actually works.

BEFOREAFTER
Mundra Ops · CHA + TransportersRamesh (CHA), Patel Transport, Sunil (Customs), +44 others
Ramesh CHAMSKU7741 Mundra gate-in ho gaya? cutoff kal 4 baje hai07:41Patel Transporttruck 2 ghante late hai, driver ka number bhej diya07:580:41BL draft kisne bheja tha? do version aaye hain09:12Sunil (Customs)@everyone Halden ka shipping bill query aaya hai, koi dekh raha hai??09:20Patel Transportdetention lagega bhai, 3 din ho gaye yard mein09:3163 unread messagesRamesh CHAcutoff miss ho gaya, agla vessel Thursday10:02
Type a message
Control tower17 customs holdstower.northgatefreight.in
NGF-58214Halden TextilesNhava Sheva → RotterdamIn transit
NGF-58213Corvane Auto ComponentsChennai → HamburgCleared
NGF-58211Meridian PharmaMundra → Jebel AliCustoms hold
NGF-58209Stellan ChemicalsMundra → SingaporeIn transit
NGF-58215Orlix Home FurnishingsNhava Sheva → FelixstoweIn transit
NGF-58216Tavira FoodsChennai → ColomboIn transit
3,812 containers in transit₹412 Cr cargo in flight0 cutoffs missed this week
  • A single source of truth. One record per transaction, not a version in every inbox.
  • An audit trail by default. Who did what, when, recoverable months later.
  • Roles and permissions. Approval limits enforced by the system, not by seniority.
  • Data you can query. Structured from day one, so reporting is a view and not a project.
Not sure which side of that line you are on?Tell us what you are running on today. That is a useful conversation in itself.Start there

A small team that finishes things.

Small is the strategy, not a stage we are trying to grow out of. It is the only way the people who take your first call are also the people who write the code.

  1. Senior attention

    You work directly with the people building the product. There is no bench to hand you off to and no account-manager layer in between.

  2. Clear scope

    You know what is being built before development starts. Changes are priced in writing, before anyone starts them.

  3. Production-minded

    Security, performance, deployment and maintenance are part of the build, not a phase that gets cut when the date gets close.

  4. Reusable systems

    Every project improves our component registry, which is why the next one starts further along than the last.

  5. Post-launch support

    Six months of warranty on what we built, included. We do not disappear after deployment.

  6. You own everything

    Code, repositories, credentials and infrastructure transfer at go-live and stay yours. No lock-in of any kind.

What you will not get

6
  • No unnecessary meetings.
  • No mystery timelines.
  • No disappearing developers.
  • No unpaid discovery disguised as development.
  • No bloated teams.
  • No handoff to someone you have never met.

What the engagement looks like

50 / 50
  1. 50% advance50% due
  2. Build
  3. Review
  4. Launch50% due
  5. Warranty

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

Start here

Want to see it run on your project?

Send a brief and you will be inside this process within a day — starting with an honest answer about whether it is the right fit.

Start a projecthello@valentir.in