Example Digital
Security practices is the weakest area (69/100).
- audited
- live sites
- 1 audited
maturity // section scores
- Tech stack currency93
- Delivery & deployment98
- Source control & code quality92
- Project management & agile86
- Security practices69
- Operations & support87
- Team shape91
- Sample projects91
Section weights: tech 15% · delivery 20% · source 15% · project 15% · security 10% · operations 10% · team 5% · sample 10%
If the team is already stretched, I can help.
NY8 can join as a private contractor for a specific upgrade, project or delivery bottleneck - no retainer, no obligation.
Why this needs to change
The weakest areas in this report: what staying as you are keeps costing, and what changes once it is fixed.
costing you now
Secrets in repositories, accounts without MFA and backups nobody has ever restored are the failures that end a client relationship in a single day.
what changes
Basic hygiene removes incidents that no insurance covers, and the security answers you can give in a tender become a reason to be chosen.
costing you now
Work that lives in chat and spreadsheets cannot be estimated, quoted or defended, so the team absorbs the difference as overtime.
what changes
A tracker and a rhythm make progress visible to the client, protect the team’s time, and turn quoting from a guess into a calculation.
costing you now
Without monitoring and error tracking the client finds the outage first, and the team spends the day reconstructing what happened instead of fixing it.
what changes
You hear about problems before the client does, support stops eating delivery time, and handover stops depending on one person’s memory.
costing you now
When one person holds each project, holidays, resignations and growth all turn into delivery risk - and the developers who notice first are the ones who leave.
what changes
Shared ownership and a second pair of eyes let the team take on more work without hiring in a panic.
Sample projects
Live sites the team handed over, audited by the Site Audit engine while this report was built.
85
The plan, as a checklist
Every failing check with something to do about it. Tick what is done and the score above the lists moves with you.
score with the fixes ticked
0 of 8 done
0%
Tick what you have done. Each tick counts that check as passed and the score moves with it.
Start here
the biggest gaps, most severe first0 / 8 doneEvery check
Open a section for its numbers, and each check's evidence and fix.
- in the stack
- 7
- past end of life
- 0
- out of support
- 1
- still supported
- 4
- upgrade plan
- yes
sources // version support dates from endoflife.date (cached for a day; an unreachable API leaves versions ungraded, never failed). Sample projects run through the same Site Audit engine as the rest of Tech Auditor. Everything else is scored from the answers given, and measures left as unknown stay unscored rather than counting as a failure. Weights: Tech stack currency 15% · Delivery & deployment 20% · Source control & code quality 15% · Project management & agile 15% · Security practices 10% · Operations & support 10% · Team shape 5% · Sample projects 10%. Release data checked .