Working pieces / assembled per project
A large technology list can hide an unclear outcome. The workshop uses complete operating pieces, each with a user, owner, exception path, evidence, and handoff.
Observe the current task, map informal handoffs, locate duplicate records, identify missing authority, and turn assumptions into decisions. Useful when the organisation knows the pain but not the system boundary.
Leaves: journey map + decision wallRebuild navigation, content, search foundations, contact paths, accessibility, performance, analytics boundaries, publishing ownership, and Spanish review around a visitor's real question.
Leaves: usable public path + content operationConnect requests, CRM records, approvals, documents, notifications, providers, fulfilment, and reporting with safe retries, visible queues, permissions, and a clear system of record.
Leaves: traceable task + operator controlsAdd retrieval, classification, research, or drafting support with bounded source access, bilingual review where relevant, evaluation fixtures, human approval, and a non-AI fallback.
Leaves: evaluated assistance + review routeProtect the current environment, reproduce the important failure, fix the narrowest unsafe boundary, improve visibility, verify production, and document deployment plus rollback.
Leaves: controlled release + return pathExamples describe possible work, not projects already completed in Uruguay.
Faith Forge Labs does not invent local customers, usage, results, demand, credentials, or offices. The actual scope is based on authorised inspection and evidence from the organisation.
Pin the current workflow and let the first session test whether the piece fits.