Credentials & Awards
A certificate is a statement that someone independent inspected how work gets done. The inspection is the interesting part, so this page describes the quality system itself — the checks, the standards and the defect discipline an auditor would examine.
Nothing reaches a client on one person's judgement.
Vinove, our parent group, is appraised at CMMI Level 3 (appraised 25 September 2025, valid to 25 September 2028). NASSCOM member. Quality is set by what has to happen before a change ships, not by a policy document. Every change passes a second engineer, an automated suite and a release decision with a name attached. An auditor traces those three, because they are the points where a shortcut would show.
01Check oneA second engineer reads it
No change merges on its author's approval alone. The reviewer is accountable for what they approve, which makes review a decision rather than a formality.
02Check twoThe suite runs, and blocks
Automated tests gate the merge rather than reporting after it. A suite that can be waved through is a dashboard, not a control.
03Check threeSomeone owns the release
A named person decides a release goes out and records what was tested and what stayed open. That record is what an audit asks for first.
04Check fourThe definition of done is written
Done includes tests, documentation and handover notes. Where it is left implicit, it quietly shrinks to whatever the deadline allows.
The same bar on every engagement, not the strongest team's bar.
A standard that lives in one team's habits is not a standard. Architecture decisions, coding conventions and review expectations are written down, applied at onboarding and revisited when they stop fitting. That is what makes quality repeatable across engagements a single lead never sees.
Written, not assumed
Architecture and coding standards exist as documents an engineer can be pointed to, and that a client can ask to read.
Applied at onboarding
A new engineer meets the standard in their first week, so consistency does not depend on who happened to train them.
Revised when they stop fitting
A standard nobody follows gets fixed or removed. Keeping dead rules on paper is how a quality system loses credibility internally.
Exceptions carry a name
Deviating from a standard is allowed and recorded, with the approver named. Silent exceptions are the ones that cause trouble later.
A defect that recurs is a process problem, not a coding one.
Counting bugs measures nothing on its own. What matters is whether the same class of failure can happen twice. Each escaped defect gets a cause, a test that would have caught it, and a change to the check that missed it — which is why the rate falls rather than plateaus.
Every escape gets a cause
A defect reaching a client is traced to the check that should have caught it, not to the person who wrote the line.
The regression test comes first
The fix ships with a test that fails without it, so the same defect cannot return unnoticed in six months.
Patterns get escalated
Three similar defects across engagements is a signal about the standard, and it is raised rather than absorbed quietly.
Four questions that separate a certificate from a badge image.
These work here and on every competitor's site equally well. A vendor that cannot answer all four is showing you an image rather than an attestation, and the gap between those two is where procurement risk actually sits.
01Who issued it, and what was the scope?
Certifications cover a defined scope, often one office or one service line. A certificate that does not name its scope is not answering your question.
02When does it expire?
Ask for the issue and renewal dates. A lapsed certificate stays on a website far longer than it stays valid.
03Can you see the certificate itself?
The issuing body's register is the check that matters. A logo on a page is not evidence, and a real certificate holder produces it without hesitation.
04Does the scope cover your work?
A credential covering a delivery centre you will never work with tells you nothing useful about the team assigned to you.
Credentials are one input among several.
A certificate says a system was inspected once. Delivery evidence and security practice tell you how it behaves week to week, which is usually the more useful signal during an evaluation.
How delivery actually performs
Release cadence, defect escape rate and predictability, with the measurement method stated alongside them.
How data and access are handled
Access control, secure development and incident response, which sit outside a quality-management scope.
The rest of the company record
Delivery model, client evidence and the people accountable for each, gathered in one index.
Records a reviewer can inspect, not badges to admire.
Each record publishes with its issuing body, scope and dates attached. Until compliance attaches those documents, every entry stays visibly marked as a sample rather than appearing as a finished certificate.
Explore case studiesCertification covering the information-security management system. Issuing body, scope statement, certificate number and renewal date publish once compliance sign-off confirms them.
Sample · pending client approvalExternally audited certification of the quality-management system described here. Issuing body, audited scope and renewal date publish on confirmation.
Sample · pending client approvalListing on an independent, review-verified B2B provider directory. Awarding organisation, category and covered period publish once the current standing is confirmed.
Sample · pending client approvalTheir auditor pack arrived complete on the first request. That has genuinely never happened to me before.
Sample · pending client approval
Questions a diligence checklist raises.
01Why are the certificate details not shown yet?
Because a certificate claim is only worth anything with its issuing body, scope and renewal date attached, and compliance is still attaching those documents to the records here. Publishing the logo first and the detail later is the pattern this page is built to avoid.
02Does a certification mean every project meets that standard?
Not automatically. Certifications carry a defined scope, and a genuine one names it. Ask whether the scope covers the delivery location and service line your engagement would actually use, because that is what determines whether it applies to you.
03What is the difference between this page and the security page?
This one covers the quality-management system: how work is reviewed, how standards hold and how defects are prevented. Security covers access control, secure development practice and incident response. An auditor treats them as separate scopes.
04Can we audit you ourselves instead?
Yes, and enterprise buyers regularly do. A client-run audit or security questionnaire is a normal part of onboarding, and the evidence described here is what gets provided against it.
05How do you keep standards current across many teams?
Standards are written, introduced at onboarding and revised when they stop fitting the work. Exceptions are allowed but recorded with a named approver, so a deviation is a decision someone owns rather than a quiet local habit.
06Do awards actually tell a buyer anything useful?
Some do and many do not. A recognition based on verified client reviews carries more information than one a vendor applied and paid for. Ask which category it was, who judged it, and what period it covers.
07What should we ask for during procurement?
The certificate itself, its scope statement, its renewal date, and the delivery evidence next to it. Those four together tell you more than any badge wall, and every one of them is checkable independently.