User needs still have to map to product function. Most vibe-coded products fail because nobody traced what the user actually needs to what the product actually does. Fine Science closes that gap before you waste another quarter scaling the wrong thing.
You can vibe-code
the product.
You can't vibe-code
the evidence
Fine Science tells you whether your AI-built product meets a real user need, and what to fix first if it doesn't. Before you build more, launch or raise.
Builders, founders,
agencies - anyone with a product that isn't working
Your PMs can build a working prototype in an afternoon. That makes it easy to fund the wrong thing by Friday. Prototype Review tells you which user needs the prototype actually serves, which are assumed, and where it lands on the Fine Science scale: Structurally Sound, Needs Surgery or Rebuild Required.
See Prototype Review →You shipped fast. Before you spend on launch or a raise, find out whether it meets a real need and what is stopping people using it. Start with a Rapid Diagnosis, or a Teardown if you are pre-revenue.
The vibe-coding goldrush is real. The failures are too
"We spent a fortune with the agency and it isn't selling." Fine Science hears this every week. The product works. The problem is it was never built around what users actually need.
A weekend build is cheap. Long-term failure is not. AI collapsed the cost of shipping, not the cost of misreading demand. You can vibe-code fast. You cannot vibe-code the evidence that would have told you the product was wrong.
Code auditors check whether it works. Fine Science checks whether anyone needs it.
- Scans heuristics
- Scores interfaces
- Follows checklists
- Feels user confidence rising or collapsing in real usage
- Spots the gap between the founder message and what the product actually communicates
- Matches cross-industry patterns and names the failure mode quickly
Ways to work with Fine Science,
priced up front
Every service has a defined output and a stated price, so you know exactly what you're buying before you commit.
One-off diagnostics
Retainers
Training
Teardown
Rapid Diagnosis
A cold walk-through of your product by a senior practitioner with 20 years of pattern recognition. No report. No deck. A structured 60-minute verbal debrief covering the three to five most significant problems observed, with an honest assessment of whether they are surface-level fixes or structural failures. Hard-scoped, not a taster. One walk-through, one debrief, one page of findings. It exists for founders who need a credible outside eye before committing to a full engagement.
The £1,500 is credited in full against Laboratory Analysis if commissioned within 30 days. This is not a taster. It is a risk-free first step into the engagement.
Prototype Review
Laboratory Analysis
A structured expert evaluation that maps every feature to the need it serves and the benefit it claims to deliver. Every finding is grounded in observable behaviour, not assumption. Covers onboarding integrity, positioning accuracy, journey failure points, need-feature alignment and retention signals. Works for live products and pre-launch builds. Concludes with a clear verdict and a sprint-ready plan your team can act on immediately.
The £1,500 Rapid Diagnosis fee is credited in full against Laboratory Analysis if commissioned within 30 days.
Fine Science On Call
A standing engagement for teams who want priority access to senior diagnostic input without commissioning a full project each time. One monthly review call, up to three product reviews per month. Each review is a structured evaluation of one product, feature area or problem statement, delivered as a written findings note. A monthly findings memo and priority escalation when something critical surfaces. Quarterly summary report included.
On Call for Teams
Learn the method
Live, with Dr Nick Fine
Fine Science teaches the same diagnostic method it uses on client work. Live cohorts for individuals, in-house sessions for teams.
Build the Right Thing with AI
A four-week live course for product managers, designers and founders who prototype with AI. Take one of your own prototypes through a needs check and a five-user test, and leave with a verdict on the Fine Science scale: Structurally Sound, Needs Surgery or Rebuild Required.
Team Training
The Fine Science method for product managers who prototype with AI. How to check a prototype against real user needs before it goes to engineering. Your actual prototypes are the subject.
A diagnosis
in practice
One anonymised example of the kind of problem Fine Science is brought in to diagnose and what changed once the underlying issue was made visible.
The client had launched, traffic was arriving and sign-up was happening, but almost nobody reached the first moment of value. Internally, the debate had split between fixing the messaging, redesigning onboarding or rebuilding the feature set.
The failure was structural rather than cosmetic. New users were being asked for commitment before the product had established credibility, so the journey created doubt before it created momentum.
The team paused launch spend, rewrote the first-run journey and relaunched two weeks later with measurably better activation.
Structured
Not guesswork
Fine Science is expert opinion - but it's expert opinion applied through a repeatable diagnostic framework, not a vibe check. Every finding is traced to a specific observation or behavioural pattern. The methodology is transparent. The reasoning is visible. You can disagree with the verdict, but you can see exactly how it was reached.
A brief is taken, precise questions are asked, then the product is worked through independently before any conclusions are formed. The client's view of what works is noted and set aside.
The product is experienced as a new user would experience it. Every friction point, dead end and unmet expectation is documented without reference to the client brief.
Each feature is mapped against the need it serves and the benefit it claims to deliver. Root causes are identified - not just symptoms.
Findings are grouped by severity and type. Every recommendation is specific and actionable. "Improve onboarding" is not a recommendation. Changing a specific step is.
A clear verdict is stated. The report is written in plain English - no jargon, no padding. Then a debrief call where the client can ask hard questions and get straight answers.
- Scores the interface against a checklist
- Identifies heuristic violations
- Produces a list of recommendations
- Tells you what looks wrong
- Uses the product as a new user would
- Identifies root causes, not surface symptoms
- Delivers a verdict you can act on
- Tells you why it is broken and what to do first
A heuristic checklist can tell you a button is hard to find. It cannot tell you that users are abandoning because the product asked for commitment before it established credibility. That is the difference.
Fine Science gives
verdicts, not suggestions
Every diagnostic ends in an unambiguous verdict on this one scale. Not a list of things to consider. A professional opinion you can act on.
Structurally Sound
The product has problems but they're fixable without fundamental rethinking. The priority stack tells you what to do and in what order.
Needs Surgery
One or more structural failures need to be addressed before surface-level fixes will have any effect. Specific surgery required before you scale.
Rebuild Required
Fundamental need-feature misalignment that can't be resolved incrementally. Rare - but when warranted, Fine Science will say so honestly.











