Process
The whole thing, drawn out.
Most agencies describe their process in adjectives. Ours is a set of states with conditions between them, enforced by the system we run the studio on — so we can just show you the diagram.
24h
Reply to every enquiry
14
Weeks, typical build
Before anything is signed
Where your enquiry goes.
One pipeline, two ways out of it, and a twenty-four hour clock running from the moment you write in. If we are not right for the work you will hear that quickly rather than politely never.
No build without a paid advance
A project cannot enter build until its 50% advance is paid. Enforced as a gate in the API, not as a guideline.
Reply within 24 hours
An enquiry waiting longer than a day is an SLA breach. It shows red on the morning digest until it is answered.
Proposal within 24 hours of the call
Same-day is the standard. Twenty-four hours is the hard limit, not the target.
Once it is signed
Six stages and three hard gates.
A gate is a condition the software checks, not a habit we try to keep. A project cannot enter build before the advance clears, cannot be marked delivered before the QA checklist passes, and cannot reach handover before credentials have moved.
▮ A stage with a gate cannot be entered until its condition is true. The check lives in the API, not in a document.
- 01Scope written down
Discovery
We work out what is actually being built and what it costs, in writing. If the timeline is not honest, this is where we say so — week one is the cheapest moment to hear it.
- 02Within 24 hours of the call
Proposal
A locked-scope statement of work with a fixed price and a fixed date. Same-day is the standard; twenty-four hours is the hard limit.
- 0350% advance paid
Build
A project cannot start until its advance is paid — that gate is enforced in our own API, not left to good intentions. From there you see working software, not status decks.
- 04Checklist passed
QA
Delivery means the QA checklist is signed off and the final invoice is out. Real devices, real data, and the states nobody demos: empty, offline, and failed.
- 05Credentials transferred
Handover
Final payment, then every repository, credential and piece of infrastructure moves to your ownership. Accounts were created in your name from day one anyway.
- 06Six months
Warranty
Six months of fixes on what we built, included. After that some clients keep us on maintenance and some never need us again. Both are fine outcomes.
During the build
A fortnight is the unit.
Phases overlap — design does not stop when build starts. What does not move is the cycle: every two weeks there is something on a URL you can open.
Every fortnight you get
A working deploy
on a URL you can send to anyone
A written note
what moved, what is next, what is at risk
Scope status
anything added, priced, before it is built
The date
restated, or renegotiated early if it is at risk
At the end
Handover is the deliverable.
Accounts are created under your ownership from the first day rather than migrated at the end, which turns handover from a negotiation into an afternoon.
public value
GA4 ID, domain, profile URL
A real input. Stored in the panel, visible to your team, safe in a breach because it is not a secret.
secret value
API keys, registrar logins
No input field exists. The page explains how to add us as a user on your own account instead.
We never accept a real secret through a web form. A leaked database should not be able to expose a client's payment gateway.
valentir.in
public site
- · static, revalidated
- · no CMS of its own
- · no mail credentials
Valentir Admin
operations console
- · owns the content
- · owns the credentials
- · owns the pipeline
A form on this page posts to the panel, which holds the mail keys and drops the enquiry straight into the pipeline. The site itself stores nothing — so there is nothing on it worth stealing.
Repositories
Transferred to your GitHub organisation
Infrastructure
Reproducible from code, in your cloud account
Runbooks
Written so a new hire can follow them
A live walkthrough
We work through the codebase with your team
Taking new projects
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.
- 24h
- Reply to every enquiry
- 24h
- Proposal after the call
- ₹0
- Cost of the first conversation