Plan ahead · Xelence Product Roadmap 2025

What to start discussing now

Most of what's on the roadmap reaches you through an upgrade, and some of it needs work on your side too. Starting the conversation early gives you time to budget, staff and schedule it.

Which Xelence release your solution is on today, and when your next upgrade is scheduled.
Which items in Now and Next matter most to your organization.
Which of those need configuration, implementation work or a change to how your team works. Each item's detail card says which.
Who in your organization should be part of the conversation.

From a horizon to your solution

Each horizon shows when Xelence delivers a capability: Available today, Now (2026, Xelence 10.0), Next (2027, Xelence 11.0) and On the horizon (2028, Xelence 12.0, and beyond).

A capability reaches your solution when your solution moves to the Xelence release that includes it. Your upgrade is scheduled with you.

Some capabilities also need configuration, implementation work or a change to how your team works. Each capability's card says which.

A capability reaches your solution automatically only if its card says so.

Questions to discuss, by capability area

Platform & Architecture

Which hosting model, cloud or your own data center, fits your agency's policies and IT strategy?
Would you run more than one program or organization on one installation, and how must their data be kept apart?
Which custom extensions and code would need retesting each time the platform version changes?
Who in your organization approves platform, database and hosting changes in each environment?
How will you schedule platform upgrades around your busiest periods, such as year-end or payment runs?
Do your public portals need to serve constituents in more than one language?

Forms & Data Capture

Which high-volume forms cause the most re-keying, errors or incomplete submissions today?
What accessibility standards must your public-facing forms meet, and how do you test for them?
Which forms will constituents mostly complete on phones or tablets?
Where should AI help complete a form, and which answers must always come from a person?
Who owns form standards, such as layout, wording and style, across your teams?
Which forms would you modernize first as you adopt new Xelence releases?

Reporting & Analytics

Which decisions do your leaders make today without timely, reliable data?
How confident are you in the quality and agreed definitions of the data your reports use?
Who should be allowed to build and share reports, and who may see sensitive figures?
Which recurring reports are still assembled by hand outside Xelence?
Do your reports and dashboards need to work with screen readers and other assistive tools?
Which reports would you clean up or retire before your next upgrade?

Enterprise Integration

Which integrations matter most to your operations, and which would you modernize first?
Do you keep a current inventory of your interfaces and file exchanges, and who owns each one?
What does your security policy require for credentials, encryption and access between systems?
Who approves a new or changed connection to a partner system?
Which manual hand-offs between systems would you most like to automate?
How will you coordinate integration testing with partners when you take a new Xelence release?

Identity & Security

Which identity provider, such as Entra ID or Okta, should staff and constituents use to sign in?
Which of your policies, such as password, session or network rules, should Xelence enforce?
How often do you review user roles and access, and who signs off on the review?
How quickly can you remove access when staff change roles or leave?
What does your policy say about using generative AI with personal or sensitive information?
How will you fit the security changes in each release into your change and testing process?

File Processing & Batch Jobs

Which files and batch jobs are critical to your business cycle, such as contributions or payment runs?
How are bad records in inbound files handled today, and who corrects them?
Which partners exchange files with you, and which formats do they expect now and in future?
What processing windows must your batch jobs fit, and what happens when one runs late?
Where should staff sign off before automated file or batch steps take effect?
How will you plan regression testing of your critical batch jobs around an upgrade?

Business Process Management

Are your key business processes documented, and are they followed the same way across teams?
Where are your biggest backlogs, delays or missed service targets today?
Which decisions in your workflows must always stay with a person?
How will staff roles and workloads change as more routine steps are automated?
Who owns each process, and who approves changes to it before deployment?
How will you sequence process changes with Xelence upgrades and staff training?

Communication Management

How many letter and notice templates do you maintain, and which could be consolidated?
What accessibility and plain-language standards must your correspondence meet?
How will you provide translated correspondence, and who will check the translations?
Who must approve legal or policy wording before a template is used?
Which records-retention rules apply to the correspondence you generate and send?
Which existing templates would you convert or modernize first when adopting new releases?

Business Rules Management

Is your written policy kept current enough to serve as the source for your business rules?
Who in the business confirms that a rule matches policy before it is released?
How would you show an auditor or appeals officer why a rule produced a particular decision?
How do you test rule changes today, and where does your test data come from?
Do you have an approved policy for AI-assisted development, and who owns it?
How will you plan rule changes driven by new legislation alongside your upgrade schedule?

Application Performance & Monitoring

What service levels have you committed to, and how do you measure them today?
Who responds when performance drops, and how are they alerted?
Which monitoring data could contain personal information, and who should be allowed to view it?
Should Xelence monitoring feed into the operations tools your agency already uses?
How will you capture a performance baseline before an upgrade so you can compare afterwards?

Generative AI Services

Which systems and channels, such as staff screens or public portals, would call AI services first?
What data classification rules decide which information may be sent to an AI service?
Who governs AI use in your organization, and is there an approved policy or review board?
How will you budget for AI usage, and who will track it across programs?
How will people know when content came from AI, and how can they reach a person instead?
How will you retest and re-approve AI features when you take a new release or a model changes?

Xelence AI Engine

Which business problems would you prioritize for your first AI use cases?
Are the documents and data your agents would rely on accurate, current and searchable?
Who will design, build and maintain your agents, workflows and skills, and what training will they need?
At which points must a person review or approve what an agent does?
How will you decide an AI use case is ready to release, and who signs off?
How will you prepare staff for AI-assisted work, and how might their roles change?

Developer Studio & SDLC

How do changes move from development to production today, and where are the delays?
Who approves a release, and which checks must pass first?
How much of your testing is automated, and which areas would you automate next?
How will you keep personal information out of development and test environments?
How will you manage your customizations so that taking a new base version stays manageable?
What skills or training will your developers need as Studio adds AI assistance?

Talk to your account team

Your Sagitec account team can help you decide what to plan for, when, and what it means for your next upgrade.