# OpScore

> Agent-facing counterpart to the [human project page](/projects/opscore/).

## Record metadata

- Record: 037
- Slug: opscore
- Domain: Business
- Domain code: BUS
- Type: Product concept
- Status: Archived
- Period: 2024
- Portfolio role: Early product idea
- Publication state: Public concept record
- Case-study readiness: Concept documented
- Compendium edition: 0.4

## Summary

A concept for interviewing a business owner and turning operational context into a concrete AI implementation guide.

## Overview

Small businesses are frequently told to adopt AI before anyone has mapped the work the technology is supposed to improve. OpScore proposed starting with an interview rather than a product pitch.

An AI-led interview that maps a company's work, friction, tools, and constraints, then produces a prioritized implementation guide.

Purpose: Bridge the gap between generic AI enthusiasm and the specific workflows a small business could actually improve.

## The problem behind the project

Small-business owners often do not know which operational details matter when evaluating AI, while consultants can be expensive and generic advice is rarely actionable.

The interview would surface recurring workflows, friction, tools, constraints, and implementation capacity, then translate that context into a prioritized guide. The name suggested a score, but the more durable idea was the path from evidence to action.

Small-business owners and implementers may benefit. Employees are affected by workflow recommendations, so the process should not reduce work to surveillance or headcount.

## How it took shape

The project reached a documented concept and interview/output architecture but not a completed production system.

The project reached a documented product mechanism and output architecture, not a completed assessment platform. No universal metric, customer base, or deployment evidence exists.

Josiah originated the guided-assessment idea and explored its business and implementation model.

The product thesis is recorded; no validated scoring system, customers, or completed deployment is claimed.

## What the project means now

Its lesson is that an opaque readiness number would recreate the generic advice it was meant to fix. A credible revival would show the reasoning behind every recommendation, include affected workers, and treat security and domain knowledge as implementation requirements.

A score can create false authority, and recommendations require domain knowledge, worker input, security review, and implementation capacity.

The useful deliverable is not an abstract AI-readiness number; it is a specific, reviewable path from workflow evidence to implementation.

Revisit only as a transparent interview-and-playbook tool with no opaque universal score.

## Publication and interpretation notes

- Current classification: Archived
- Portfolio readiness: Concept documented
- Publication boundary: Public concept record

## Additional agent context

OpScore is an interesting archived idea, not an operating consultancy or validated business metric.

## Related project records

- [Forever Habits](/projects/forever-habits/llm/) — A small app experiment used to study how easy cloning has changed the economics of consumer software.
- [Criticality / IdeaGenerator](/projects/criticality-ideagenerator/llm/) — An abandoned project-idea feed whose failure led to a better question: can agents find grounded problems worth solving?

## Navigation

- [Complete project index](/projects/llm/)
- [Human version of this record](/projects/opscore/)
- [About Josiah's working method](/about/llm/)
- [Agent discovery map](/llms.txt)