curiosity

Services · Curiosity Advantage

Curiosity Advantage
with the team behind Studio

Engineers who build Studio work with your team. They help you plan the first tools, connect the systems that hold your records, ship to your users and keep every tool current.

For New and existing customers With Curiosity engineers Where On site or remote Agreed in Your order form

Why Advantage

Your first tool sooner, your tenth on the same foundation

New customers get from a signed order to a tool in production with people who have done it before. Existing customers keep up with releases and add the next tools without starting over.

01

Work with the people who build it

Our forward deployed engineers write Studio’s code. They work with your business and technical teams from the first workshop to production.

02

Start from the systems you run

We connect your tickets, part records and maintenance logs where they live, with Studio’s connectors for 70+ systems and a connector we write with you for the rest.

03

Keep access as it is

Access is synced from your source systems. A tool we build with you shows each person only what the source would already show them.

04

Grow from one tool to many

The connected data, the permissions and the audit trail stay in place. The next tool reuses them, so it takes less work than the first.

What it includes

Planning, building and running, with one team

Each engagement is agreed in your order form, so it covers the parts your team needs.

Success planning

Goals and reviews

We agree the first tools, the teams that will use them and how you will measure them, then review progress with you at regular intervals.

Connecting your systems

Onboarding

We map your sources into Studio, set up permissions from the systems that own them and check the first answers against real records.

Building the first tools

Delivery

Our engineers build alongside your team: apps, dashboards and agents on your connected data, shipped to real users.

Deployment

Your infrastructure

On premises, in a private cloud or air gapped, with the model you choose. We size the hardware with you and plan the install.

Upgrades and health checks

Running

We review how your deployment runs, plan upgrades with you and show your team what changed in each release.

Training

Your team

Instructor led sessions for the people who run Studio, build on it and use it, on site or remote.

How it runs

Plan, build, then run and grow

An engagement follows the same three steps, whether it starts with a pilot or a rollout.

  1. 01

    Plan

    Agree the goals, the first tools, the systems they need and who uses them.

  2. 02

    Build

    Connect the systems, build the first tools with your team and ship them to their users.

  3. 03

    Run and grow

    Review the results, plan upgrades and pick the next tools on the same foundation.

Before you start

Hardware, network, data, model, expertise and permissions: what a Studio project needs, and what a pilot can skip.

Read the Whitepaper

Your data. Your infrastructure.

Ship your first tool with the team that builds Studio