Growth readiness assessment
Tests whether documented capacity supports anticipated demand at 2× and 5× current load. Highlights the service constraints most likely to limit growth.
— Product & Tech
Assesses infrastructure headroom against documented peak demand, projects the first constraints at 2× and 5× load, and identifies the bottleneck to prioritise before growth puts service reliability at risk.
2–3 weeks → ~25 minutes
For a full population, not a sample
No coding required
— USE CASES
Tests whether documented capacity supports anticipated demand at 2× and 5× current load. Highlights the service constraints most likely to limit growth.
Provides an evidence-based view of infrastructure headroom, reliability history and scaling exposure. Makes capacity assumptions and projected failure points explicit.
Identifies the first bottleneck to address and relates capacity constraints to infrastructure costs. Gives teams a focused basis for investment discussions.
Compares documented peak demand with available capacity by service. Shows where limited headroom may put latency or service commitments at risk.
— HOW IT BEHAVES
The mechanics behind this specific template — what it reads, what it calculates, and where a human stays in the loop.
Each role is assessed against criteria you control and weight, so the same standard applies to every role in the organisation in scope.
The figures behind each role are computed by formula during the run, so the arithmetic is identical every time and can be checked line by line.
Figures buried in narrative org data, role documentation and headcount exports are extracted as data you can compute and compare with.
Current external sources on the organisation in scope are researched during the run rather than recalled from training data, and every source travels with the output.
Each row of your export is processed on the same basis, so no role is skipped however long the table is.
Movement across the organisation in scope is visualised from the computed data, so the trend is legible at a glance.
Growth plans often assume infrastructure can absorb more demand without a clear view of capacity limits, service dependencies or cost pressures. In practice it shows up as growth readiness assessment: tests whether documented capacity supports anticipated demand at 2× and 5× current load. Highlights the service constraints most likely to limit growth. The value sits in the rigour, not the typing — yet the rigour is exactly what gets traded away when there is only 2–3 weeks of capacity for it.
Skillsize turns that work into a Skill: you supply the material, and what comes back is scalability and infrastructure risk diagnostic, with service-level throughput, latency and cost-per-transaction analysis. The criteria, ordering and review points that make the answer trustworthy are encoded in the Skill itself — which is the difference between a structured method and a prompt someone pastes in. In effect, 2–3 weeks of senior time compresses into ~25 minutes — and the output is comparable across clients, quarters and colleagues instead of shaped by whoever ran it.
Scalability & infrastructure stress test exports as a structured SKILL.md file and is MCP-ready, so the same method runs in ChatGPT, Claude, Copilot or your own AI products. Adapt it to your methodology, and the intelligence stays yours — not locked to one vendor.
Assesses a reported vulnerability against severity scoring, real exposure and the criticality of the affected asset, then returns a governed remediation decision — patch now, take it in the next cycle or formally accept the risk — with the reasoning recorded and a security lead sign-off before work is scheduled.
Maps a target’s data and intellectual property assets, clarifying ownership, licence obligations and portability constraints to support migration and exit planning.
Builds a complete inventory of the technology estate — every system with its vendor, purpose, integrations, hosting and build-or-buy status — and flags where concentration, lock-in or vendor viability creates risk.
Assesses security controls and supporting evidence against relevant compliance frameworks, producing a risk-led remediation plan or an assurance summary grounded in documented findings.
Tests product roadmap commitments against engineering capacity, delivery history and dependencies to give investment committees a defensible view of what is likely to ship within twelve months.
Reviews data rights, AI use and model controls against governance maturity, producing a deal-risk memo or readiness summary that clarifies exposure and its implications for the transaction.