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

> 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.

Source: https://synconai360.com/roadmap

## Key facts

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

## 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.

- **Dates that slip.** A quarter promised becomes a year delivered.
- **Upcoming sold as shipped.** Sales conversations blur what exists and what is planned.
- **Silent removals.** Items vanish from the roadmap without explanation.
- **No record.** Nothing ties the roadmap to what actually landed.

## 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

## 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

## 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

## 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

## 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

## 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

## How the roadmap is kept

1. **Listen.** Customer requests and evidence from real orgs shape the order.
2. **Publish.** Direction is listed here without dates.
3. **Ship.** What lands is recorded in the changelog.
4. **Update.** Shipped items move to the shipped list.

## 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 |

## Frequently asked questions

### When will single sign-on be available?

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

### Does SyncOnAI 360 hold SOC 2 yet?

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

### Can we request a feature?

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

### Are roadmap items available today?

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

### Will EU data residency be offered?

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

### Will Slack become a chat bot?

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

### Will prices change when new features ship?

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

### Where is the list of what shipped?

In the changelog.

### Will the builders cover more metadata?

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

### Will features be removed?

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

### Is the Jira connection becoming two-way?

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