System discovery before implementation
Map the operation, challenge assumptions, and leave with explicit decisions, dependencies, and open questions.
Illustrative terrain · not a project estimate, delivery schedule, or ROI model
Fit gate
Tusk Discovery is designed for owner-led and service businesses deciding what to change before buying software, automating work, or commissioning a custom system.
Decision terrain / interactive example
Select evidence layers to revise an illustrative build path. The result never estimates cost, timeline, feasibility, or return.
The expedition
WAYPOINT 01
Confirm one decision, one operating unit, the sponsor, evidence, access, and exit criteria.
WAYPOINT 02
Study real work, artifacts, handoffs, exceptions, ownership, tools, and data.
WAYPOINT 03
Test assumptions against edge cases, constraints, adoption, conflicts, and missing access.
WAYPOINT 04
Shape the target state, dependencies, alternatives, and factual corrections with stakeholders.
WAYPOINT 05
Deliver a Proceed, Validate, or Hold recommendation with the blueprint and 30/60/90 route.
Standard commercial scope
Payment is due before kickoff. The signed statement of work controls the final boundary, schedule, acceptance, and any separately offered implementation credit.
Blueprint contents
The blueprint reflects the stakeholders, systems, and evidence available during Discovery. Implementation readiness depends on resolving its stated dependencies and gates.
The bounded question, evidence criteria, and a Proceed, Validate, or Hold recommendation.
Workflows, actors, tools, data, and important exceptions.
Observed facts, hypotheses, contradictions, unknowns, and required validation.
Components, boundaries, ownership, and information flow.
Dependencies, decision gates, deferred work, and two or three quick-win candidates—not implementation.
What could change the plan and who validates next.
A decision readout plus PDF and agreed editable formats.
Before the expedition
No. It is the decision-and-design phase. Implementation, licensing, and support require separate scope.
One entity or operating unit, one decision and its main workflow, up to four stakeholder interviews, one observation session, up to five systems, up to ten key artifacts, and one factual-correction round.
After the agreement, payment, participants, access, and required inputs are ready. Late evidence or expanded scope may require a revised schedule or change order.
No. The pack may identify two or three candidates. Configuration, code, automation, migration, or rollout requires a separate signed scope.
No. It documents planning assumptions and dependencies, not guaranteed schedule, cost, adoption, or return.
The blueprint is designed to be portable. Readiness still depends on resolving its gates and open questions.
No. Only a signed statement of work can define whether a credit applies, its eligibility, expiration, minimum project size, and cancellation treatment.
Discovery fit review
Four short steps produce a structured fit request. They do not approve a project, estimate ROI, or create a purchase.
One bounded decision · up to 30 calendar days after required inputs are ready · signed SOW controls final scope and any later implementation credit.
STEP 1 / 4
Decision point