Townhouse 2.0

UKBT Institute · FORTRESS R&D

The Townhouse 2.0

Where Innovation Meets Reality

The Practitioner Readiness Level (PRL) framework enforces practitioner pull over technology push, turning the linear R&D pipeline into a co-creative process that reduces failure rates and accelerates adoption.

Get InvolvedExplore the Framework

10-Stakeholder Townhouse Model

All 10 validate at PRL 3. Select a voice to see the question they answer.

The Innovation Crisis We're Solving

Stalled

High UK R&D project failure rates: many never reach production

Unadopted

Significant adoption gaps despite technical viability in public sector innovation

£50B

annual UK business R&D investment with stagnant real-term growth since 2018

Of the projects that do reach production, many still fail to win practitioner adoption. There is a clear need for better validation frameworks that ensure innovations actually work for the people who need them.

Why We Exist

PRL introduces a rigorous, evidence-based measurement system that validates practitioner adoption intent and workflow integration before capital is committed to technical development. Integrated within FORTRESS R&D's four-stage model—Collaborate, Experiment, Build, Scale—the PRL framework creates a structured pathway from problem identification through to sector-wide standardisation. All 10 stakeholders validate at PRL 3, ensuring comprehensive risk assessment.

Access for All

We help technologists, professionals, and communities access emerging technologies and explore real-world problems across sectors—from women's health to education, legal services to supply chains.

Home-Grown Talent

We provide home-grown talent into sectors that couldn't previously access it. Fresh eyes, new thinking, diverse perspectives—this is how we transform industries.

Permission to Fail

A safe space to test, fail, and move on if the solution doesn't make sense. Startups can't afford traditional R&D—we're creating an affordable, practitioner-led alternative.

Interdisciplinary Innovation

We bring together not just tech professionals, but health workers, teachers, community leaders, lawyers, and sector professionals to provide a holistic perspective on technology.

Supporting the Tech Ecosystem

Our aim is to explore as many sectors as possible, bringing new talent and thinking while supporting the tech ecosystem to build better tools that actually work.

Practitioner Pull > Tech Push

We enforce practitioner pull over technology push, transforming R&D from a linear pipeline into a co-creative innovation process that reduces failure and accelerates adoption.

How the Townhouse Works

The Townhouse is where we bring together experts and individuals beyond tech. It's a four-floor collaborative space that transforms how innovation happens—replacing technology push with practitioner pull.

Floor 4: SCALE

Growth & Markets + Promotion & Ecosystem

The Scale stage encompasses both operational expansion (PRL 8) and sectoral transformation (PRL 9), where solutions transition from early adopter communities to mainstream practice. This stage requires different capabilities than development—specifically, infrastructure for training, support, and continuous improvement.

Floor 3: BUILD

Practitioner-Led & Research

The Build stage formalises the transition from validated prototype to production-ready solution, with practitioner champions taking co-ownership of development roadmap and academic partners embedding rigorous research methodologies. This stage prevents the common failure mode where early adopter enthusiasm does not translate to broader organisational adoption.

Floor 2: EXPERIMENT

Stress Test & Validate

The Experiment stage subjects potential solutions to rigorous practitioner-led testing, progressing from low-tech analogue prototypes through to digital workflow integration. This stage enforces the principle that technology is a solution enabler, not a solution itself—if the fundamental approach doesn't work in analogue form, adding technology will not rescue it.

Floor 1: COLLABORATE

Knowledge Transfer & Discovery

The Collaborate stage establishes the foundational requirement for all subsequent R&D activity: practitioner-validated problem identification. This stage prevents the all-too-common scenario where innovations are developed in response to perceived rather than actual practitioner needs.

Who We Bring Together

The Townhouse 2.0 is intentionally interdisciplinary. We believe better technology emerges when diverse perspectives collide. This isn't just about technologists—it's about humanity.

Technologists

Health Workers

Teachers

Lawyers

