What does discovery cost, and what changes the price?

Data and systems discovery runs $20,000 to $45,000 over 4 to 6 weeks. More business units or systems, legacy or inaccessible data, extra workshops and an optional proof of concept move the work up the range. This is draft pricing for review.

Do you need access to our production systems?

Not by default. We begin with the responsible people, current documentation and approved samples or demonstrations. Any direct access is agreed explicitly, stays under your control and is limited to what the discovery question requires.

How is this different from a readiness assessment?

Readiness chooses where to start across business value, data, systems, governance and operations. Discovery goes deeper once several systems or candidate workflows need to be mapped and produces the architecture blueprint and build sequence.

What if our data is incomplete or hard to reach?

The map records the constraint and the roadmap shows whether to remediate it, change the workflow, test an alternative or stop. Data remediation itself is not included.

Will we know the final build price at the end?

You will have the architecture, dependencies and sequence needed to scope a build. A fixed build price still depends on the chosen workflow, integrations, data conditions and acceptance requirements.

Can another team build from the blueprint?

Yes. You keep the discovery package. It is written to brief your internal team, SUPERWISE or another provider without hiding the assumptions behind the recommended design.

Data and Systems Discovery

What you get

Working outputs, not a presentation about them

You finish knowing which AI workflows your data and systems can support, what should be built first and the architecture and sequence needed to build it.

Systems and data map

A visual and written map of the applications, data stores, integrations, owners and handoffs involved in the candidate workflows, including known access and quality constraints. Use it to scope integrations, answer where information comes from and give a future builder a reliable starting point.

Workflow and decision inventory

A record of the work discussed in discovery: who starts it, which information is used, which decisions are made, where people intervene and what output moves to the next system. Use it to keep technical design tied to the work people actually perform and to catch missing owners or exception paths.

Workshop findings

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

Scored opportunity list

A ranked long list that compares value, feasibility, data readiness, delivery effort and risk, with the reasons and assumptions behind each score. Use it to choose the first workflow and explain why other ideas come later or do not proceed.

Architecture blueprint

A target view of the components, data flows, integrations, human approvals, controls and operating boundaries needed for the selected opportunity. Use it to obtain security and technical review, estimate a build and brief your own team or another provider.

Sequenced build roadmap

A practical order for prerequisites, proof points, implementation and handover, naming which dependencies must be resolved before each step. Use it to set the delivery plan and budget and avoid starting several dependent pieces at once.

Optional proof-of-concept brief

When one material technical question cannot be answered from the available evidence, a separate brief defines the test, sample data, pass condition and 2- to 4-week boundary. The proof of concept itself is not included. Use it to buy only the evidence needed before committing to production work.

Outcomes

What will we have at the end?

A build decision grounded in your systems

The team can approve, defer or reject each opportunity using evidence about the data, integrations, effort and risk behind it rather than relying on a demonstration.

One ordered list instead of competing ideas

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

A path from current systems to a working result

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

Examples

What could this look like in our business?

These are examples of suitable work, not claims about past client engagements.

Example: customer information lives in several systems

A team wants AI to prepare account summaries, but the useful facts sit across a CRM, email and a line-of-business system. Discovery maps the sources, identifiers, access and handoffs before anyone promises an agent.

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

Example: leaders have a long list of AI ideas

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

Example: a legacy system may block the plan

The desired workflow depends on data in an older system with limited interfaces. Discovery identifies what can be accessed, what needs remediation and whether a different sequence is more practical.

Example: 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 needed to test it, separately from production implementation.

Success measures

How do we know it worked?

We agree the measures at kickoff and use them in the final decision.

Measures agreed at kickoff

Map completeness: the owners of the in-scope systems and workflows agree the material sources, integrations and handoffs are represented.
Decision quality: each shortlisted opportunity has an explicit value, feasibility, effort and risk assessment with its assumptions visible.
Technical fit: the selected opportunity has an architecture that the responsible 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: any unresolved technical assumption has a named owner and either a document check, access task or optional proof-of-concept test.

Your team

What does our team need to give?

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 business priorities, brings the right functions into the room and approves the final opportunity order.about 1 hour

Business and domain leads

Walk through the candidate workflows, explain exceptions and value, and take part in the two cross-functional workshops.about 2 to 3 hours during workshop weeks

Systems and data owners

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

Security or governance owner

Reviews data flows, access boundaries, approval points and control requirements for the shortlisted opportunities.about 1 to 2 hours during review weeks

Duration

A build path your team can see

4 to 6 weeks

Week 1

Map the systems, integrations, data stores, and decision makers.

Weeks 2–3

Run workshops and test candidate workflows for value, effort, and risk.

Weeks 4–6

Validate technical fit and deliver the architecture and build sequence.

Data and security

Is our data safe?

How the engagement handles data

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, the design keeps PHI out of the SUPERWISE platform because the platform is not covered by a BAA.

Ownership

What do we own when it is over?

You keep the systems and data map, workflow inventory, workshop findings, scored opportunity list, architecture blueprint, roadmap and any proof-of-concept brief. If you stop working with us, the assumptions and decisions remain visible so your team or another provider can use the package to scope the next work.

After the engagement

What happens after?

Discovery ends with a build sequence and a decision about the first workflow. A separately priced proof of concept is useful only when a material technical question remains; it runs $10,000 to $25,000 over 2 to 4 weeks. A selected workflow can move into an agent build, while governance or data remediation is handled first when the findings show it is a prerequisite. Production implementation and managed operations are separate engagements.

Draft pricing for review

Know the range before the first call

We confirm a fixed scope and price after a scoping call.

Tier	Price range	Duration	Included in a line
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; discovery can define it, but delivery is separately scoped.
Additional workshops, business units or systems beyond the agreed scope.

Fit

Know whether this is the right starting point

Teams of 50 to 500 people with several systems or AI opportunities

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

You need to decide where to start before mapping systems.

Start with AI readiness assessment

Who delivers and proof

Delivered by the SUPERWISE services team

We have not published a case study for a data and systems discovery engagement, so we do not present one. The Renova Health case study is the nearest real example of AI integrated into an existing operating workflow; it is not described as the result of this service.

Related published work

The nearest approved examples for this work.

Renova Health case study