How pricing works

We scope each engagement around the business result, the work to deliver it and the support after launch. We discuss these needs with your team before we propose the work. This includes how the solution runs and who operates it.

  • WashU Medicine: infrastructure costs at 1/3 of the traditional approach
  • First use case live in 90 days
  • WashU Medicine
  • University of Kansas Medical Center
  • Saint Francis Healthcare System
  • Saint Louis University
  • Compana Pet Brands

The work included in an engagement

We define the outcome with your stakeholders, then get the first use case live in 90 days. Our team builds the solution on Databasin, including the connections, definitions and workflows it needs.

Communication, rollout, training and success measurement are part of that work. The proposal describes the first use case and how we will judge its result, along with the platform and support arrangements.

What shapes the scope

Sources and definitions

Source owners help us understand the records and the measures people use. We identify the connections and preparation needed to build the agreed analysis.

Process and adoption

We examine how departments prepare and use information today. That tells us what staff will need to learn and how to introduce the new process.

Deployment and operation

We account for the environment and the people operating it. Hosting with Databasin, installing in private Azure or using an existing platform changes that work.

Bring the question you can't answer today.

In the demo call, we look at where that data lives and who prepares it now. Then we show a working example. Not ready to talk? Send a short question. Our data team replies by email within one business day.

  • In production at WashU Medicine since 2022
  • HIPAA-ready, with a BAA available
  • First use case live in 90 days

Ask about your setup

Which data do you want to use?
Which platform do you use now?

Three ways to run the solution

We run it

Databasin operates the solution for you. The proposal defines the data products, workflows and operating responsibilities our team will handle.

Monthly support hours

Set aside monthly time with our team for help and further development. We agree the work that this continuing support covers.

On call

Keep our team available when you need help. We agree how to request that help and define the work involved.

Design, Build, Run

We take responsibility for the work from defining the outcome through implementation and ongoing support.

Design

We define the outcome, current processes and expected return with your stakeholders. A working example shows how Databasin would answer your business questions.

Build

We get your first use case live in 90 days. Communication, rollout, training and success measurement are included in the work.

Run

Choose the help you need after launch. We can run the solution for you, provide monthly support hours or stay on call.

Discuss the scope of the work

Tell us about the work you would like to improve. We can discuss the systems it depends on, show where Databasin would help and explore how much implementation and ongoing support your team needs from us.

FAQ

How can we evaluate Databasin before an engagement?

The starting point is a demo. You can see the relevant parts of Databasin and ask about the work of implementing them. We can discuss what your organization would need to evaluate next, from its data and deployment requirements to how people would use the result.

What should we look for in the proposal?

The proposal should connect the result you want to the work we will do. It sets out the systems involved, what we will implement, how staff will learn to use it and how we will measure success. It also describes the support you have chosen after launch.