Community Leaders

Sector Professionals

Right Person, Right Question, Red Flag Answer

The 10 stakeholders you must validate with, the critical questions to ask, and the red flag answers that signal failure

1

PRACTITIONERS

Daily End Users

Right Question:

"Do you face this problem daily?"

Active PRL Stages:

PRL 1-2, 5-6, 8

Validates:

Problem frequency; workflow reality; operational pain

Catches:

Low-frequency problems; theoretical issues; nice-to-haves

Red Flag Answers:

  • "Occasionally"
  • "Sometimes"
  • "Not urgent"
2

CUSTOMERS

Budget Authority

Right Question:

"Will you pay real money for this today?"

Active PRL Stages:

PRL 3, 9

Validates:

Economic signal; willingness-to-pay; purchasing authority

Catches:

Speculative interest; no budget; 'after v2' syndrome

Red Flag Answers:

  • "Let me think"
  • "After v2"
  • "Maybe later"
3

ACADEMICS

Research/Evidence

Right Question:

"Is this domain scientifically promising?"

Active PRL Stages:

PRL 1, 4

Validates:

Technical feasibility; evidence base; fundamental principles

Catches:

Impossible ideas; violation of physics; no research basis

Red Flag Answers:

  • "Unclear"
  • "Needs more research"
  • "Violates physics"
4

SUPPLY CHAIN

Sourcing/Manufacturing

Right Question:

"Can we source, build, deliver this reliably?"

Active PRL Stages:

PRL 4-5

Validates:

Materials availability; manufacturing reality; logistics

Catches:

Can't source materials; impossible tolerances; scale barriers

Red Flag Answers:

  • "Can't source materials"
  • "Impossible tolerances"
  • "Scale barriers"
5

INTERNAL CHAMPIONS

Organizational Advocates

Right Question:

"Does our team need this yesterday to win?"

Active PRL Stages:

PRL 6-7

Validates:

Urgency; organizational priority; budget mobilization ability

Catches:

'Nice to have'; no urgency; can't mobilize budget

Red Flag Answers:

  • "Nice to have"
  • "Low priority"
  • "Can't mobilize budget"
6

MARKET

Timing/Competition

Right Question:

"Is the timing right or are we early/late?"

Active PRL Stages:

PRL 3, 6, 9

Validates:

Market readiness; competitive landscape; adoption timing

Catches:

Too early/late; saturated market; bad timing

Red Flag Answers:

  • "Too early"
  • "Too late"
  • "Saturated market"
7

BUDGET HOLDERS

Finance Decision Makers

Right Question:

"What's the budget cycle and approval process?"

Active PRL Stages:

PRL 3

Validates:

Funding pathways; procurement timelines; budget availability

Catches:

18-month cycles; no discretionary budget; wrong fiscal year

Red Flag Answers:

  • "18-month cycles"
  • "No discretionary budget"
  • "Wrong fiscal year"
8

FINANCE/PROCUREMENT

Economic Reality

Right Question:

"What's the real Total Cost of Ownership?"

Active PRL Stages:

PRL 3, 8

Validates:

TCO calculation; buying process; payment terms; unit economics

Catches:

Hidden costs; 90-day payment terms; integration costs

Red Flag Answers:

  • "Hidden costs"
  • "90-day payment terms"
  • "Integration costs"
9

LAWYERS/REGULATORY

Compliance/Risk

Right Question:

"What are the regulatory barriers and costs?"

Active PRL Stages:

PRL 3

Validates:

Compliance requirements; approval timelines; liability costs

Catches:

MHRA 2-year delay; indemnity kills margins; no approval path

Red Flag Answers:

  • "MHRA 2-year delay"
  • "Indemnity kills margins"
  • "No approval path"
10

TECHNOLOGISTS

Implementation

Right Question:

"Can we actually build this? What's cost-to-serve?"

Active PRL Stages:

PRL 1, 4-5

Validates:

