Define the next decision before you commit to a build.

What to bring

• The business problem, affected users, current process, and the outcome you want to evaluate.
• System names and versions, available documentation, known constraints, and anonymized examples of normal work and exceptions.
• A business owner who can review priorities and a technical owner who can confirm system access and dependencies.
• Any budget boundaries, target dates, procurement requirements, and how you would judge an acceptable result.

A short summary is enough for an initial enquiry. Share sensitive records or credentials only through an agreed secure process after access and confidentiality arrangements are in place.

Outputs to agree and review together

Depending on the question and evidence available, the assessment scope can include:

• A current workflow or data-flow map with ownership and exception handling.
• A comparison of options, including improving an existing system, using a packaged tool, or building a defined change.
• A record of findings, assumptions, unresolved questions, dependencies, and proposed next checks.
• A proposed implementation boundary, acceptance criteria, and an estimate with its assumptions and exclusions.

The agreed business and technical reviewers check these outputs against the assessment scope. Unknowns stay explicit; a limited experiment may need a separate scope before a reliable implementation estimate is possible.

Dependencies that affect the assessment

Useful findings depend on representative information, reviewer availability, access permissions, and cooperation from system or third-party owners. Sandbox access, API availability, licensing, data quality, and security requirements can change what can be checked. We agree who owns each dependency and revisit scope when an assumption changes.

What is outside the initial assessment

Production changes, a complete application build, data migration, penetration testing, compliance certification, and ongoing support are outside this outline unless separately scoped and agreed. An initial enquiry does not include an open-ended consulting engagement or a promise of free assessment work.

Estimate, review, and decide

1. Agree the assessment. Confirm the question, inputs, outputs, reviewers, exclusions, fees, and timing before beginning.
2. Review the evidence. Check findings against the agreed scope, identify corrections or missing information, and decide whether the assessment outputs meet the agreed acceptance criteria.
3. Choose the next step. Proceed to an implementation proposal, investigate a named dependency, narrow the scope, or stop. Completing an assessment does not commit you to a build.

Any implementation proposal needs its own agreed scope, commercial terms, responsibilities, schedule, and acceptance process. Estimates reflect the evidence available and may change when requirements or dependencies change.

Choose a starting point

• API and business-system integration — scope data ownership, interfaces, and recovery.
• AI application development — define evaluation and human review.
• Custom software development — assess workflows, existing systems, and build options.

Use the planning resources to organize your questions, or review our public company records.