I turn unclear requests into buildable decisions

I define system requirements so teams can build, test, and validate them without guessing. That means clear scope, zero fluff, and full traceability for dev and QA.

• Product Requirements Documents
• Software Requirements Specifications
• User stories and acceptance criteria
• Non-functional requirements
• Out-of-scope statements

Relevant project Nufacturing - 12-section PRD Liviti - website and funnel PRD CloudCore - 40-requirement SRS

I investigate how a business works today, combining stakeholder interviews, system audits, and hard data to translate vague operational pains into clear, prioritized opportunities.

• Recorded elicitation sessions
• UX and IT audit reports
• Competitor benchmarking
• Information architecture reviews
• Dataset analysis

Relevant project Altronics - 26-finding audit SELISE - 13-page research document Pharmagility - scope and research

I turn feature wishlists into structured actors, system states, and business rules. By mapping who can do what early on, I surface hidden scope disputes when they are still cheap and easy to solve.

• Actor and role models
• End-to-end user and approval flows
• Business rules written into the flow
• State models and notification matrices
• Interface screens and IA

Relevant project TicketAse - four actors, four ticket states Hydrogen EU - 12+ module screens Authente Bangladesh - storefront and funnel

I define what working means, then check it repeatedly and write down what actually happened. Defects described in the system own words are more useful to a developer than a pass or fail column.

• Regression test logs with evidence per row
• Defect notes with reproduction detail
• CRM and integration traceability
• Page and form inventories
• Rubric-based output evaluation

Relevant project Multi-brand lead-capture QA - 139 page checks Project Phoenix - LLM output evaluation

I classify controls before judging them, and price exposure so a finding can be acted on. A risk a manager cannot cost is a risk a manager cannot fund.

• Control classification by type
• Asset registers and exposure tables
• SLE and ALE calculations
• Risk registers
• Governance and assurance notes

Relevant project Building 410 - AUD 48,740 priced by exposure Value maps - governance and controls Nufacturing - risk section

I connect delivery activity to the operational details that usually disappear between design, build and launch: who owns it, what state it is in, and where the exception is recorded.

• Phased delivery plans
• Page-level migration schedules with owners
• WBS, critical path and risk registers
• Handover and onboarding documentation
• Status and exception tracking

Relevant project Kartra to GoHighLevel - 20 pages, 4 owners Nufacturing - 16-week phased plan RTW - LMS project plan