SyncOnAI360

Roadmap

Where SyncOnAI 360 is going, stated without dates we cannot keep.

What has shipped, what we are working on now and what comes later. Direction, not a contract: we publish order and intent, and the changelog records what actually lands.

See the changelogTalk to us

Service Transformation

Projects · Board · Sprint 7

To do 2

Remove 14 unused Case fields

From audit

Consolidate Account triggers

Apex

In progress 1

Fault paths on intake Flows

From audit

In review 1

APAC routing for Service

Flow

Done 1

Retire Process Builder on Lead

Release 24.3

Work items link to the proposals and deploys that delivered them

In one paragraph

The SyncOnAI 360 roadmap lists recently shipped capabilities and the direction of upcoming work in three horizons: now, next and later. It carries no dates, because a date we miss is worse than none. Anything listed here as upcoming is not available today, and the changelog is the record of what has shipped.

Horizons: now, next, later
3Horizons: now, next, later
Promised dates
0Promised dates
Record of what shipped: the changelog
1Record of what shipped: the changelog
Upcoming item marked as not yet available
EveryUpcoming item marked as not yet available

01The problem

Why most product roadmaps are hard to trust

Roadmaps tend to promise dates that slip and features that quietly disappear, and buyers end up planning around things that never arrive.

  1. 01

    Dates that slip

    A quarter promised becomes a year delivered.

  2. 02

    Upcoming sold as shipped

    Sales conversations blur what exists and what is planned.

  3. 03

    Silent removals

    Items vanish from the roadmap without explanation.

  4. 04

    No record

    Nothing ties the roadmap to what actually landed.

02shipped

What has SyncOnAI 360 shipped recently?

Named pre-flight checks with blast radius and an overall risk on every proposal. A priced audit with a letter grade, severity and effort, and verified fixes after re-audit. Findings to a priced statement of work in one step. A deploy policy with freeze windows, required approvers and auto-approval that can never override a failed check.

Visual builders for Flows, Lightning pages, Lightning Web Components and Apex. Specialist agents with tool permissions and approved memory. A verified prompt library. A read-only MCP server for Claude, Cursor and other clients. The Trust Center, security overview, subprocessors list and data processing addendum, and secrets held in a cloud key management service.

  • Pre-flight checks and deploy policy
  • Priced audit and audit to SOW
  • Four visual builders
  • Agents, prompts and MCP

Proposal: Case intake fault handling

Acme Production

Checks passed
  • Validated against the org without changing it
  • No component outside the change is modified
  • Apex tests pass, coverage 81%
  • No freeze window in effect
  • Policy: production requires a second admin

Blast radius

  • 2 Flows read Case.Priority
  • 1 report filters on it
  • Case_Intake_Route assigns from it

Risk: medium

03now

What are we working on now?

Enterprise readiness: single sign-on for enterprise customers and the start of independent security certification. More of the governance model in the product itself, with per-org controls over what AI may do.

None of this is available today. The Trust Center states each control as it stands, and will change when these ship.

  • Single sign-on for enterprise
  • Security certification
  • Per-org AI controls
  • Not available today

Workspace security

Settings · Security

  • Configuration onlyMetadata and code. CRM records stay in Salesforce.
  • Isolated per customerEnforced by the database and tested every release.
  • Keys in Google Cloud KMSCredentials encrypted under a per-customer key.
  • Second admin for productionThe author can never approve their own change.
  • Hosted in the United StatesEvery subprocessor listed with its region.

04next

What comes next?

Monitoring that watches for drift between orgs, such as a sandbox diverging from production on a key object, with notifications. A richer Slack presence beyond deploy results. Quality scoring on generated changes, and saved recipes that turn a good run into a reusable starting point.

These are direction, not commitments, and are not available today.

  • Drift monitoring between orgs
  • More from Slack
  • Quality scoring and recipes
  • Not available today

Acme Production

Org health · synced 4 minutes ago

82

Health · B

Health

82

Confidence

74

Coverage

91

Apex coverage 78%, from the org's last test run

  • 3 Flows on Case run on the same trigger
  • 11 Apex classes below 75% coverage
  • Managed package source hidden by Salesforce: 2 packages

