Founding pilot
The UDDI Founding Pilot
Two weeks. Your Azure tenant. One team and one knowledge domain — ending in a decision, not a demo.
What it is
A real team, real documents, a real decision.
UDDI deploys into your Azure subscription and answers questions from the SharePoint content your teams already trust — with citations back to the file, filtered by the permissions you already manage.
The pilot puts that in front of one real team, on one real knowledge domain, for two weeks. Not a sandbox with our sample data: their documents, their questions, their permissions.
It ends with numbers — usage, answer helpfulness, knowledge gaps, and a permission test you can hand to security — and a production plan you can say yes or no to.
Who it's for
A good fit looks like this.
- A team whose day involves finding things in SharePoint: specs, standards, procedures, contracts, project folders.
- A knowledge domain with a few hundred to a few thousand documents, mostly Office and PDF, that lives in one or two SharePoint sites.
- A sponsor who can make the production decision at the end, and a team lead who will spend an hour building the first collection.
- Microsoft 365 with Entra ID, and an Azure subscription — or the ability to create one.
You bring
- A sponsor and a team lead
- The sponsor owns the decision; the team lead owns the collection. Together, about three hours across the two weeks.
- Five to fifteen pilot users
- The team that actually asks the questions. They sign in with the Microsoft accounts they already have — no new logins.
- One SharePoint site or library
- The knowledge domain. Documents never move; UDDI reads them in place through Microsoft Graph under delegated permissions.
- An Azure subscription
- UDDI's application, search index and model calls run here — nothing runs on our side. Someone with Contributor rights and Azure OpenAI enabled.
- One consent, once
- A Global or Application Administrator grants the app's permissions in a single consent screen on day one. About fifteen minutes, and it is the last time we need them.
We bring
- Deployment into your tenant
- We deploy and configure UDDI in your Azure subscription with you on the call — your keys, your network, your audit logs.
- A hands-on curation session
- We sit with the team lead while they build the first collection. Ninety minutes, and they can do the next one without us.
- A permission and security review
- We test that answers respect your SharePoint permissions and Entra groups using your own accounts, and walk your security contact through the data boundary and audit trail.
- The readout and production plan
- Usage, helpfulness ratings, knowledge gaps, what to add next, what it costs to run — and a written plan for rolling out to the next teams if you choose to.
The two weeks
Day by day.
Day 1
Kickoff and deploy
Scoping call, admin consent, deployment into your Azure subscription, SharePoint connected. Success criteria agreed and written down.
Days 2–3
Curate
The team lead builds the first collection from the chosen site with the file picker, scoped to the right Entra group. A managed site can be added for whole-site coverage. Indexing runs the same day.
Days 4–10
Use it for real
The team asks the questions they actually have, in the web app and optionally through the @UDDI bot in Teams. We watch the Insights dashboard together mid-week and do a second curation pass on the gaps it surfaces.
Days 11–12
Permission and security review
Access tests with your real accounts and groups: someone outside the team must not see the team's answers. Audit-log walkthrough. Data-boundary summary for your security reviewer.
Days 13–14
Readout and decision
The numbers against the criteria from day one, the knowledge-gap list, running costs from your own Azure bill, and the production plan. Then you decide.
How we'll know it worked
Success criteria, agreed on day one.
We set these together at kickoff and write them down. Defaults we propose, adjusted to your team:
- Adoption — at least two-thirds of pilot users ask five or more real questions during the fortnight.
- Helpfulness — at least 70% of rated answers are rated helpful, and every answer cites its source.
- Permissions — zero cases in the access tests where someone sees content they could not already open in SharePoint.
- Knowledge gaps — the gap list at readout is something the team lead recognises as a real curation to-do, not noise.
- Cost — running cost for the fortnight, from your Azure bill, lands inside the estimate we gave at kickoff.
Your data during the pilot
Nothing leaves your tenant. Including during the pilot.
- Everything runs in your Azure subscription: the application, the search index, the embeddings and the model calls. There is no UDDI-hosted copy of your content.
- Documents never move. UDDI reads SharePoint through Microsoft Graph under delegated permissions — it can only see what the connecting user can see, and per-document permissions are carried into every answer.
- Answers are filtered by the asker's identity before retrieval, and retrieval fails closed when authorization is uncertain.
- Azure OpenAI in your subscription generates answers and does not train on your content.
- If you stop, delete the resource group. Your documents were never anywhere else.
Founding-pilot terms
3 founding pilots. Here are the terms.
- The guided two-week pilot is at no charge. The only cost to you is the Azure consumption in your own subscription — typically around $75 for the fortnight plus pennies-per-question model usage, billed at your rates.
- If you continue, your first year of Tenant-Deployed is at half the list price on the pricing page ($25 per user per month billed annually, 50-seat minimum), locked for that year — so a 100-person team pays $15,000 instead of $30,000.
- In return we ask for candid feedback throughout, and — only if the pilot earns it — a case study that you approve line by line before anything is published. Your name never appears anywhere without that approval.
- If it doesn't earn it, you keep the feedback and everything UDDI built in your tenant; we keep the lesson.
Next step
Reply with the team, the knowledge domain, and a rough document count, and we'll schedule a thirty-minute scoping call. Kickoff is usually within a week of that call.
Ask about a founding pilotOr write to pilots@uddi.co.