PUZINSKI / B2B ONBOARDING APP RELEASE BRIEF
Fictional consultancy example. Not a client application or delivered result.

JOB TO COMPLETE
Give one internal coordinator a place to understand what is still needed
before handing a newly signed project to delivery.

PRIMARY USER
Internal onboarding coordinator. A client-facing portal is not assumed.

THREE PROPOSED FLOWS
1. Create an onboarding record from approved, fictional test information.
2. Review required inputs and mark outstanding items.
3. Mark readiness for delivery and identify the next owner.

ONE POSSIBLE INTEGRATION
An existing approved intake source, subject to access and API review.
The exact connection must be named in the written scope.

ACCEPTANCE CRITERIA TO AGREE
The coordinator can identify required and missing inputs.
Incomplete records do not appear complete without the agreed review.
Similar names do not merge separate client records.
The agreed role can access only its authorized information.
A failed integration is visible and can be investigated.
Optional AI summaries link to approved sources and require human review.

BEFORE BUILDING
Check whether the existing tools can support the workflow.
Agree on permissions, source of truth, retention, ownership, and running costs.
Use fictional records for demonstrations and initial testing.
Name the launch, handover, maintenance, and issue-reporting responsibilities.

LATER IDEAS / SEPARATE SCOPE
Client portal, additional roles, billing, document signing, new integrations,
migrations, mobile application, and broad analytics.

Explore scopes: https://puzinski.com/packages/
Requirements guide: https://puzinski.com/insights/internal-business-app-requirements/