Home/Methodology

How PROTHEUS Works

Architecture-first analysis powered by 12-agent hybrid system: deterministic validation rules + generative agents. Full transparency into our methodology.

πŸ” Transparent Methodology

Unlike Copilot or ChatGPT, PROTHEUS shows you exactly how it approaches feasibility:

  • βœ“ Architectural validation constraints (immutable rules)
  • βœ“ Budget calculations (effort Γ— regional rates Γ— overhead)
  • βœ“ Market data sources (current regional rates)
  • βœ“ Clear assumptions (overhead factors, coordination buffers)
INPUT
5 min
Brief, budget, timeline, team
ANALYSIS
12
Multi-agent pipeline
OUTPUT
30-50
Pages (ADRs + Stories + Budget)
4-PHASE ANALYSIS PIPELINE
PHASE 1: CONTEXT ANALYSIS
Knowledge Base Query
β€’ Known technical patterns and anti-patterns
β€’ Current market rates by region and skill level
β€’ Domain complexity factors and common pitfalls
β€’ Regional coordination overhead estimates
PHASE 2: DETERMINISTIC VALIDATION
Module 1:Project Tier Classification
Module 2:Budget Feasibility Validation
Modules 3-11:Architectural Constraint Validation
β†’ All checks use deterministic logic (no probabilistic guessing)
PHASE 3: GENERATIVE LAYER (STRATEGIC LLM USE)
Agent A:Architecture Design
β†’ Generates modular structure and component breakdown
Agent B:User Stories Generation
β†’ Creates epics with acceptance criteria and prioritization
Agent C:Commercial Opportunities
β†’ Identifies potential revenue models and monetization paths
β†’ Strategic LLM use for creative tasks (not excessive API calls)
PHASE 4: QUALITY VALIDATION
AUTOMATED TESTS
13+
Schema validation, completeness checks
OBJECTIVE ANALYSIS
Final
LLM validates logical coherence

Architectural Guardrails

Immutable validation constraints that catch fatal flaws before you write code. Zero hallucination in these checks.

1

Technology Fit

Ensures technology choices match project tier and complexity. Prevents over-engineering MVPs or under-tooling enterprise projects.

βœ“ Stack Appropriateness

Validates that architectural patterns align with project scope and team capabilities. Example: Microservices require justification for complexity tier.

βœ“ Architecture Compatibility

Detects technical impossibilities in stack combinations. Example: Validates if chosen framework supports required real-time features.

2

Resource Alignment

Validates that budget, timeline, and team capabilities align with project requirements.

βœ“ Timeline Feasibility

Accounts for team learning curves when new to technologies. Adds realistic time estimates for skill development.

βœ“ Budget-Cost Balance

Validates infrastructure and operational costs are sustainable within project budget. Flags excessive infrastructure spending early.

βœ“ Team Skills Match

Identifies critical skill gaps requiring training or additional resources. Prevents committing to tech stacks outside team expertise.

βœ“ Budget Capacity

Rejects projects where budget gap exceeds recoverable threshold. Prevents financially unviable commitments.

3

Completeness & Security

Ensures all critical components are present and security baselines are met.

βœ“ Feature Completeness

Validates domain-specific mandatory features are included. Example: E-commerce requires catalog, cart, orders, and payment processing.

βœ“ Security Baseline

Enforces minimum security requirements appropriate to project tier. External authentication and secure communication mandatory.

βœ“ Setup Complexity

Validates infrastructure setup time aligns with project tier and timeline. Prevents complex orchestration for rapid delivery requirements.

Why These Guardrails Matter:

These validation constraints catch fatal flaws before you write a single line of code. They're based on 25+ years of architecture experience, codified as deterministic logic. No probabilistic guessingβ€”just hard constraints that protect your project.

Multi-Factor Viability Model

How PROTHEUS calculates the Viability Score (0-100) using weighted risk assessment.

HighTimeline Risk

Realistic estimate vs client's deadline. Primary risk factor in most projects.

Assessment factors:
β€’ Scope-timeline alignment
β€’ Regional coordination overhead
β€’ Learning curve requirements
β€’ Critical path dependencies
MedTeam Risk

Skills match, capacity, and coordination overhead assessment.

