Everything we ship
has to be F.I.T.
Three principles govern the work at Nilavil — how we scope a project, how we write code, how we answer a client at eleven at night. Stated plainly, without the mission-statement language.
Customers First
“A decision that helps us at the client's expense is not a decision we make.”
- Scope is driven by what the business needs, not by what is convenient to build.
- Every flagged document, failed sync and edge case is treated as though it happened to us.
- Response time is a product metric here, not a support afterthought.
Integrity, Always
“We tell clients the truth, particularly when the truth costs us the work.”
- If our systems produced a wrong number, we raise it before anyone else finds it.
- No manufactured urgency, no dark patterns, no metrics we would not publish.
- A clear no, given early, is worth more than a yes we cannot honour.
Think in Decades
“We optimise for the system that still holds up in ten years, not the demo that ships this quarter.”
- Correct and slower beats fast and fragile, every time it comes to a choice.
- Every architectural decision assumes someone else maintains it five years from now.
- Trust compounds the way revenue does — gradually, and then all at once.
In practice
What that means
when you hire us.
Principles are cheap to write. These are the working commitments they translate into on every engagement.
You work with the builders
No account layer between you and the people writing the code. The person who scopes your project is the person who delivers it, and the one who answers when something breaks.
Small scope, shipped early
We cut work into pieces that reach production in weeks rather than quarters. Real usage tells us more in a fortnight than a specification does in a month.
Fixed scope, honest estimates
We quote what we understand and say plainly what we do not. When something turns out larger than estimated, you hear it as it happens, not at invoicing.
You own everything
Code, infrastructure, domains and accounts are yours from day one. Nothing is held hostage to a retainer, and any competent team can pick up where we left off.
Written over verbal
Decisions, trade-offs and reasoning are written down. It keeps a distributed team aligned and leaves you with a record of why the system is the way it is.
We use what we build
Bright AI runs our own document workflow before it runs anyone else's. Products we would not depend on ourselves do not reach clients.
That is the whole rulebook