Complimentary Enquiry Audit
Take one request your catalogue could not answer, and see what was actually missing.
Use the worked locker example, paste a redacted enquiry or describe a request your company receives regularly. You will see the preliminary result before you are asked for anything.
No account or email is required before the preliminary result.
- Provide one enquiry
- Preliminary analysis
- Two questions
- Draft Structured Opportunity
- Founder review
What the preliminary result contains
A document you can read, argue with and take to a colleague.
- Potential Catalogue Blind Spot
- Customer-supplied requirements
- Draft Structured Opportunity
- Missing information
- One or two next useful questions
- Possibly acceptable alternatives
- Likely capability path
- One applicable constraint or authority limitation
- Preliminary decision state
- Preliminary fit indication
What this preliminary audit does not produce.
- It is not a price, cost estimate or quotation.
- It is not a technical approval or feasibility confirmation.
- It is not a delivery commitment or lead-time confirmation.
- It is not a manufacturing instruction.
- It is not a final Decision Record.
Generated interpretation is labelled as generated throughout. Where the request asks for something no one has yet approved, the audit says so rather than filling the gap.
Once your rules are in it
The audit stops short of a price because your business has not set one.
Nothing above is a permanent limitation of the platform. Once a business defines and approves its own price logic, lead-time rules, capacity constraints and technical approval thresholds, Specify applies them and can return an indicative estimate, a lead time or a quotation under those approved rules.
- Price logic your commercial owner defines and approves.
- Lead times derived from your capacity and production rules.
- Technical thresholds that decide what needs review and what does not.
- Quotations assembled from rules the business already stands behind.
The distinction is authorship. Specify never invents commercial logic. It applies the logic your business owns, and it will not produce an answer that no approved rule supports.
Why it is complimentary
We are learning where the Capability Gap is commercially significant.
Specify is reviewing early demand patterns to learn where Premature No events and Capability Gaps matter most. Each reviewed request tests the core demand-driven commerce model: intent, capability, constraints, decision and learning.
After the audit
If one enquiry is not enough evidence, the next step examines a pattern.
A Request Readiness Sprint takes a representative set of your real customer enquiries, models the relevant capability and constraints, and produces a Pilot Decision Brief recommending expand, revise or stop.