Define a useful first step before building the system

Alongside implementation, I worked on early-stage conversations where the problem, useful first scope and evidence of success still needed to be defined. These were separate discovery and proposal workstreams, rather than one launched product.

For a business managing seasonal freelance staffing, I documented needs around approvals, attendance and payroll and outlined an AI-readiness assessment. The work included identifying data-access boundaries and questions about the priority workflow, ownership and success measures.

The outcome was a clearer assessment scope. A purchase or delivery engagement had not been agreed in the recorded work.

I prepared bilingual stakeholder decks for a junior-secondary algebra MVP, including competitor comparison, delivery planning and adjustable cash scenarios. The English proposal was shared for a stakeholder meeting.

The delivery estimates and financial scenarios were planning assumptions. Scope agreement, teacher/user interviews and student trials were still validation work ahead.

In a separate client-facing workstream, I designed, developed and presented a contract-lifecycle business-development concept, adapting the presentation in response to live feedback. The record supports solution shaping and presentation work, with acceptance and commercial outcomes unestablished.