Skip to content
Case studies

See how the work connects.

From a same-day Design handoff to routine AI follow-through. See verified customer cases and explore workflows that keep the next person informed.

Follow the work

A practical challenge. A connected workflow. A clearer next step.

A closer look

Make the handoff part of the workflow.

Follow recorded customer cases, then explore practical workflow examples for project review and AI assistance. Each entry identifies the result observed or the benefit the example is designed to support.

Verified case
CMK Construction Inc.

Sales to Design

From appointment to Design in one day.

A CMK Construction Inc. project recorded a signed proposal and entered Design on the same date as its scheduled appointment.

The challenge

Moving a sale into Design calls for a clear handoff between the appointment context, the agreed scope, and the team taking over the project.

The workflow

  1. 01

    1:00 PM · Scheduled appointment

    The project’s appointment was scheduled for September 14, 2026, at 1:00 PM Eastern.

  2. 02

    2:07 PM · Proposal signed

    The proposal signature was recorded that afternoon, connecting customer approval to the project’s next steps.

  3. 03

    7:31 PM · Project entered Design

    The project’s recorded workflow reached Design that evening, with the signed proposal available for the handoff.

The result

The project entered Design 6 hours and 31 minutes after the scheduled appointment time, on September 14, 2026.

Historical project records. All times are Eastern. Elapsed time is measured from the scheduled appointment; timing varies with each project’s requirements.

Verified case
CMK Construction Inc.

Project-book review

Six review items reconciled with project evidence.

A project-book review recorded six resolved items through documented corrections, while keeping the remaining findings visible for further review.

The challenge

Documentation, layout, appliance, and scope questions can overlap in a project book. The team needs a way to work through each finding and retain the evidence behind a correction.

The workflow

  1. 01

    Review the project materials

    The recorded November 2, 2026 review included an attached project asset and findings the team could inspect in Book Builder.

  2. 02

    Document the corrections

    Six review items were recorded as resolved. Their correction history covered documentation, layout and code, appliances, additional or omitted scope, and scope authorization.

  3. 03

    Keep the remaining work visible

    The review continued to show that attention was needed. Resolved items and their supporting evidence stayed alongside the findings still requiring review.

The result

Six project-book review items were resolved in the recorded correction process. Remaining issues stayed visible for further review before the package could be treated as ready.

Recorded review and correction history from November 2, 2026. The review remained open for further attention.

Workflow example

Company knowledge

Keep company knowledge ready for your AI agents.

Configure trusted company websites and a refresh schedule, then let connected AI workflows retrieve the published content when they need it.

The challenge

Services and website content change. Copying that information into individual agent instructions creates more places to maintain it.

The workflow

  1. 01

    Choose the sources once

    Enable indexing for trusted company domains. Choose whether to include subdomains and exclude routes or subdomains that should stay out of the knowledge source.

  2. 02

    Let scheduled refreshes do the upkeep

    Set a daily or weekly refresh, or start a run manually. Review indexed pages and status, with the published version available while a new run is prepared.

  3. 03

    Put the sources to work in conversations

    Connected AI workflows can retrieve relevant excerpts and source links as questions arise. When the available material does not answer a question, the agent is guided to seek staff confirmation.

The intended benefit

A maintained, reusable source of company information for connected agents, with website selection, exclusions, and refresh settings controlled by the team.

Workflow example

AI follow-through

Configure the routine. Bring people in for the exceptions.

Put AI agents and configured follow-up workflows to work on intake, qualification, appointment callbacks, and reminders.

The challenge

Routine follow-up competes with new inquiries and project work. Rebuilding the next step for every customer adds more work for the team.

The workflow

  1. 01

    Define how the agent should help

    Configure the agent’s instructions, qualification questions, connected tools, and route to a person in AI Studio.

  2. 02

    Connect the follow-through

    Use configured campaigns and reminders to support the next step, following the company’s timing, channel, and eligibility settings.

  3. 03

    Keep the team in the loop

    Review activity and use the handoff to a person when an exception, approval, or customer question needs human attention.

The intended benefit

Less repeated setup for routine work, with the team’s instructions and controls guiding the workflow and a clear path for human help.

Built around the next step

The context moves with the work.

A connected workflow helps each team understand the project, the evidence behind a decision, and what needs to happen next.

A shared project story

Bring customer context, documents, and next steps together as work moves between teams.

Review before handoff

Make project-book findings and supporting evidence part of the conversation before the next stage.

Configure once, keep working

Give agents the sources, instructions, and follow-up settings to handle routine work, with a route to your team when needed.
Your workflow

Bring us the handoff you want to improve.

Talk through the people, project information, and next steps involved. We can show you where Nucleus fits.