Independent technical assessment
An experienced, independent look at what you've built - before your next big decision.
A Technical Reality Check is a focused, independent assessment of what is working, what is worrying, and what should happen next.
Who it is for
When the problem is real but the explanation is not clear.
- Development is taking much longer than expected.
- A project is late, stuck, or getting steadily more expensive.
- You cannot tell whether a team or agency is performing well.
- You are considering replacing developers or changing technical direction.
- Architecture or technical debt may be slowing the business down.
- You are about to approve a large technical investment.
- You inherited a product or codebase that nobody fully understands.
What I examine
Enough evidence to make the next decision - not a ritual audit of everything.
Goals and decisions
What the business is trying to achieve, what has actually been decided, and where ambiguity is entering delivery.
Delivery reality
Plans, progress, bottlenecks, dependencies, quality expectations, and how work currently moves from idea to production.
Team and ownership
Responsibilities, communication, incentives, vendor relationships, and whether the right decisions have clear owners.
Technical risk
Architecture, code, infrastructure, data, and security - including how much AI-generated code has crept in, and how well anyone understands it.
Vendors, docs, and alignment
Whether outside vendors, documentation, and the technical direction actually line up with where the business is going.
What happens next
The smallest practical actions that reduce uncertainty and improve the next 90 days.
Access depends on the question. Some situations can be clarified through conversations, plans, contracts, and delivery artifacts. Others require repository, infrastructure, or data access. Scope and access are agreed before the assessment begins.
How it works
Understand. Prioritize. Act.
This isn't about finding everything that's wrong. It's about understanding where you are and making better decisions about what comes next.
Understand
I look at what you've actually built - architecture, code, delivery, team, and how it got here - broadly enough to see the real picture, not just the parts that are easiest to inspect.
Prioritize
Not everything matters equally. I separate what's genuinely risky from what merely looks messy, and tell you plainly which is which.
Act
You leave with a clear, practical view of what to address first, what to leave alone for now, and what your sensible next steps actually are.
What you receive
A usable decision, following Understand → Prioritize → Act.
- • A concise written view of what is solid, unclear, and risky.
- • Important risks separated from distracting technical noise.
- • Practical priorities and decisions for the next 90 days.
- • A walkthrough with the people responsible for acting on it.
What it is not
Not a sales device disguised as an audit.
- • Not a guarantee that every problem will be found.
- • Not automatically a line-by-line code review.
- • Not a search for reasons to replace the current team.
- • Not an obligation to work together afterward.
A completely valid conclusion is: your team is doing fine, the architecture is appropriate, and the right next step is simply to let them continue.
What happens next
No mystery about what you're agreeing to.
01
Short conversation
We spend around 20-30 minutes understanding why you're looking for an outside view and what decision you're facing.
02
Agree on scope
I tell you what I think is worth examining, what access I need, and what isn't necessary.
03
Reality Check
I review the relevant product, technology, delivery, team, and supporting material based on the agreed scope.
04
Findings
You get the concise written assessment, and we walk through it together, including priorities and practical next steps.
Start with the situation, not a formal brief.
A few sentences are enough. I will review them and tell you whether this assessment - or another next step - would be useful.
Get a Technical Reality CheckMost engagements end here. Some continue into fixing what's found, or ongoing technical partnership - only if it makes sense.