Milestone Review
A focused inspection of one delivery milestone and its acceptance criteria.
Request scope & quoteIndependent technical inspection
Before you approve the next milestone, know what was actually delivered.
Your vendor says the project is ready. Tech Inspector gives decision-makers an independent engineering assessment before they approve, launch, pay for or take over a software project.
72Overall readiness
Requirement completion84%
Security hygiene61%
Operational readiness58%
Maintainability78%
Critical finding
Partially deliveredProduction backup requirement
Evidence
Automated backupPass
Seven-day retentionPass
Restore procedureMissing
Restore testNot verified
Business risk
Backups exist, but recovery capability has not been proven. A production incident may still result in extended service interruption.
When to inspect
When the decision is commercial, but the evidence is technical.
You do not need another vague health check. You need facts tied to the decision in front of you.
Vendor milestone acceptance
Your agency says a milestone is complete and requests payment.
Before production launch
The software works in demos, but customers are about to depend on it.
Development vendor change
You are replacing the company or freelancer that built the system.
Technical handover
Another team needs enough access, documentation and deployment knowledge to take over.
Cloud ownership review
AWS, domains, repositories or SaaS accounts may depend on contractor-owned credentials.
Investment sanity check
A practical technical review before committing further capital—not legal due diligence.
Evidence model
From contract language to a defensible action.
Every important conclusion should have evidence behind it and a decision attached to it.
01
Requirement
Daily automated backups.
02
Technical evidence
RDS backup enabled. Seven-day retention. No restore test evidence.
03
Assessment
Partially delivered.
04
Business risk
Recovery capability is not proven until a restore works.
05
Recommended action
Run a controlled restore and document it before final acceptance.
✓
Acceptance decision
Hold the requirement open until the evidence exists.
Inspection coverage
The parts that determine whether you can safely own and operate the system.
Scope is agreed first. A milestone review stays focused; a full inspection goes wider.
Requirements vs implementation
- Feature completion
- SOW alignment
- Acceptance criteria
Code health
- Architecture
- Maintainability
- Reproducible builds
Testing & delivery
- Critical-path tests
- CI/CD
- Rollback
Security hygiene
- Leaked secrets
- Dangerous defaults
- Permission problems
Not a substitute for a full penetration test.
Cloud & operations
- Ownership
- Backups
- Monitoring
- Infrastructure as code
Handover
- Documentation
- Repositories
- Accounts
- Bus-factor risk
Trust model
We inspect. We don't take control.
Access is temporary, restricted and read-only wherever possible. The report belongs to the client.
GitHubRead-only
AWSRestricted role
StagingTest access
ProductionNo changes
V3rim Inspector
No unnecessary copying of business data. Access can be revoked immediately after inspection. NDA available where appropriate.
No production modifications unless separately agreedProcess
A focused route from concern to evidence.
Scope
Understand the milestone, contract and concern.
Evidence
Inspect repositories, staging, cloud and delivery.
Review
Combine automated checks with senior review.
Report
Prioritize evidence, impact and action.
Validation
Review findings and optionally verify fixes.
Scope options
Choose the decision, then size the inspection around it.
Pricing follows scope. No credentials are requested through the inquiry form.
Full Technical Inspection
A broader review of application, infrastructure, operations and delivery.
Request scope & quoteTakeover & Handover Review
Designed for vendor or team transition, ownership and continuity.
Request scope & quoteFAQ
Practical questions, direct answers.
Do you need production access?
Not always. We agree the minimum access needed for the scope and use read-only access wherever possible.
Will you change anything?
No production modifications are made during an inspection unless separately scoped and approved.
Can our vendor participate?
Yes. Vendor context can make evidence gathering faster, while the assessment remains independent.
Is this a penetration test?
No. We review security hygiene and obvious risks, but Tech Inspector does not replace a full penetration test.
Is this legal due diligence?
No. It is a practical engineering inspection and does not provide legal certification or legal due diligence.
Can you verify fixes afterward?
Yes. Optional re-validation can confirm whether selected findings were resolved.
What happens to access afterward?
Temporary access should be revoked after the inspection. The client keeps the report.
Have a system you don't fully trust yet?
Start with a technical conversation. We will help you establish the facts and decide what to do next.