What I can take off your plate

I sit with the business, the analysts and the people who do the work, and find where time and money are being lost. Output: a problem statement and a ranked list of pain points everyone agrees on.

Karya started from a documented study of where employees wait on a busy human; Vaasova from the way landlords run rentals over chat and spreadsheets.

Business requirements, product requirements, scope by phase, personas, user journeys, and user stories with acceptance criteria. Every requirement gets an ID so nothing is lost between the document and the build.

133 catalogued requirements for Karya; 64 features and user stories for Vaasova.

Solution architecture, data model, integration design, security and sharing model, and a written record of each decision with the alternative that was rejected and why.

Solution design specifications on the South Australian government programme, used by integration engineers, testers and the client; 12 architecture decision records for Karya.

Apex, Lightning Web Components, Flow, REST services, Platform Events, custom metadata frameworks, Agentforce agents and prompt templates, Data Cloud ingestion. Bulk-safe and written to pass static analysis.

Unit tests with real assertions, tests that run as restricted users, prompt regression fixtures for AI features, and ownership of user acceptance testing with the client.

Owned UAT onsite in Sydney through to a low-defect launch.

Source control, pull requests, quality gates and deployments through Azure DevOps, Gearset and the Salesforce CLI.

Handover documents, training content and mentoring, so the team that inherits the system can run it.

20+ developers mentored, 80+ hours of training content.