Implementation reality; technical architecture; scalability

Catches:

Cost-to-serve scales wrong; technical debt; infrastructure costs

Red Flag Answers:

  • "Cost-to-serve scales wrong"
  • "Technical debt"
  • "Infrastructure costs"

Real-World Examples

Practitioner

Daily User

Question

"Does this save you 2+ hours a week?"

Red Flags

"Maybe"

"I'd try it"

Why It Matters

If practitioners can't definitively say yes, the problem isn't urgent enough.

Customer

Pays

Question

"Will you pay £X today to fix this?"

Red Flags

"Let me think"

"After v2"

Why It Matters

Delayed payment signals low urgency or misaligned value proposition.

Frontline Operator

End User

Question

"Would you fight to keep this tool?"

Red Flags

"Silence"

"Shrugs"

Why It Matters

If operators won't advocate for the tool, adoption will fail.

Never skip a voice. If any stakeholder gives a red flag answer, pause and pivot before investing further.

The Townhouse methodology ensures all 10 stakeholders validate before progression. Core Principle: "Never skip a voice" - All stakeholders validate at PRL 3.

The Practitioner Readiness Level (PRL) Framework

A Pioneering UK R&D Validation Model | Integrated with FORTRESS Four-Stage Innovation Pipeline

The PRL framework ensures every innovation moves up only when practitioners have validated it, only when it solves real problems. Each level requires rigorous evidence before progression.

PRL 1COLLABORATE · Knowledge Transfer & Discovery

Is the problem practitioner-identified and operationally significant?

Evidence:
1-3 practitioners articulate top-3 pain
Ask Practitioner (Daily User):
"Do you face this problem daily?"
Red flag:
Occasionally or Sometimes
Framework alignment
TRL: Basic principles observed · CRL: Hypothetical commercial proposition
PRL 2COLLABORATE · Knowledge Transfer & Discovery

Is this an industry-wide problem or localized pain point?

Evidence:
≥10 practitioners across organisations confirm; sector mapping validates scope
Ask Practitioners (Sector Cohort):
"Is this a sector-wide problem or just your organisation?"
Red flag:
Only 1-2 organisations face it
Framework alignment
TRL: Technology concept formulated · CRL: Commercial proposition formulated
PRL 2.5COLLABORATE · Knowledge Transfer & Discovery

Will practitioners and domain experts commit time to solution development?

Evidence:
≥5 practitioners commit scheduled time; LOI for pilot participation
Ask Practitioners (Pilot Participants):
"Will you commit 10+ hours over 2 weeks to test solutions?"
Red flag:
Maybe later or If we have time
Framework alignment
TRL: — · CRL: —
PRL 3COLLABORATE · Knowledge Transfer & Discovery

Have all ecosystem stakeholders been consulted across the value chain?

Evidence:
All 10 stakeholder voices validated; economic signal confirmed
Ask Customer (Pays) + 10 Stakeholders:
"Will you pay £X today to fix this?"
Red flag:
Let me think or After v2
Framework alignment
TRL: Experimental proof of concept · CRL: Applied research based on market reality
PRL 4EXPERIMENT · Stress Test & Validate

What technology innovation type is proposed and what baseline performance exists?

Evidence:
Tech classified; ≥70% task completion in analogue pilot
Ask Supply Chain + Academics:
"Can we source, build, deliver this reliably?"
Red flag:
Can't source materials or Impossible
Framework alignment
TRL: Technology validated in lab · CRL: Small-scale pilot commercially valid
PRL 5EXPERIMENT · Stress Test & Validate

Does technology demonstrate utility, impact, or originality in real-world conditions?

Evidence:
Measurable workflow impact; practitioners validate usefulness
Ask Practitioner (Daily User):
"Does this save you 2+ hours per week?"
Red flag:
Maybe or I'd try it
Framework alignment
TRL: Technology validated in relevant environment · CRL: Large-scale pilot commercially validated
PRL 6EXPERIMENT · Stress Test & Validate

