FIXED-SCOPE TECHNICAL REVIEW

3-Day Technical Risk Review

Decide what to stabilise, rewrite or stop before you spend another month of runway.

Scope the decision

WHO IT'S FOR

Who it's for

Funded founders & CTOs

A live system, a dated decision and too much uncertainty about what to fix first.

Investors & acquirers

An independent technical read before capital, acquisition or the next milestone.

Inherited or unstable systems

A new technical owner, production incident or release delay exposed wider architecture risk.

WHAT I ASSESS

What I assess

Architecture and maintainability · Dependencies and supply-chain risk · Testing, CI/CD and observability · Security red flags within scope · Ownership and bus factor · Roadmap feasibility · AI/data/model pipeline and governance unknowns when relevant

PROCESS

Process

  1. Scope (20 minutes)

    Confirm the decision, deadline, access, stakeholders and whether a review is the right next step.

  2. Book and review (3 business days)

    50% booking payment, complete access checklist, then focused evidence review.

  3. Decide

    60-minute readout plus decision memo, prioritised risk register and 30-day stabilisation plan.

WHAT YOU GET

What you get

Decision memo · Prioritised risk register with evidence · 30-day stabilisation plan · Evidence appendix and unknowns · 60-minute readout · One written clarification round

PRICING

Pricing

3-Day Technical Risk Review

$3,500 fixed

50% to book · 50% before final readout and report release · One product/system · one decision context · up to three primary repositories

Need ongoing technical ownership instead of a standalone review? Fractional Head of Engineering from €4,800/month for four days.

WHAT THIS IS NOT

Explicit non-goals

Not implementation · Not a line-by-line code audit · Not penetration testing · Not legal or financial diligence · Not certification · Not a guaranteed rebuild estimate

DECISION READINESS

Do You Have Sufficient Evidence to Decide?

If you are evaluating whether an independent review is required, download the 12-question technical decision scorecard to assess visibility gaps before committing capital or engineering runway.

Stabilise, Rewrite or Pause? — 12-Question Scorecard (PDF)

A 12-question technical decision scorecard to evaluate whether you have sufficient evidence to decide before committing capital or engineering runway.

Request it by email.

Request by email

PROOF

Proof

These are reproducible methodology demos, not client endorsements or final verdicts on the open-source projects shown.

See public evidence packs · Rust due-diligence toolkit

ℹ

Direct Technical Scoping via Email

To reduce exposure and agree on the appropriate communication channel for your system, intake requests are handled directly via email with Jose Robles.

Email Jose Robles (jose@josedrobles.com)