01
Diagnostic Working Session
We map how the business actually operates using recent, specific evidence: workflows, knowledge, data, decisions, people, tools, constraints, risks, and desired outcomes.
Business Systems Diagnosis
Find the real constraint.Before you pay to build the wrong solution.
A paid diagnostic engagement for established founder-led and small-team businesses. We map how work, knowledge, data, decisions, people, and technology actually operate; identify the structural constraint; and recommend what should be kept, connected, replaced, protected, simplified, or built.
The diagnosis remains useful whether Prymetheus implements the recommendation, another provider does, or the right decision is not to build.
Section 01 · How it works
Three disciplined steps. One decision asset.
The engagement separates evidence gathering, analysis, and decision review. Each step has one job: understand the current system, identify the governing constraint, and support a responsible decision.
02
Written Diagnosis
The evidence is analyzed into a decision asset that separates observation from interpretation, identifies the structural constraint, and explains the strongest available options.
03
Decision Review
We examine the evidence, recommendation, tradeoffs, risks, readiness, and unresolved questions. Implementation is scoped separately only when the diagnosis justifies it.
The working session gathers evidence before conclusions are drawn. Initial assumptions may be tested during the session, but the written recommendation is not finalized until the available evidence, contradictions, risks, and unknowns have been reviewed.
Section 02 · The human glue
What we are looking for.
Most founders can't see it clearly because they're inside it. The business looks organized, but underneath, you are manually carrying context, files, decisions, and workflow logic between disconnected tools. You are the integration layer. The diagnosis surfaces that pattern specifically: which steps, knowledge, decisions, tools, and moments, without assuming that every manual responsibility should be automated.
The manual bridge
You copy the same information from one tool into another, for every client, every time. The transfer happens because nothing connects.
The disconnected tools
You pay for tools that don't talk to each other. You're the one connecting them, every single time a handoff needs to happen.
The founder-dependent decision
Work only moves when you're there to decide, approve, or check something. Nothing is authorized to proceed without you.
The re-explained AI
You use ChatGPT or Claude, but you start from scratch every session. Your business context never carries over.
The scattered file
Files, notes, context, and instructions live in tools, inboxes, and memory, spread across enough places that finding anything takes longer than doing it.
The repeated step
The same thing happens for every client, every project, every week. It still runs on you because it has never been built to run without you.
Section 03 · The deliverable
What the diagnosis covers.
The written diagnosis is designed to stand on its own. It records evidence, interpretation, assumptions, limitations, tradeoffs, and the recommended next step. It is a decision asset, not a disguised implementation proposal.
The written diagnosis covers
- The current business system: people, work, knowledge, data, decisions, and technology
- The structural constraint beneath the visible symptoms
- What is working and should be preserved
- What should be kept, connected, replaced, protected, simplified, or built
- Ownership, authority, dependency, security, maintenance, and readiness considerations
- A recommended sequence with evidence, assumptions, risks, and unresolved questions
The diagnosis separates "what the data shows" from "what it likely means." Where the evidence is thin or uncertain, that is labeled clearly. The goal is a real picture, not a polished version of what you want to hear.
Section 04 · Fit
Built for a specific founder.
The diagnosis works best when there is a real working business to look at, real clients, real revenue, real repeated friction. If most of these are true, the fit is likely strong.
Strong fit: this is for you if
- You run a real service business, real clients, real revenue, real repeated workflows
- Operational complexity has outgrown the way the business currently works
- Important knowledge, decisions, or handoffs depend on particular people
- Current tools, data, and workflows do not operate as one reliable system
- You are prepared to provide evidence and participate in the diagnosis
- You want the strongest recommendation, even when it is not a custom build
Not a fit: this is not for you if
- Still building the businessIf there are no real clients yet and no repeated operations, there is little evidence to diagnose. The engagement creates the most value when there is a working business to examine.
- Seeking a predetermined buildIf the decision to buy a particular app, automation, or AI agent has already been made and cannot be questioned, this is not an independent diagnosis.
- Looking for a free strategy reportThe fit conversation is free. The diagnosis and written decision asset are paid professional work.
- Expecting results with no founder involvementBuilding anything meaningful requires your context and your participation. If the goal is automation with no input, this is not what gets built here.
- Enterprises or larger teamsPrymetheus serves owner-operated and small-team businesses. Very large organizations with established internal engineering teams are usually a different kind of engagement.
Section 05 · Questions
Common questions.
Is the Business Systems Diagnosis free?
No. The diagnosis is a paid professional engagement because the analysis, written decision asset, and recommendation are substantive work. A short Systems Fit Conversation is free and determines whether the diagnosis is likely to create sufficient value.
Does the diagnosis commit me to implementation?
No. The diagnosis must remain useful whether or not Prymetheus implements the recommendation. Implementation is proposed, scoped, priced, and approved separately.
What is the Decision Review?
A live session where we examine the evidence, diagnosis, tradeoffs, risks, readiness, and recommended next step together. It is also where unresolved assumptions are challenged before any implementation decision.
What if the recommendation is not to build?
Then Prymetheus says so. The right answer may be to keep the current system, simplify a workflow, improve documentation, connect existing tools, wait, or use another provider.
Do I need to be technical?
No. The diagnosis concerns how the business works. Prymetheus translates the technical implications so the responsible owner can understand the decision, its tradeoffs, and the responsibilities it creates.
How long does the diagnosis take?
Timing depends on scope, access, complexity, and the evidence required. The duration, working sessions, deliverables, assumptions, and decision date are defined before the paid engagement begins.
How is this different from a software discovery call?
A sales discovery call usually qualifies a predetermined service. The Business Systems Diagnosis is paid analysis that may recommend software, workflow change, structured knowledge, integration, protection, keeping the current system, or no new technology.
What is the 'human glue' pattern?
Human glue is the pattern where a founder or employee manually carries context, files, decisions, and workflow logic between disconnected parts of the business. The diagnosis makes the exact responsibilities and handoffs visible without assuming every manual responsibility should be automated.
The first step is a systems fit conversation.
Describe the business problem and the current operating context. The free fit conversation determines whether a paid Business Systems Diagnosis is likely to create sufficient value. Scope, deliverables, timing, and price are made clear before it begins.