# How to deliver Salesforce client work, and prove it was delivered. > Delivering client work with SyncOnAI 360 means planning on a project board beside the client's org, building changes with the AI, agents and visual builders, shipping them as validated, approved proposals with receipts, linking work items to deploys, and proving the outcome with re-audits shared as read-only reports. Source: https://synconai360.com/use-cases/client-delivery ## Key facts - **Every**: Work item linkable to its deploy - **Every**: Change validated before approval - **Verified**: Fixes confirmed by re-audit - **0**: Accounts the client needs to see results ## Why client delivery is hard to prove At the end of a phase the client asks what they got. The answer is a list of closed tickets, which says nothing about what reached the org or whether it worked. - **Tickets, not outcomes.** Closed cards are not proof of delivered change. - **Context switching.** Plans, orgs and evidence live in different tools. - **Risky changes.** Fast delivery without checks breaks client orgs. - **Reports by hand.** Every steering meeting needs a fresh deck. ## How do you plan client delivery beside the org? Projects have a board, backlog, sprints, roadmap, releases, a wiki and reports, in the same workspace as the client's org. Audit findings become work items with their evidence and estimate in one step. - Board, sprints and releases - Beside the client's org - Findings as work items ## How does the team build faster? The AI and specialist agents draft changes against the client's real org, and visual builders for Flows, Lightning pages, components and Apex explain before they edit. Org rules keep each client's conventions. - AI that knows the client's org - Visual builders - Client conventions kept ## How is client work shipped safely? Every change is a proposal with named checks, blast radius and validation against the org; production needs a second admin's approval, which can be the client's own admin. Every deploy leaves a receipt with rollback. - Checks and validation - Client admin can approve - Receipts and rollback ## How do you prove delivery to the client? Work items link to the deploys that delivered them. Run the audit again and fixed findings are marked verified fixed; share the updated report as a read-only link. Reports show delivery, deploys and health, with coverage stated. - Work linked to deploys - Verified fixes - Read-only reports ## How do you hand over at the end? Runbooks, decisions and meeting transcripts are pages beside the org, the change history and receipts record every change, and the client's org stays synced and explained for whoever comes next. - Runbooks as pages - History and receipts - An explained org ## How do you report progress to the client each week? Read delivery, deploys and org health from reports on one engine, with every widget stating its coverage, and share the latest health or audit as a read-only link. Fixed findings show as verified fixed, so progress is measured against the same checks each time. Steering meetings start from the record rather than from a deck someone built the night before. - Reports with coverage stated - Verified fixes - Links instead of decks ## How to deliver client work 1. **Plan.** Findings and requirements onto the board. 2. **Build.** AI, agents and builders against the real org. 3. **Ship.** Validated, approved proposals. 4. **Prove.** Re-audit and share the report. 5. **Hand over.** Pages, history and receipts. ## Client delivery, claimed versus proven | Without | With SyncOnAI 360 | |---|---| | A list of closed tickets | Work items linked to deploys | | Plans and org in different tools | One workspace | | Fast but risky changes | Checked, approved, reversible changes | | A deck per steering meeting | Reports and re-audits on demand | ## Delivery checklist - [ ] Put findings and requirements on the project board. - [ ] Set the client's conventions as org rules. - [ ] Invite the client's admin to approve production changes. - [ ] Build against the real org with the AI, agents and builders. - [ ] Ship every change through a proposal. - [ ] Link work items to the deploys that delivered them. - [ ] Re-audit and share results at each milestone. ## Who delivers client work - **Consultancies.** Deliver with one method and prove it. - **Delivery managers.** Report from what shipped. - **Independent consultants.** Look like a much larger team. ## Frequently asked questions ### Can the client approve production changes? Yes, if their admin is an admin in the workspace; production needs approval from someone other than the author. ### Can the client see progress? Yes, through read-only health and audit reports. ### Are work items linked to deploys? Yes, to the proposals and deploys that delivered them. ### Can findings become work items? Yes, in one step, with evidence and estimate. ### Can we keep each client's conventions? Yes, with org rules per org. ### What happens at handover? Pages, history and receipts stay with the org in the workspace. ### Can delivery link to Jira? Audit findings can be raised as Jira Cloud issues; it is not a two-way sync. ### Is this on every plan? Yes. Every plan includes every feature. ### Can deploy results go to the client's Slack? A workspace posts deploy results to one Slack channel through a webhook you create. ### Can the client see the board? Projects are inside the workspace; share health and audit reports externally. ### Can the team work on several clients at once? Yes. Each client org has its own rules, projects and reports in the workspace. ### What if a delivered change misbehaves? Roll it back from the receipt while the fix is prepared. ### Can delivery start before the contract is signed? That is your commercial decision; technically, work can start as soon as the client connects an org.