Focused screen
A limited production-risk brief: strongest signals, top concerns and the investigation needed. It does not establish whole-system readiness.
For vibe-coded and AI-built products
Production Readiness Assessment
It works today. Can you depend on it for what comes next?
Receive a production-risk brief or a scoped readiness conclusion for your product's next stage, according to the selected depth. AI-assisted investigation and principal validation support prioritized recommendations, conditions and evidence gaps.
What you receive
The result of this engagement.
A focused production-risk brief or an integrated readiness conclusion for the intended next stage. The selected depth defines the result, with priorities, evidence gaps and recommended next actions.
- A production-risk brief or scoped readiness conclusion, according to the selected depth, with traceable findings, strengths and material risks.
- Prioritized remediation direction linked to the next-stage decision, with conditions and evidence gaps.
- A principal-led readout explaining the conclusion, recommended actions and appropriate reliance.
A defined engagement
An agreed depth. A defined result.
- Coverage
- An existing product, its intended next-stage use and the selected assessment depth. Agree the system boundary and any specialist testing required.
- Inputs
- Access to the relevant architecture, code, configuration, tests and operating evidence, with owner participation to explain business use and constraints.
- Completion
- A focused screen delivers a production-risk brief; an integrated review delivers a scoped readiness conclusion. Each includes the agreed recommendations, evidence gaps and principal-led readout.
Assessment depth
Choose the depth the decision needs.
Integrated production review
An integrated view of interacting risks for the next business stage, with a readiness assessment and prioritized recommendations. Evidence gaps and coverage remain explicit.
Deeper enterprise scope
Additional system, integration and specialist depth for the agreed decision and criteria. An enterprise or regulated context does not imply certification or complete compliance coverage.
The selected depth defines the assessment coverage and conclusion. Evidence access, client participation, specialist needs, timing and fees are agreed before work starts.
When this helps
Recognize the situation.
- You built the product quickly with AI tools such as Claude Code, Cursor, Codex, Copilot, Lovable, Bolt, Replit or v0, and it now has real users.
- A working product is about to serve more users, a larger customer or a critical business process.
- AI-assisted development has moved faster than independent architecture review.
- You need to distinguish structural risk from configuration changes and routine hardening.
How the work unfolds
Evidence appropriate to the question.
01
Define the next stage
Agree the intended next-stage use, system boundary and relevant operating conditions.
02
Investigate the production risks
Examine relevant architecture, code, tests, configuration and operating evidence. Validate findings and distinguish strengths from weaknesses.
03
Establish the readiness judgment
Explain conditions for proceeding, material limitations and a prioritized remediation direction.
Implementation handoff
What engineering can act on
A remediation item connects the finding, evidence, consequence, priority and recommended action. A targeted fix can go directly to your engineers for planning and verification; another Sparkling engagement is not automatically needed.
When the response changes component, data or integration boundaries, a path decision or architecture design may be useful. A full build-ready backlog is included only if explicitly agreed in the scope.
Scope & responsibility
Agree the depth. Keep the boundaries clear.
Scope of the engagement
A limited screen and an integrated assessment support different conclusions. The chosen depth, source access, system complexity and specialist work determine effort and timing.
Appropriate reliance
This is an evidence-based judgment at a point in time, not a guarantee of future performance, a penetration test or compliance certification. Remediation implementation and later rechecks are separate scopes.
One accountable principal. The named architect directs the work and owns the integrated recommendation. Relevant specialists contribute where agreed. Client and partner teams implement and operate; clients retain final business and acceptance decisions.
The agreed engagement sets the coverage, deliverables, responsibilities, timing and fees. Changes to that scope are agreed explicitly.
Initial assessment or a defined gate? This package sits within Assess: investigate the current product and establish the conditions for its next stage. A scoped recheck or acceptance judgment against agreed criteria is an Assure contribution. Explore Assure
Relevant experience
Read the work in its actual context.
Practical questions
Before engaging us.
Is this an automated code scan?
No. Tools help investigate the evidence. The principal validates material findings, interprets business consequences and owns the recommendation.
Do you assume AI-built software needs a rewrite?
No. A useful assessment recognizes sound choices and separates necessary changes from unnecessary replacement.
Can you review software not built with AI?
Yes, where the system and scope fit the available architecture expertise. The assessment addresses readiness for the next stage, regardless of which coding tools were used.
Related work
Related architecture contributions
Each contribution is available as a standalone service when the evidence and scope support it.
What is the decision you need to make?
Share the situation and the intended commitment. We will establish whether this scope fits.