Scope the constraint, what it touches, and who must make the fix hold.

For a business that can see symptoms but cannot yet tell which project deserves priority. The work surveys the buyer path and operating handoffs, identifies the primary constraint, and makes the dependencies and reasoning explicit.

• Current-state review across Signal, Access, Flow, and Force.
• Observed friction, evidence gaps, and competing explanations.
• Primary constraint, related dependencies, and repair order.
• A written recommendation and implementation scope when further work makes sense.

The free Field Friction Map is a separate, ungated self-assessment. A requested Field Diagnostic is a direct inquiry and is not represented as a free engagement.

For one dominant constraint whose surrounding dependencies are clear enough to scope. The engagement stays focused without pretending the website, message, intake path, or workflow exists in isolation.

• Positioning and proof work that gives the public system one stable commercial story.
• Website strategy and implementation built around buyer questions and usable next steps.
• Lead intake and response from a prospective customer's first contact to an accountable recorded outcome.
• Workflow automation for recurring operating paths with clear rules, ownership, exceptions, and recovery.

Review the complete service areas before deciding which surface should lead the work.

For a constraint that crosses positioning, proof, the website, inquiry handling, workflow, and measurement. An integrated engagement aligns those parts in phases so an isolated change does not preserve the same broken handoff somewhere else.

Integrated does not mean unlimited. Each phase still names its decisions, inputs, deliverables, owners, test conditions, exclusions, and release gate.

Inspect the Field Theory owned-system rebuild for implementation evidence and explicit limitations, not a client result.

1. Field Theory owns the logic in scope. Diagnosis, decisions, artifacts, implementation, tests, and handoff remain connected.
2. The client owns business judgment. A clear decision owner supplies evidence, access, context, and consolidated approvals.
3. Specialists have named roles. When a scope requires additional expertise, responsibilities and handoffs are explicit.
4. Production ownership transfers cleanly. Accounts, source, content, access, documentation, and operating records included in scope stay with the client.

• The number and condition of existing pages, offers, workflows, and systems.
• Whether positioning, copy, evidence, identity, and technical foundations already exist.
• Integration, migration, privacy, accessibility, and approval requirements.
• The number of stakeholders and availability of internal subject matter experts.
• The production accounts, providers, data, and failure states that must be tested.

Pricing and timing are provided in a written scope after these factors are understood. The scope is reviewed before an engagement begins. The site does not publish an invented fixed range or response-time promise.

Field Theory can define an observable system, implement the agreed work, test controllable behavior, document ownership, and report what the evidence shows. It cannot guarantee rankings, traffic, lead volume, conversion, revenue, savings, or another business outcome.

Client names, quotations, results, and private artifacts remain private unless documented permission and an adequate evidence record support publication.