# Pilot: one workflow, measured against your own baseline Pilot: start on one workflow ยท DataBridge by Walnut A pilot on one workflow your team repeats, installed on your machines, with scope and measures agreed in writing first. A pilot runs DataBridge on one workflow your team repeats, installed on your machines. Scope and measures are agreed in writing first, and you decide what comes next on your own numbers. It starts with a demo on a sample of your own documents and data. ## [Tell us your workflow](https://walnut.sg/start/#contact-head) Write to outreach@walnut.sg with one task your team does every week. Which job costs your team hours? Every new data or AI project begins with months of data gathering. ### What changes with DataBridge Sources connect once. Every project after that draws from the same record, in the format it needs. ### What you get back Projects start sooner Start here: Projects start sooner. [Plan a pilot on it](https://walnut.sg/contact/). Access requests hold up new joiners and project teams. ### What changes with DataBridge Access follows each person's role, set once by your administrators. ### What you get back Access set once, by role Start here: Access set once, by role. [Plan a pilot on it](https://walnut.sg/contact/). Old systems decide which tools teams can use. ### What changes with DataBridge DataBridge reads data where it sits and feeds the tools you choose. Retire the old system on your schedule. ### What you get back Freedom to change tools Start here: Freedom to change tools. [Plan a pilot on it](https://walnut.sg/contact/). Know-how leaves when people move on. ### What changes with DataBridge Decisions, corrections and context stay in the record with the evidence behind them. ### What you get back Knowledge that stays Start here: Knowledge that stays. [Plan a pilot on it](https://walnut.sg/contact/). Routine emails and reports are put together by hand. ### What changes with DataBridge Ask in one sentence. The draft is ready for a person to check and send. ### What you get back Hours back every week Start here: Hours back every week. [Plan a pilot on it](https://walnut.sg/contact/). ## [How a pilot runs, in five steps](https://walnut.sg/start/#steps-head) ### See it on your files A demo on a sample of your own documents and data. ### Agree the workflow Scope and success criteria in writing, with a named owner on each side. ### Set up on your machines Installed and connected to your sources. ### Measure Hours and outcomes tracked against the baseline you set. ### Decide what comes next Expand to more teams, with your data and the full record always yours to keep. ## [What is measured](https://walnut.sg/start/#measure-head) Hours and outcomes on one workflow, against the baseline you set at the start. ## [What you keep](https://walnut.sg/start/#keep-head) You keep everything built from your data, and a record of every question asked and answered during the pilot. You can export both. It starts with a demo on a sample of your own documents and data.