05later

What is further out?

Portfolio insight for consultancies: spotting where a solution built for one client fits another, and opt-in anonymised benchmarks. Provisioning of users from an identity provider, a data residency option outside the United States, and wider coverage of Salesforce clouds such as Marketing Cloud and Data Cloud.

These are direction, not commitments, and are not available today.

  • Portfolio insight
  • User provisioning
  • Regional data residency
  • Wider cloud coverage

Command Center

Org portfolio

5

Connected orgs

78

Average health

3

Need attention

  • Global Sales · ProductionProd

    12 open findings · Deploy approved 2h ago

    86

  • Service EMEA · ProductionProd

    31 open findings · Change made outside pipeline

    71

  • Partner Portal · ProductionProd

    18 open findings · Audit finished 20m ago

    79

  • Global Sales · UATSandbox

    14 open findings · Proposal validated

    84

  • Service EMEA · DevSandbox

    36 open findings · Sync running

    68

06principles

What will not change?

Nothing reaches a customer org except through a proposal that is checked and validated. Salesforce stays the authority, and CRM records are not stored. Every plan includes every feature. Missing data is reported as missing, never as zero.

Whatever ships, it ships inside those rules.

  • Proposals for every change
  • Salesforce stays the authority
  • Every feature on every plan

Proposal: Case intake fault handling

Acme Production

Checks passed
  • Validated against the org without changing it
  • No component outside the change is modified
  • Apex tests pass, coverage 81%
  • No freeze window in effect
  • Policy: production requires a second admin

Blast radius

  • 2 Flows read Case.Priority
  • 1 report filters on it
  • Case_Intake_Route assigns from it

Risk: medium

07influence

How do customers shape the roadmap?

Requests that come with a real org behind them carry the most weight: a check the audit should run, a metadata type the builders should edit, a control a security review asked for. Tell us through the contact form what you need and why, and what it would let you do.

We would rather build one thing customers use every week than five that look good on a slide, so the order changes when the evidence does.

  • Requests with real use behind them
  • Security review asks
  • Order follows evidence

SyncOnAI 360

AI architect for Salesforce

Ask SyncOnAI to build flows, rules, Apex, or SOQL...

08How it works

How the roadmap is kept

Order and intent here, facts in the changelog.

  1. 01

    Listen

    Customer requests and evidence from real orgs shape the order.

  2. 02

    Publish

    Direction is listed here without dates.

  3. 03

    Ship

    What lands is recorded in the changelog.

  4. 04

    Update

    Shipped items move to the shipped list.

09Before and after

A roadmap, promised versus published

Without

With SyncOnAI 360

Dates that slip

Order and intent, no dates

Upcoming sold as shipped

Every upcoming item marked as not available

Silent removals

Shipped work recorded in the changelog

Rules that bend for features

Principles that do not change

10Questions

Frequently asked questions

It is being worked on now. We do not publish dates; the changelog will record it when it ships.

Not yet. Certification work is on the roadmap, and the security overview states each control as it stands.

Yes. Tell us through the contact form; requests backed by real use shape the order.

No. Only shipped items are available; everything under now, next and later is upcoming.

A regional residency option is on the later horizon. Today the application and database run in the United States.

A richer Slack presence is on the next horizon. Today Slack receives deploy results only.

Every plan includes every feature, and we intend to keep it that way.

In the changelog.

Coverage grows over time; the supported metadata page lists what is read, built and deployed today.

If something is retired, the changelog will say so rather than letting it quietly disappear.

Not on the current roadmap. Today it raises audit findings as Jira Cloud issues and checks their status on demand.

11Keep exploring

Related

ChangelogWhat shipped, and whenTrust CenterWhat we hold and how it is protectedEnterprise Salesforce teamsGovern every org and every change at scaleWhy SyncOnAI 360What makes it different, and what it is notPlatformUnderstand, build, ship and deliver in one workspaceContactTalk to our team

Start in 5 minutes. No card required.

Connect your Salesforce org. Run your first health scan. Ask your first question. See what you've been missing.

Start free, connect my orgBook a demo with SyncOnAI
  • Anthropic
  • OpenAI