Assessment factors:
β€’ Skill-technology alignment
β€’ Team size appropriateness
β€’ Experience with similar projects
β€’ Availability and commitment
MedComplexity Risk

Domain difficulty, compliance requirements, and integration complexity.

Assessment factors:
β€’ Domain expertise required
β€’ Regulatory compliance needs
β€’ Third-party integrations
β€’ Technical novelty
LowScope Risk

Feature creep probability and requirements clarity assessment.

Assessment factors:
β€’ Requirements specificity
β€’ Stakeholder alignment
β€’ Change history patterns
β€’ Scope flexibility

Example Assessment:

Timeline Risk: Significant gap detectedWeighted contribution
Team Risk: Skills alignment moderateWeighted contribution
Complexity Risk: High compliance needsWeighted contribution
Scope Risk: Clear requirementsWeighted contribution
Final Viability Score:54/100
β†’ VERDICT: MODERATE RISK (recommend timeline or scope adjustment)

What You Get: 9 Documents

Complete architecture package: 30-50 pages of actionable insights. Not a summaryβ€”a full feasibility study.

01

Viability Score (0-100)

Multi-factor risk assessment combining timeline, team capacity, complexity, and scope flexibility

Example: 78/100 (MODERATE RISK) β†’ Recommend adjusting timeline
02

Timeline Reality Check

Realistic timeline with location-adjusted coordination buffers

Example: Client wants 8 weeks β†’ Analysis suggests 12 weeks realistic
03

Budget Validation

Labor + infrastructure + compliance costs with current market rates

Example: Budget analysis shows feasibility within acceptable margin
04

Risk Assessment

Prioritized risks with mitigation strategies and cost impacts

Example: Compliance requirements β†’ Hire consultant, adjust budget & timeline
05

6-8 Architecture Decision Records (ADRs)

Technical decisions with context, options evaluated, and rationale

Example: ADR covering tier classification, stack selection, security approach
06

30-80 User Stories

MoSCoW prioritization with acceptance criteria and story points

Example: 42 stories with prioritized delivery sequence
07

Stack Recommendation (3-5 Options)

Technology choices with comparative analysis and trade-offs

Example: Multiple stack options with fit analysis and setup estimates
08

Sprint Plan (2-8 Sprints)

Dependency-aware sequencing with team velocity considerations

Example: 6-sprint delivery plan with dependency mapping
09

Compliance Checklist

GDPR, HIPAA, WCAG, PCI-DSS requirements with implementation effort

Example: Compliance requirements with cost and timeline impacts

Total Package:

30-50 pages of comprehensive analysis

Export formats: PDF, Markdown, JSON (API)

πŸ“‹ Illustrative Example (Not Real Project)

The scenario below demonstrates PROTHEUS methodology using realistic but fictional data. This is NOT a validated case study with actual client outcomes.

Validation Status: We're collecting real project data now. Once we have 20-50 completed projects with validated outcomes (Q3-Q4 2025), we'll publish actual case studies with client permission.

Example Scenario: Healthcare Appointment System

How PROTHEUS would analyze an MVP project with compliance requirements

CLIENT INPUT
Project: Healthcare appointment scheduling (MVP)
Requirements: Patient scheduling, SMS reminders, compliance needs
Team: 2 mid-level full-stack developers (React experience)
Client timeline: "4 weeks is ideal"
Client budget: Limited budget
Priorities: Fast time-to-market, security, low infrastructure costs
PROTHEUS ANALYSIS
TIER CLASSIFICATION
TIER: Mid-Complexity (Standard Web Application)
Rationale: Healthcare domain + compliance β†’ Beyond MVP scope
RECOMMENDED STACK
β”œβ”€ Frontend: Modern React framework
β”œβ”€ Backend: Managed backend service (auth + database)
β”œβ”€ Messaging: SMS service provider
└─ Rationale: Fast MVP iteration, built-in security, compliance-ready hosting
⚠ FINDING 1: TIMELINE GAP
β”œβ”€ Client wants: 4 weeks
β”œβ”€ Realistic estimate: Significantly longer
└─ Gap reason: Compliance adds substantial implementation time
β€’ Legal agreement reviews
β€’ Audit logging implementation
β€’ Security hardening requirements
⚠ FINDING 2: BUDGET CONSTRAINTS
β”œβ”€ Client budget: Limited
β”œβ”€ Realistic cost: Significantly higher
└─ Breakdown:
β€’ Development labor (realistic market rates)
β€’ Compliance-grade infrastructure
β€’ Third-party service integrations
β€’ Contingency buffer
β†’ ASSESSMENT: Budget insufficient for stated requirements
RISK FLAGS DETECTED
⚠ CRITICAL:Compliance requirements without specialist consultation
Mitigation: Engage compliance specialist, extend timeline for legal review
⚠ HIGH:Database security configuration complexity
Mitigation: Allocate time for security policy design and testing
⚠ MEDIUM:Third-party service integration testing
Mitigation: Additional time for webhook testing and validation
VIABILITY SCORE
TIMELINE RISK
High
Significant timeline gap
TEAM RISK
Med
Adequate skills, small team
COMPLEXITY RISK
High
Healthcare + compliance
SCOPE RISK
Low
Clear requirements
Final Viability Score:54/100
β†’ VERDICT: HIGH RISK - Not feasible with current constraints
PROTHEUS RECOMMENDATION

