The first version is centered around the core workflow: deliverable →
feedback → revision → approval → record.
Deliverables
A project broken into clear units of work
Each deliverable has its own title, description, status,
ownership, discussion, attachments, and lifecycle.
Status flow
Simple stages that keep work easy to follow
Example statuses include proposed, in progress, in review, changes
requested, and completed.
Requests
Structured requests instead of scattered messages
New asks can be captured more clearly so they are visible,
tracked, and easier to evaluate.
Revisions
Feedback connected to the correct deliverable
Revision cycles stay tied to the work item they belong to, which
helps both sides keep context.
Approvals
Clear sign-off with visible history
Deliverables can be submitted for review and explicitly approved
or sent back for changes.
Comments
Discussion where it belongs
Comments stay attached to the project or deliverable instead of
getting lost in long chat threads.
Files
Share project files in context
Files can live at project level or be attached directly to the
relevant deliverable.
Pricing clarity
Give better visibility to estimated work cost
Deliverables or extra work can carry pricing context so cost is
clearer before work begins.
Templates
Start recurring projects faster
Reusable templates can help teams spin up common project types
with predefined deliverables.