The first contact with Prymetheus is a free Systems Fit Conversation. Its purpose is narrow: understand the stated business problem, current operating context, consequence, readiness, and whether Prymetheus is likely to create sufficient value.
It is not a free diagnosis, architecture session, implementation scope, or disguised closing call. The responsible outcome may be to proceed, wait, make a smaller change, keep the current system, or use another provider.
When deeper analysis is justified
The next step is a paid Business Systems Diagnosis. It maps how work, knowledge, data, decisions, people, authority, and technology actually operate. It separates evidence from interpretation and identifies the structural constraint beneath the visible symptoms.
The written diagnosis evaluates what should be kept, connected, replaced, protected, simplified, automated, or built. It also records ownership, security, dependency, maintenance, capacity, and readiness considerations.
The diagnosis is useful without a build
The diagnosis is a decision asset, not a sales pretext. It must remain useful if Prymetheus implements the recommendation, another provider does, the business waits, or the conclusion is that no new technology should be introduced.
Implementation is proposed, scoped, priced, and approved separately. The diagnosis does not silently become permission to build.
When implementation is justified
Prymetheus designs the future system before implementation begins. The design covers workflows, knowledge, data, responsibilities, authority, technology, ownership, safeguards, failure states, operating responsibility, and measures of success.
Implementation may include process change, documentation, automation, applications, integrations, data infrastructure, deployment, and AI with a defined responsibility. The objective is the smallest complete system that responsibly produces the required outcome.
What is never promised
Prymetheus does not guarantee revenue, time savings, adoption, market response, or other outcomes it cannot control. It commits only to defined work and standards within its control, with acceptance criteria, responsibilities, assumptions, dependencies, and limitations made explicit.
Continuing support is optional and exists only under an explicit agreement where monitoring, maintenance, support, evaluation, governance, or improvement creates continuing value.
The sequence protects both parties
Fit qualifies the need. Diagnosis supports the decision. Design defines the future system. Implementation makes the design operational. Measurement and improvement determine whether it is producing the intended result.