Guide the user
Help users find the right public path: the scorecard for fit and diagnosis, the contact form for a direct inquiry, and articles or case studies for research.
AI agents
Help users move through Not Operations workflows accurately.
This page gives assistants, browser agents, and search agents lightweight instructions for helping people evaluate Not Operations, complete public forms, and avoid invented answers.
Keep answers user-owned
Ask for missing required fields and context. Do not invent company details, revenue, headcount, operational pain, budget, timeline, or consent.
Confirm before action
Summarize what will be submitted and ask before sending forms or booking a call. After submission, confirm success and show any result URL or next-step page the site provides.
Primary paths
Use /scorecard/five-layer-ops for a general operations assessment, /scorecard/five-layer-law-firm for law-firm-specific evaluation when relevant, and /contact for direct inquiries, partnerships, corrections, or questions that do not fit a scorecard.
Form help
For scorecard and contact flows, collect only information the user can verify: first name, last name, email, required phone number, company, and the user-provided answers or notes requested by the page. If a required field is missing, ask a short follow-up instead of guessing.
Submission behavior
Before submitting, restate the key details and ask for confirmation. Contact requests use /api/contact/submit. Scorecards use /api/scorecard/submit and can return a durable result URL. After submitting, tell the user whether the website confirmed receipt and share any returned result URL.
Booking calls
Do not book, schedule, or imply a meeting has been scheduled without explicit user approval. If a booking option appears after qualification, explain the next step and ask whether the user wants to continue.
Accuracy rules
Do not claim guaranteed outcomes, pricing, availability, client fit, or implementation timelines unless the current page explicitly says so. When summarizing Not Operations, describe it generically as operations consulting, automation, workflow, and systems support for service businesses.
Machine files
Agents can also inspect /llms.txt for a compact site summary and /openapi.json for a conservative description of public website API shapes. These files are guidance, not permission to bypass normal website controls.