Integration Layer · Client Onboarding

Let’s scope your Agentic PMO integration.

Answer the questions below to scope the custom sync connector between your scheduling tool (Primavera P6 / MS Project) and Agentic PMO. Your answers drive the field mappings, sync cadence, and effort estimate. It’s also why this connector is custom-built — your custom fields and workflow are unique.

~30–45 minutes · answers auto-save in this browser · export to Markdown and email it back when done. Some questions are best answered by your PMO lead and your IT/API owner together.

What happens next

We review your answers and confirm scope, custom-field mappings, and sync direction.
We validate API access with a test call to your tool — Phase 1: Discovery.
We build and test the connector against sample data — Phase 2: Build.
We deploy, run an initial full sync, and monitor for 48 hours — Phase 3: Deploy.
We hand over the source code and documentation — Phase 4: Handover.

Estimated build effort: 8–12 days after this questionnaire is complete and API access is confirmed. The integration-layer code is owned by you.

What we will not do

Pilot before scale. Every engagement begins with a bounded pilot against one project.
Your schedule of record stays authoritative. Default sync is one-way into Agentic PMO; we never write back without explicit configuration.
No schema lock-in. The connector talks to Agentic PMO’s REST API only — no direct database writes, no backend changes.
Indicative, not inflated. This scopes honestly; it is not a fixed quote until API access and custom fields are confirmed.