The layers of a solution.
Proposed service categories for review. These examples outline the kinds of project needs that can be discussed, not confirmed offers or claims of previous work. Availability, scope, and deliverables would be agreed individually.
Software around
the actual need.
Example needs include a web application, an internal operational tool, or improvements to an existing product. Discussion can cover users, business rules, data, and the limits of the current environment.
Possible deliverables include a documented requirements outline, an application codebase, tests for agreed behavior, and setup or handover notes. The technology and acceptance criteria would follow the project rather than a fixed template.

Make the boundaries
work together.
Example needs include connecting an application to an external API, synchronizing records between systems, or replacing repetitive manual transfers. Data ownership, authentication, and error handling are important parts of the discussion.
Possible deliverables include interface mappings, integration code, validation rules, tests, and operational documentation. Dependencies on third-party systems and any limitations would be identified within the agreed scope.
A clearer view
before the next step.
Example needs include evaluating a technical approach, planning a migration, or understanding why an existing architecture has become difficult to change.
Possible deliverables include a current-state review, a comparison of options, documented risks and assumptions, and a phased technical plan. Advice would reflect the information available and does not guarantee a particular outcome.

Consider the system
beyond deployment.
Example needs include planning environments, reviewing deployment steps, managing configuration, or documenting recovery procedures. Existing access controls, dependencies, and responsibilities help define the work.
Possible deliverables include environment configuration, deployment documentation, monitoring recommendations, and a handover checklist. Any support period, availability, or response expectations would require a separate agreement.