← Back to packages

AKILTA / DISCOVERY

Paid Discovery / Technical Assessment

What do you get?

Start with the scope elements that matter most to the decision; detailed technical context stays below.

  • Evidence-backed current-state findings
  • Constraints, risks and dependency map
  • Recommended bounded next path
  • Proposal-ready scope direction where justified

Scope boundary

A package creates speed without hiding uncertainty. Included deliverables are defined in the package description; the conditions below are confirmed before a binding start.

IncludedDeliverables explicitly stated in the summary above and the detailed package description.
Not included by defaultWork not explicitly listed in this package; content/data production, additional migration or integration, ongoing ownership/care, and third-party fees or approvals unless explicitly agreed.
Confirmed separatelyAccess, third-party dependencies, content/data condition, provider constraints and acceptance boundaries.

Package contract

Deliverables, limits, customer inputs and out-of-scope work are explicit before a buying decision.

SCHEDULEStarts after the assessment question and evidence access are confirmed; depth is governed by the selected plan.
REVIEWSOne factual-clarification pass is included; a materially different assessment question is new scope.
POST-DELIVERYFindings remain a point-in-time assessment of the evidence available during the engagement.
What exactly is delivered?
  • Assessment question and evidence boundary
  • Current-state findings supported by available evidence
  • Key constraints, risks, assumptions and dependencies
  • Recommended next commercial/technical route
  • Implementation scope direction where evidence supports it
Scope limits
  • Assessment only; implementation is not included
  • Depth and system count depend on selected plan
  • No guarantee that every uncertainty can be resolved without additional access/evidence
What do we need from you?
  • Clear assessment question or business decision
  • Relevant system/document access
  • Available architecture, vendor and operational information
  • Named stakeholder for factual clarification
What is not included?
  • Implementation or production changes
  • Open-ended research
  • Legal/security certification
  • Third-party audit fees
  • Guaranteed proposal if evidence remains insufficient
What can be added later?
  • Follow-on fixed package
  • Custom software/project proposal
  • Additional Discovery scope
  • Commerce Rescue when a live incident exists
What happens after starting?

After commercial activation: choose assessment depth → evidence/access intake → investigation → findings → review → decision-ready next scope.

How does it work?

The package creates clarity; the start still confirms access, dependencies and acceptance conditions.

  1. 01Confirm fit and intended outcome
  2. 02Lock scope, access and dependencies
  3. 03Execute after onboarding
  4. 04Verify against QA and acceptance conditions
  5. 05Handoff, launch or move into the next ownership path

Decision questions

The questions most often worth clarifying before purchase or project start.

What is confirmed before starting?

We confirm the intended outcome, deliverables, access, third-party dependencies, scope boundary and acceptance conditions.

What if the scope is not clear enough?

When uncertainty affects architecture, integrations, data or risk boundaries, Discovery / Technical Assessment is used to make the next scope decision-ready.

If this package looks right, define the next step.

Check fit & start