# See SyncOnAI 360 on your own org, not a demo org. > A SyncOnAI 360 demo is a working session on a sandbox of your own Salesforce org. We connect it together, read its health and audit, question it in plain language, build and validate a small change through the governed path, and answer your security, pricing and rollout questions with the evidence in front of you. Source: https://synconai360.com/demo ## Key facts - **Your**: Own sandbox, not sample data - **55**: Audit checks run live in the session - **0**: Changes made without your approval - **0**: CRM records stored ## Why most Salesforce tool demos tell you little A polished demo org always looks good. What you need to know is what the tool says about your org, with your automation, your packages and your history. - **Sample data.** A clean demo org hides how a tool copes with a real one. - **Slides first.** Half the hour goes on positioning, not the product. - **Unanswered security questions.** Security and data questions wait for a follow-up call. - **No way to check.** Claims made in the demo cannot be verified afterwards. ## What happens in a SyncOnAI 360 demo? Connect a sandbox with Salesforce OAuth at the start of the session; the sync runs in the background while we talk through your goals. By the time it finishes, the health score, the audit and the dependency graph are ready for your org. If you prefer not to connect anything live, we can walk through the product on a representative org first and you can connect your own afterwards on the Free plan. - Your sandbox, connected together - Results from your org - Or a representative org first ## What will we look at? The audit's 55 checks and the findings that matter most to you, with evidence and costs. Plain-language questions to the org about processes you know well, so you can judge the answers. A small change built and validated through the proposal path, with its named checks, blast radius and receipt. For consultancies, we also show how findings become a priced statement of work and a client deal room. - Audit findings with evidence - Questions you can check - A governed change end to end ## Which questions can be answered in the demo? Security and data handling, using the Trust Center and security overview: what is stored, where, who processes it, and what is not yet in place. Pricing by production org, with sandboxes included. Rollout: roles, approvals and freeze windows for your team. - Security and data - Pricing - Rollout and governance ## How should you prepare? Bring a sandbox you are comfortable connecting and someone who can authorise it. Think of two or three processes you know well, so you can test the answers, and one small change you would like to see shipped safely. If security review is part of your process, invite that person too. - A sandbox and its admin - Processes you know well - Your security reviewer ## What does a demo look like for a consultancy? We start from a client-style org and follow the chain a consultancy sells: the audit and its priced findings, the statement of work generated from them, the engagement with its proof and deal room, and the project board where accepted work lands. Then a change is shipped through the governed path, and the re-audit shows it as verified fixed. It is the quickest way to see whether the workflow fits how your practice wins and delivers work. - Audit to statement of work - Engagement and deal room - Delivery and verified fixes ## What does a demo look like for an enterprise team? We focus on governance: portfolio health across orgs, the deploy policy with freeze windows and required approvers, maker-checker approval for production, receipts and the activity log, and how external AI tools are scoped and logged. Bring your security reviewer: the Trust Center, subprocessors list and data processing addendum are open in the session, including what is not yet in place. - Governance first - Receipts and activity log - Security questions answered openly ## What happens after the demo? Keep using the sandbox you connected on the Free plan, or disconnect it. If you want to continue on a paid plan, paid plans open to a founding cohort first through the contact form, and enterprise customers get a rollout plan sized to their team. - Keep going on Free - Founding cohort for paid plans - Enterprise rollout plans ## How the demo runs 1. **Request.** Tell us about your team and orgs on the contact form. 2. **Connect.** Authorise a sandbox at the start of the session. 3. **Explore.** Audit, questions and a governed change. 4. **Decide.** Security, pricing and rollout, answered. ## A typical demo versus a SyncOnAI 360 session | Without | With SyncOnAI 360 | |---|---| | A polished demo org | Your own sandbox | | Slides and positioning | Mostly the product | | Security questions deferred | Answered with the Trust Center | | Claims you cannot check | Results you keep on the Free plan | ## Frequently asked questions ### Do we have to connect production? No. A sandbox is better for a demo. ### Will you change anything in our org? No. Changes only happen through proposals you approve, and the demo change can stay in the sandbox. ### Are our records copied? No. Metadata is read; CRM records are not stored. ### Can we keep the results? Yes. Continue on the Free plan, or disconnect the org afterwards. ### Can we try it without a demo? Yes. Start free and connect a sandbox yourself. ### Who should attend? Someone who can authorise a sandbox, someone who knows the org's processes, and your security reviewer if needed. ### Is there a cost? No. ### How do we book? Use the contact form and tell us about your team and orgs. ### Can we see it with our own Flows? Yes. Once your sandbox is synced, any Flow in it can be opened and explained in the builder. ### Can the demo be recorded? Yes, if you would like to share it with colleagues who could not attend. ### How long does the sandbox sync take? Several minutes for a large org, in the background, so we start talking while it runs.