Option 1: Adjust Timeline + Budget

β€’ Extend timeline to realistic delivery window
β€’ Increase budget to cover compliance consulting
β€’ Revised viability: Significantly improved

Option 2: Reduce Initial Scope

β€’ Launch without full compliance (demo/internal only)
β€’ Shorter timeline achievable
β€’ Lower budget requirement
β€’ Revised viability: Acceptable risk level

Why This Example Matters:

This scenario demonstrates how PROTHEUS catches critical feasibility issues before you commit. Accepting the original proposal without analysis could result in:

  • β€’ Substantial budget overrun
  • β€’ Significant timeline slippage
  • β€’ Potential compliance violations (legal risk)
  • β€’ Total potential loss: Major financial impact

Scope & Limitations

Radical transparency: What PROTHEUS does and doesn't do

❌ What PROTHEUS Does NOT Do:

Replace Architects

PROTHEUS augments architects, it doesn't replace them. Human judgment required for final decisions.

Generate Executable Code

PROTHEUS analyzes pre-code phase (architecture, planning). Use Cursor/Copilot for code generation.

Guarantee Project Success

PROTHEUS reduces risk, it doesn't eliminate it. Success depends on execution, not just planning.

Analyze Maintenance/Legacy Projects

Optimized for greenfield (new builds). Brownfield analysis coming in Q3 2025.

Work with Non-Technical Projects

Requires software engineering scope (web, mobile, API, infrastructure projects only).

Handle Very Small Budgets

Minimum analysis threshold applies. Below that, too many unknowns for reliable prediction.

βœ… What PROTHEUS DOES Do:

Pre-Sales Validation

Perfect for agencies/freelancers: validate scope + budget BEFORE signing contract.

Sprint 0 Planning

Generate ADRs, user stories, sprint plan for initial sprints.

Budget Negotiation

Data-driven timeline/cost estimates with regional market rates.

Greenfield Projects

New builds with technology stack decisions (web, mobile, API, SaaS, etc.).

Technical Due Diligence

M&A, vendor selection, feasibility studies for CTOs/investors.

πŸ“Š Validation Status (Honest Disclosure):

Current Status: Internal test suite pass rate 85-95% (comprehensive automated testing).

What's NOT Validated: Timeline predictions against real project outcomes. We don't have "500 projects analyzed" or "84.6% accuracy" β€” that would require retrospective validation with actual client data.

Validation Roadmap:

  • β€’ Q1 2025 (Now): Launch with honest messaging, collect early adopters
  • β€’ Q2 2025: Follow up with early adopters, validate predictions vs reality
  • β€’ Q3 2025: Comparative analysis (PROTHEUS vs architects, multiple projects)
  • β€’ Q4 2025: Publish validated accuracy report with completed projects

We're being honest: PROTHEUS is a decision support tool with strong architectural logic, but NOT yet validated with extensive real projects. We'll earn that claim in 2025.

Ready to Analyze Your Project?

3 free analyses per month. No credit card required. See exactly how PROTHEUS thinks.

Start Your Free Analysis β†’

Full transparency β€’ Multi-agent pipeline β€’ Architectural validation β€’ Strategic LLM use