Can innovation withstand multi-stakeholder adversarial testing?

Evidence:
NPS ≥80; TVR ≥10; cross-sector stress test passed
Ask Frontline Operator + Market:
"Would you fight to keep this tool?"
Red flag:
Silence, shrugs, or It's okay
Framework alignment
TRL: Technology demonstrated in relevant environment · CRL: Commercial trial with repeat customers
PRL 7BUILD · Practitioner-Led & Research

Can innovator demonstrate documented practitioner impact?

Evidence:
≥1 peer-reviewed case study; academic validation
Ask Internal Champion:
"Does your team need this yesterday to win?"
Red flag:
Nice to have or Eventually
Framework alignment
TRL: System prototype in operational environment · CRL: Commercial launch with market traction
PRL 8SCALE · Growth & Markets

Will practitioners sustain adoption beyond proof-of-concept?

Evidence:
≥100 users; 90% retention; 30% referral; week-long operational trial
Ask Community (Peer Network):
"Would you recommend this to peers?"
Red flag:
<30% referral rate
Framework alignment
TRL: System complete and qualified · CRL: Scaling product/business
PRL 9SCALE · Promotion & Ecosystem

Has innovation achieved commercial validation and sector adoption?

Evidence:
≥1 paying customer with contract; community of practice; policy influence
Ask Market + Customer:
"Is this becoming sector standard?"
Red flag:
No ecosystem effects visible
Framework alignment
TRL: System proven in operational environment · CRL: Sustainable business model proven

The Complete PRL Framework

Select a level for its evidence requirements, collaboration mechanisms, failure modes and gate threshold.

PRL 1
COLLABORATE

Practitioner-Identified Problem

Core Question:

Is the problem articulated by practitioners in their operational context?

Evidence Requirements

  • 1-3 domain practitioners independently identify pain point as top-3 operational challenge
  • Problem documented using practitioner's own terminology (not researcher language)
  • Problem manifests ≥3 times per week in normal workflow conditions
  • Problem causation understood by practitioners (not just symptoms)

Collaboration Mechanisms

  • Knowledge Transfer Roundtables: Structured problem surfacing sessions convening cross-sector practitioners (NHS clinicians, teachers, solicitors, supply chain managers, public sector workers)
  • Problem Mapping Workshops: Facilitated sessions to distinguish root causes from symptomatic complaints
  • Cross-Sector Peer Review: Practitioners from adjacent domains validate whether analogous problems exist

Failure Modes & Pivot Actions

Impossible Problem

No known solution pathway within 5-year horizon → Research alternative problems within same practitioner domain

Impractical Problem

Solution requires systemic change beyond capacity → Narrow scope to addressable sub-problem

Non-Urgent Problem

Cannot articulate consequences of non-resolution → Research what practitioners consider genuinely urgent

🎯 Gate Threshold: Problem must score ≥60/100 on urgency-feasibility matrix to progress to PRL 2

Gates, Red Flags & Scoring

The rules that decide whether an innovation earns the right to move up a level.

Rule: Any red flag at designated PRL level = automatic gate failure

Recognize red flag signals early to prevent costly failures. Each red flag triggers immediate pivot or kill decision.

PRL 1-2

Red Flag Signal:

"Occasionally / Sometimes"

What It Means:

Low frequency; not urgent; not top-3 pain

Immediate Action:

KILL or pivot to higher-frequency problem

PRL 2.5

Red Flag Signal:

"Maybe later / If we have time"

What It Means:

No commitment; low priority

Immediate Action:

KILL or find practitioners with urgency

PRL 3

Red Flag Signal:

"Let me think / After v2"

What It Means:

No willingness-to-pay; speculative interest

Immediate Action:

KILL or pivot value proposition

PRL 3

Red Flag Signal:

"Too early / Too late"

What It Means:

Market timing wrong

