Phase 0 · Qualify · Template
Fit Assessment Rubric.
Pre-engagement scoring tool. Surfaces whether a prospect's workflow is a Lighthouse-shaped problem before a proposal is written. Green / Yellow / Red across eight dimensions.
Used in Qualify calls before contract. A Red score is a gentle decline, not a push.
Faithful mirror
This HTML is a read-only projection of
lighthouse-fit-assessment-rubric.xlsx. For filling in a live engagement, open the XLSX file.
§00
Workbook overview
This workbook contains 3 sheets. Each sheet below is rendered as a read-only table — for filling in a live engagement, open the XLSX version.
§01
Sheet · Fit Assessment
| UMBRA STUDIO — FIT ASSESSMENT RUBRIC | |||
|---|---|---|---|
| Lighthouse Sprint — Stage 1: Discovery — Determine workflow fit for agentic redesign | |||
| CLIENT: | [Client name] | ||
| DATE: | [YYYY-MM-DD] | ||
| SPRINT LEAD: | [Name] | ||
| Criterion | Score (1-5) | Evidence / Notes | Risk Factors |
| Workflow Repeatability | [Evidence] | [Risk] | |
| Volume/Frequency | [Evidence] | [Risk] | |
| Document-Heaviness | [Evidence] | [Risk] | |
| Current Automation Level | [Evidence] | [Risk] | |
| Decision Complexity | [Evidence] | [Risk] | |
| Data Availability | [Evidence] | [Risk] | |
| Stakeholder Buy-In | [Evidence] | [Risk] | |
| Budget Authority | [Evidence] | [Risk] | |
| Timeline Flexibility | [Evidence] | [Risk] | |
| Compliance Sensitivity | [Evidence] | [Risk] | |
| Technical Infrastructure | [Evidence] | [Risk] | |
| Change Readiness | [Evidence] | [Risk] | |
| TOTAL SCORE: | 0 | ||
| SCORE INTERPRETATION: | |||
| 48+ = Strong Fit — Proceed with confidence | |||
| 36-47 = Moderate Fit — Proceed with caveats and risk mitigation | |||
| <36 = Not Recommended — Revisit workflow selection or constraints |
§02
Sheet · Scoring Guide
| FIT ASSESSMENT RUBRIC — DETAILED SCORING GUIDE | ||
|---|---|---|
| Criterion | Score | Description & Guidance |
| Workflow Repeatability | 5 | Same sequence every time, no exceptions; highly standardized |
| 3 | Generally repeatable with common exceptions (< 10% variance) | |
| 1 | Highly variable; each execution is different; many exceptions | |
| Volume/Frequency | 5 | High volume (100+ per week or continuous); every day |
| 3 | Moderate volume (10-100/week); 2-3 times daily | |
| 1 | Low volume (<10/week); ad-hoc or monthly | |
| Document-Heaviness | 5 | Heavy documents (contracts, briefs, regulatory); >50% of cycle time |
| 3 | Moderate docs (templates, reports); 20-50% of cycle time | |
| 1 | Light docs; mostly system-based data | |
| Current Automation | 5 | Fully manual, no automation today |
| 3 | Partially automated (50%); mixed manual/system | |
| 1 | Mostly automated; limited manual work | |
| Decision Complexity | 5 | Rule-based decisions; clear criteria; binary or categorical outcomes |
| 3 | Mixed: some rules, some judgment; 70% rule-based | |
| 1 | Highly subjective; requires deep expertise and judgment | |
| Data Availability | 5 | All data available in accessible systems; structured |
| 3 | Most data available; some manual entry or external sources | |
| 1 | Data scattered; not all accessible; poor quality | |
| Stakeholder Buy-In | 5 | High pain, strong desire to change; leadership committed |
| 3 | Moderate pain; stakeholders open to change but cautious | |
| 1 | Low urgency; resistance or skepticism | |
| Budget Authority | 5 | Budget approved; clear ownership; no delays expected |
| 3 | Budget likely; minor approvals needed | |
| 1 | Budget uncertain; requires multiple sign-offs | |
| Timeline Flexibility | 5 | Flexible; can extend without business impact |
| 3 | Some flexibility; soft deadline; can adjust scope | |
| 1 | Hard deadline; zero flexibility; scope locked | |
| Compliance Sensitivity | 5 | No compliance requirements; all decisions can be made by agent |
| 3 | Some compliance; can audit and log agent decisions | |
| 1 | Highly regulated; every decision must be reviewed/approved | |
| Technical Infrastructure | 5 | Modern stack; APIs available; good data quality |
| 3 | Functional systems; some legacy; most APIs available | |
| 1 | Legacy systems; limited API access; poor integration | |
| Change Readiness | 5 | Team excited; low resistance; high adoption likelihood |
| 3 | Team neutral; some training needed; moderate adoption | |
| 1 | Team resistant; high training burden; adoption risk |
§03
Sheet · Summary
| FIT ASSESSMENT SUMMARY | |
|---|---|
| Link to Fit Assessment Tab | |
| Refer to the 'Fit Assessment' tab to complete scoring. | |
| RECOMMENDATION LOGIC | |
| Total Score | Recommendation |
| 48+ | Strong Fit — Proceed with confidence. Risk profile is low. |
| 36-47 | Moderate Fit — Proceed with caveats. Identify key risks and mitigation. |
| <36 | Not Recommended — Revisit workflow scope or constraint assumptions. |