> For the complete documentation index, see [llms.txt](https://docs.nested-knowledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nested-knowledge.com/start-a-pilot-trial/enterprise-pilot.md). # Enterprise Pilot A 30-day, structured path to proving Nested Knowledge's value for your team's evidence synthesis needs {% hint style="info" %} Looking to start an Enterprise pilot but haven't met with us yet? No problem, [contact sales](mailto:sales@nested-knowledge.com) to get set up. {% endhint %} ### Pilot Value and Outputs In 30 days, your team completes a full rapid review on your own Research Question in Nested Knowledge, finishing with real research you can use and firsthand proof of how AI-assisted synthesis fits your workflow. ### Before We Start: Your Research Question The best pilots start with a Research Question already on your plate. Send or bring this question (plus population, intervention/exposure, comparator, and outcome) so we can co-build a full rapid review and deliver immediate value as part of the training and pilot. ### How It Works – Training & Co-build Sessions

Timeline of Enterprise Pilot training and co-build sessions — Enterprise Pilot training and co-build session timeline

### What Nested Knowledge Provides 24/7 Support * A dedicated contact for the full 30 days * Assistance with Search & Configuration on your Research Question * Two structured training sessions, timed to each stage of the workflow * On-call 1:1 support throughout the pilot, whenever your team has questions ### What We Need From You * Your Research Question, shared 5–7 business days before kickoff, so we can pre-build the search * Identify the key team members who should be involved in the pilot, we recommend: * An Executive Sponsor / Decision Maker who can attend kickoff and the Day 30 decision call * A Pilot Lead who attends the two trainings and works in the platform on test reviews * About an hour a week of hands-on time, plus participation in the Day 15 check-in and trainings

Recommended review types to pilot

Not sure which review type fits your 30-day pilot? Match your team's goal to a starting point below, then refine it with your Nested Knowledge contact before kickoff. | Your goal | Recommended review type for your pilot | Why it fits 30 days | | -------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------ | | Reach a defensible answer to a focused, time-sensitive question | Targeted / Rapid Review | Built for a narrow question on a tight timeline — the closest fit to a 30-day window | | Replicate a full existing review with systematic rigor | [Systematic Literature Review (SLR)](/guides/guidance-by-review-type/systematic-literature-review.md) | Import your SLR and turn it into a living review | | Compare effectiveness or cost outcomes between therapies | Targeted/Rapid Review scoped to one comparator pair | Full statistical synthesis across a treatment network is a heavier lift than a proof-of-value pilot is built for | | Map how much, and what kind of, evidence exists on a broad topic | [Scoping Review](/guides/guidance-by-review-type/scoping-review.md), scoped to one sub-question | Broad landscape questions can expand quickly in corpus size; one representative slice keeps the pilot on track | | Pinpoint where evidence is missing, to guide future research | [Gap Analysis](/guides/guidance-by-review-type/gap-analysis.md) | Identifying missing evidence is usually a bounded exercise well suited to one pilot window | | Describe and interpret the literature in narrative prose, for an internal report or briefing | [Narrative Review](/guides/guidance-by-review-type/narrative-review.md) | Narrative synthesis of a defined topic is usually straightforward to scope to 30 days | | Support a health-technology submission (clinical, epidemiological, or economic) | [HTA submission](/guides/guidance-by-review-type/evaluations-for-hta-submission.md) route, scoped to one component | Piloting a single clinical, epidemiological, or economic question gives a representative test of the full workflow | *These are starting points, not requirements — your Nested Knowledge contact will help you scope your specific research question at kickoff.*

### What You Walk Away With at Day 30 By Day 30, your team will have: * A completed rapid review on your own Research Question — real research, not a demo * Validation of AI-assisted screening, tagging, and synthesis on your topic, checked by your own team * A documented results summary showing the time and effort saved on your review * A clear, evidence-based decision on next steps, made together on the Day 30 call ### Questions? Reach out to your Nested Knowledge Account Management contact directly — that's what the 30 days are for. Or email us directly at ### Useful links per phase #### Phase 1. Setup


Quickstart	Set up your first nest and begin reviewing evidence.	Quickstart
Organization Management	Manage your organization and its members.	Organization Management
Core Concepts	Learn the objects and terminology used in Nested Knowledge.	Core Concepts
Nest Setup	Choose your review route and prepare your nest.	Nest Setup
Build With AI	Use AI-assisted tools to build your nest.	Build With AI

#### Phase 2. Search and Screening


Search	Find, import, and organize literature for your review.	Literature Search
Screening	Review records with configurable screening workflows.	Screening

#### Phase 3. Tagging and Synthesis


Tagging	Capture structured evidence from included studies.	Tagging
Synthesis	Build and share outputs from your review.	Synthesis
Study Inspector	Find, filter, edit, and export your studies.	Study Inspector
Exports And Outputs	Export review data and generate shareable outputs.	Exports

#### Phase 4. Questions, close-out, and move to contracting


Subscriptions	Set up continued access after your pilot.	Subscriptions
AI Transparency	Review AI oversight, traceability, and data practices.	AI Transparency

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.nested-knowledge.com/start-a-pilot-trial/enterprise-pilot.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.