Immediate Action:

KILL or wait for market readiness

PRL 4

Red Flag Signal:

"Can't source / Impossible"

What It Means:

Technical/supply chain impossibility

Immediate Action:

KILL or research alternative approaches

PRL 5

Red Flag Signal:

"Maybe / I'd try it"

What It Means:

Marginal benefit; insufficient impact (<2 hours/week)

Immediate Action:

Redesign for 10x impact or KILL

PRL 6

Red Flag Signal:

"Silence / Shrugs / It's okay"

What It Means:

Not mission-critical; won't defend it

Immediate Action:

KILL; will never achieve adoption

PRL 7

Red Flag Signal:

"Nice to have / Eventually"

What It Means:

No urgency; won't mobilize budget

Immediate Action:

KILL or find different champion segment

PRL 8

Red Flag Signal:

"<30% referral rate"

What It Means:

Poor product-market fit; retention will collapse

Immediate Action:

Fix core value proposition or KILL

PRL 9

Red Flag Signal:

"No paying customers"

What It Means:

Business model broken; no commercial validation

Immediate Action:

Pivot business model or KILL

Why PRL Catches More Failures Than TRL + CRL Combined

The Synthesis Effect: The Townhouse IS the Mechanism That Powers PRL

The Synthesis Effect

PRL catches Technical + Commercial + Regulatory + Operational + Adoption issues simultaneously and early

TRL: Technical impossibility (eventually, through expensive experiments)
CRL: Business model issues (eventually, through expensive market testing)
PRL: All failure modes at once, in weeks not years

10 Stakeholder Perspectives

10 stakeholder perspectives > sum of individual insights

  • •Cross-disciplinary challenges surface hidden assumptions
  • •Non-stakeholder perspectives (from other sectors) provide novel solutions
  • •Constructive criticism early >> expensive pivots late

Early Failure Detection

Catch failures early (weeks not years, £10K not £1M)

Time

Weeks vs Years

Cost

£10K vs £1M

Failure

87% → <20%

Two-Way Knowledge Transfer

Innovators learn, practitioners gain visibility

  • •Practitioners understand emerging technologies
  • •Innovators understand real-world constraints
  • •Mutual learning creates better solutions

Stakeholder Buy-In

Validation participants become champions

Early engagement creates advocates who drive adoption

Constructive Challenge

Safe space to expose flaws before investment

Fail fast, fail cheap, learn quickly

Cross-Sector Innovation

Insights from one field solve problems in another

  • •Healthcare solutions inform education tools
  • •Legal tech insights improve supply chain systems
  • •Sector-agnostic problem solving

The Four Rules That Reduce Innovation Failure from 87% to <20%

"Never skip a voice"

Validate with all 10 stakeholders before proceeding

Impact: Catches hidden barriers early

"Test simple before mass tech implementation"

Low-cost pilots (paper/concierge/no-code) before building

Impact: Validates approach before expensive development

"Co-create, don't dictate"

Work shoulder-to-shoulder with practitioners

Impact: Builds ownership and adoption commitment

"Share everything"

Build in public; publish learnings

Impact: Enables others to copy, improve, or join

"The Practitioner Readiness Level framework isn't just a scoring system - it's a convening methodology that brings together diverse expertise to catch failures early, create two-way knowledge transfer, build stakeholder buy-in, enable constructive challenge, and generate cross-sector innovation."

The power of PRL is the power of the Townhouse

Enter the Townhouse

Join us in transforming UK innovation. Choose the path that fits you.

Practitioners

Bring a problem

Frustrated with solutions that don't work? Tell us the problem you face every day.

Get Involved

Innovators & startups

Validate before you build

Can't afford traditional R&D? Test your idea with the people who'll actually use it.

Get Involved

Academics & partners

Join the Townhouse

Researchers, funders, legal, finance and supply chain experts: become one of the 10 voices.

Get Involved
View Framework Comparison