Offer

AI Readiness Review

Find where AI helps your teams today and what to secure before an agent touches live data.

Most contractors run project management, scheduling, accounting and field tools, each with its own credentials and API, and agents tend to pick up access to all of them. Large APIs such as Procore's give an agent thousands of possible actions, and billing, change orders and baseline schedules carry contractual weight. Without a narrow first question and an access plan, pilots either stall or take on risk nobody signed off on.

Who it's for

  • CIOs, IT directors and construction technology leaders being asked for an AI plan
  • Project controls and scheduling teams curious about AI for Primavera P6 and XER analysis
  • Operations leaders who want AI answering questions about Procore or financial data
  • Companies that want guardrails in place before staff connect agents to live systems on their own

What you get out of it

  • A short list of AI use cases ranked by value, data readiness and risk, each tied to a specific question your team asks
  • A map of the systems, APIs and identifiers each use case needs, including where systems disagree
  • An access and governance plan: read-only first, scoped credentials, logging and where human approval is required
  • A pilot design for the top use case, with success measures agreed before anything runs
  • Data-quality gaps that would undermine AI answers, with where to fix them
  • A clear view of which ideas are not worth pursuing yet, and why

What's included

Stakeholder interviews

Conversations with the people in finance, operations, scheduling and IT who would use or approve AI tools, focused on the questions they answer by hand today.

Systems and data inventory

Which systems hold the data each use case needs, how they can be reached (API, database, export or offline files such as XER), and how projects and jobs link across them.

Use-case scoring

Each candidate is assessed for value, data readiness and blast radius, separating analysis and explanation, where AI is most reliable, from drafting and write-backs, which need tighter oversight.

Governance and access plan

Least-privilege credentials, a single secret store, read-first rollout, per-call logging, tool routing for large APIs and named approval for any write.

Pilot plan

A step-by-step pilot for the top use case, starting on exports, sandboxes or closed projects, with an evaluation rubric and a set of real questions to test against.

Readout

A written report and a working session with your leadership covering the recommendations, the risks and the next decision to make.

How it runs

  1. 01

    Free scoping call

    We agree which teams and systems are in scope and what decision the review should support, then fix the scope and price.

  2. 02

    Interviews and inventory

    We talk to the people involved and review the systems, data access and any AI tools already in use.

  3. 03

    Assessment

    Use cases are scored, data gaps are tested where access allows, and the governance plan is drafted.

  4. 04

    Readout and pilot plan

    We present the findings, agree the first pilot and hand over the written report.

What we need from you

  • An executive sponsor and a point person to coordinate interviews
  • Time with the people who would use or approve AI tools in finance, operations, scheduling and IT
  • A list of your core systems and admin contacts, plus read-only or sandbox access where you want data tested
  • Sample artifacts where relevant, such as an XER export, a monthly report or a current IT security policy

Not included

  • Building or deploying production agents; that is scoped separately once a pilot is chosen
  • Write access to any production system during the review
  • A formal security audit, penetration test or legal review
  • Vendor selection across AI platforms beyond the use cases in scope

See it in real builds

Frequently asked questions

How much does it cost?

Fixed scope, fixed price, agreed after a free scoping call. The price depends on how many teams and systems are in scope.

How long does it take?

It depends on the number of systems and how quickly interviews can be scheduled, so we scope the timeline in the call and write it into the proposal.

Do you need access to our live systems?

Not necessarily. Much of the review works from interviews, documentation and exports such as XER files. Where testing live data helps, we ask for read-only or sandbox access only.

Will you recommend a specific AI product?

We recommend what fits the use case. Sometimes that is an existing feature in a tool you already own, sometimes a governed agent over your data, and sometimes not using AI for that problem yet.

What comes after the review?

You get a pilot plan you can run with any team. If you want us to build it, we scope that as a separate fixed-price project.

Is this only about scheduling?

No. We cover project management, financial reporting and scheduling data. Scheduling is a common starting point because XER files allow analysis without touching a live database.

Start with a free scoping call

Fixed scope, fixed price, agreed before we start.

Tell us your systems and what the result needs to look like. We reply within two business days with an honest take on fit, scope, and next steps.

Other ways to start