20 years of
pattern recognition
One discipline
• B2B and B2C platforms
• Internal tools
• Consumer apps
• Regulated environments
• Enterprise platform teams
• Regulated and compliance-heavy environments
• Consultancy product work
Client-side taught consequences and long-term thinking. Agency taught speed and client variety. The diagnostic method draws on both.
• Analysing conversion funnels
• Diagnosing drop-off points
The difference between testing randomly and testing with a hypothesis grounded in behavioural analysis. CRO isn't guesswork - it's structured experimentation with a diagnostic foundation.
He had been practising it since 2009. The academic foundation is a PhD in HCI from Brunel University and an MSc from University College London. Published research covers behavioural analysis and personalised interface design. The training matters because it's why every finding is structured, traceable and defensible - not just observed.
11 podcast appearances including Brave UX, One Knight in Product and Human Tech - where UX Psychology was first named publicly in March 2018. Regular contributor to industry debate on the future of UX, the limits of AI tooling and the case for evidence-based practice.
A talk that shows how Fine Science thinks - recorded live
"Most product failures aren't technical. They're behavioural. The product works fine - it just doesn't work the way real people think."
The laboratory
is open
Tell us what the product is and what's wrong with it. Fine Science will confirm which service fits and whether it's the right match for the problem.
MSA and custom invoicing available for enterprise engagements. Data handling terms on request.
- Product URL
- What it is built with
- The decision you need to make
Or message Dr Nick Fine on LinkedIn
Not sure which fits? Teardown if you're pre-revenue, Rapid Diagnosis if you're about to launch or raise, Prototype Review if you're a product team.