SUPERWISE services · Step 3 of 7
Data and systems discovery
What you walk away with
- Systems and data map
- Workflow and decision inventory
- Workshop findings
- Scored opportunity list
Where this fits
Step 3 on the services path
Each step answers the question the last one raised. Start wherever the assessment points you.
Assess
AI Readiness AssessmentStart safely
Assisted deploymentBuild
Data and systems discovery
Govern and run
AI governance and controls
Why it matters
What changes for your team
Before anyone funds a build, you know which AI workflows your data and systems can support, which one goes first, and the architecture and sequence to build it.
Everyone works from one ranked list
The path to a working result is mapped
How it works
Three stages, with your team in the room
4 to 6 weeks
Get one map of your systems, data, integrations and decision makers, so gaps show up early.
Turn competing ideas into one list, with each candidate workflow tested for value, effort and risk.
Leave with an architecture your owners can review and a build sequence you can budget for.
The details
Everything you need to decide
Price, fit, your team’s time, how data is handled, and what you keep.
Price and scope
Draft pricing for review: we confirm a fixed scope and price after a scoping call.
| Tier | Price range | Duration | Included |
|---|---|---|---|
| Service | $20,000 to $45,000 | 4 to 6 weeks | Systems and data map |
Not included
- Production implementation, an agent build or deployment of the architecture blueprint.
- Cleaning, migrating or repairing source data and legacy systems.
- Software, model, data or other third-party subscriptions.
- The optional $10,000 to $25,000 proof of concept, which discovery can define but which is scoped separately.
- Extra workshops, business units or systems beyond the agreed scope.
Is this the right starting point?
Good fit if
- For teams that need to know which workflows their data and systems can support before they build.
- Teams of 50 to 500 people with several systems or AI opportunities
- You want a defined handover your team keeps.
Start somewhere else if
What you keep
Systems and data map
Workflow and decision inventory
Workshop findings
Scored opportunity list
Architecture blueprint
Sequenced build roadmap
Optional proof-of-concept brief
What your team gives
About 20 to 35 hours across the team for a typical discovery, concentrated in interviews, two workshops and review of the map and blueprint. These are planning figures and are confirmed against the number of systems and business units in scope.
Executive sponsor
Business and domain leads
Systems and data owners
Security or governance owner
Data, security, and ownership
- Discovery maps the systems, data categories, flows and access conditions agreed in scope; it does not require moving production data into a SUPERWISE product.
- System access and credentials remain under your control. The work starts from interviews, existing documentation and samples or demonstrations your owners approve.
- The architecture blueprint records human approval points, access boundaries, logging and audit needs so they are part of the build plan rather than an afterthought.
- We do not connect to a live system, copy a production dataset or widen access as part of discovery unless a separate scope explicitly authorizes it.
- If health information is in scope, tell us at the start so the design accounts for it.
SUPERWISE signs a Business Associate Agreement with healthcare customers, and the scope is confirmed during scoping. See the trust center.
You keep the whole package: systems and data map, workflow inventory, workshop findings, scored opportunity list, architecture blueprint, roadmap and any proof-of-concept brief. The assumptions and decisions stay visible, so if you stop working with us, your team or another provider can use it to scope the next work.
Discovery ends with a build sequence and a decision on the first workflow. A separately priced proof of concept, $10,000 to $25,000 over 2 to 4 weeks, is worth it only when a material technical question remains. The chosen workflow can move into an agent build, or governance or data remediation comes first when the findings make it a prerequisite; production implementation and managed operations are separate engagements.
Examples and how we measure success
These are examples of suitable work, not claims about past client engagements.
Customer information lives in several systems
A document workflow looks ready to automate
Leaders have a long list of AI ideas
A legacy system may block the plan
The team needs evidence before a full build
Measures we agree at kickoff
- Map completeness: the owners of the in-scope systems and workflows agree the material sources, integrations and handoffs are shown.
- Decision quality: each shortlisted opportunity has a value, feasibility, effort and risk assessment with its assumptions visible.
- Technical fit: the selected opportunity has an architecture its system, data and security owners can review.
- A buildable sequence: the roadmap names prerequisites, owners and decision points clearly enough to scope the first build.
- Open questions are bounded: each unresolved assumption has a named owner and a document check, access task or optional proof-of-concept test.
Who delivers the work
No case study of a data and systems discovery engagement has been published, so none is shown. Renova Health is the nearest real example of AI built into an existing operating workflow; it is not presented as the result of this service.
Data and systems discovery questions
What to expect before you start
Talk to us
Talk to our team
Tell us about your team and we will scope data and systems discovery with you.