SUPERWISE services · Step 3 of 7

Data and systems discovery

Learn which ideas your data and systems can support before anyone spends on a build.
$20,000 to $45,0004 to 6 weeks

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.

  1. Build

    Data and systems discovery

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.

Build decisions rest on your real systems

Each idea is approved, deferred or dropped on evidence about its data, integrations, effort and risk, not on how good a demo looked.

Everyone works from one ranked list

Business and technical people leave with the same scored list and a clear first workflow, so planning and budget talks start from an agreed order.

The path to a working result is mapped

The blueprint and build sequence show what connects to what, which dependencies come first and where a proof of concept is still needed.

How it works

Three stages, with your team in the room

4 to 6 weeks

Week 1

Get one map of your systems, data, integrations and decision makers, so gaps show up early.

Weeks 2–3

Turn competing ideas into one list, with each candidate workflow tested for value, effort and risk.

Weeks 4–6

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.

TierPrice rangeDurationIncluded
Service$20,000 to $45,0004 to 6 weeksSystems 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.
What you keep

Systems and data map

A visual and written map of the applications, data stores, integrations, owners and handoffs behind the candidate workflows, with known access and quality limits. Use it to scope integrations and give any future builder a reliable starting point.

Workflow and decision inventory

A record of who starts each workflow, what information it uses, which decisions are made, where people step in and what moves to the next system. It keeps the design tied to the real work and exposes missing owners or exception paths.

Workshop findings

The decisions, assumptions, disagreements and open questions from the two cross-functional workshops at the low end of the range, organized by opportunity. Use it to settle open questions, so the same conversations do not restart during a build.

Scored opportunity list

A ranked list comparing value, feasibility, data readiness, effort and risk, with the reasons and assumptions behind each score. Use it to choose the first workflow and explain why other ideas wait or stop.

Architecture blueprint

The target design for the chosen opportunity: components, data flows, integrations, human approvals, controls and operating boundaries. Use it for security and technical review, a build estimate, or a brief for your own team or another provider.

Sequenced build roadmap

The order of prerequisites, proof points, build and handover, with the dependencies each step needs resolved first. Use it to set the plan and budget without starting dependent pieces at once.

Optional proof-of-concept brief

If one material technical question stays open, a separate brief defines the test, sample data, pass condition and 2- to 4-week limit; the proof of concept itself is not included. Use it to buy only the evidence you need before production work.
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

Sets the priorities, brings the right functions in and approves the final order.about 1 hour

Business and domain leads

Walk through the candidate workflows, explain value and exceptions, and join the two workshops.about 2 to 3 hours during workshop weeks

Systems and data owners

Explain the applications, data, integrations, access and known limits, and review the map.about 2 to 4 hours in weeks 1 to 4

Security or governance owner

Reviews data flows, access boundaries, approval points and controls for the shortlist.about 1 to 2 hours during review weeks
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 team wants AI account summaries, but the facts sit in a CRM, email and a line-of-business system. Discovery maps the sources, identifiers, access and handoffs before anyone promises an agent.

A document workflow looks ready to automate

Invoices, claim files or forms arrive in several formats and people re-key the same fields. Discovery checks sample availability, exception paths and the destination system before the workflow is ranked.

Leaders have a long list of AI ideas

Several departments propose assistants, forecasts and automations. Two cross-functional workshops compare them on value, feasibility, effort and risk, and produce one scored list.

A legacy system may block the plan

The workflow depends on an older system with limited interfaces. Discovery shows what can be reached, what needs remediation and whether a different sequence is more practical.

The team needs evidence before a full build

An opportunity looks valuable, but a technical assumption is unproven. Discovery defines the smallest optional proof of concept to test it, separate from production work.

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.

Tools in scope (required)