Question 1

What does the Workflow Live Guarantee cover?

Accepted Answer

If the selected workflow is not live in production by the end of week 12 (measured from Phase 4 kickoff, recorded in Schedule A of the engagement letter), your final invoice (the 20% closing instalment) is reduced by 50% and we keep working at no additional cost until the workflow is live. Eligibility: scope locked at signing, client-side dependencies delivered per the SOW timeline (data access by Day 14 of Phase 4, integration approvals by Day 21, named subject-matter expert at least 4 hours/week), remedy invoked in writing within 14 days of the week-12 deadline. We commit to the result, not the procedure.

Question 2

What counts as 'live in production'?

Accepted Answer

The canonical definition lives in our Phase 4 quality gate, incorporated into the engagement letter by version tag and SHA pinned at signing. The dimensions: the workflow runs against the production environment (not staging), users in your team can invoke it, monitoring and alerting are in place, real data flows through it (not test fixtures), and your team has run-instructions to operate it. Stability (uptime, sustained operation over a window) is tracked separately under the Measurement Framework as a non-guarantee SLA.

Question 3

What if my data isn't ready by the deadlines in the SOW?

Accepted Answer

The SOW specifies named, dated client-side deliverables: data access by Day 14 of Phase 4, integration approvals by Day 21, named subject-matter expert availability of at least 4 hours/week. If those dates slip, the Workflow Live Guarantee eligibility is voided. We'll still finish the work, but the 50% remedy doesn't fire on a missed deadline caused by a missing input. The dependencies are listed plainly in the engagement letter so there's no ambiguity at week 12.

Question 4

What if we want to change scope mid-engagement?

Accepted Answer

Mutually-signed change orders are allowed, but they have to specify what happens to the week-12 clock: reset to the change-order signature date, or extend by an agreed delta. The change order is the artifact. No clock changes happen verbally. If you don't specify, the default is Extend, with a delta proportional to the operator-day cost of the changed scope. Same logic for Disqualifying Events (RIF over 10% of the named delivery team, system migrations, vendor outages over 5 business days): they suspend the guarantee, not the engagement.

Question 5

Why 12 weeks specifically?

Accepted Answer

Phase 4 builds for First Workflow Live engagements take 8-12 weeks in our methodology. Vendor-led where possible, integration-heavy, with a kickoff at the start of the phase that pulls your team and the chosen vendor into the same room. Twelve weeks is the upper end of that range. If we're sitting at week 11 with a buggy build, the guarantee tells you we'll keep working free until it's live; it doesn't tell you we'll cut corners to ship a half-built workflow at week 11.5.

Question 6

How is this different from a generic AI consultancy?

Accepted Answer

Generalist consultancies sell a deck and a roadmap. We sell a shipped workflow with a contractual commitment to its launch date. The Workflow Live Guarantee is the part of the offer companies most often ask for and most consultancies don't carry. The trade-off: we're scoped tight (one workflow, locked scope at signing); we won't take an engagement we can't ship.

Question 7

What if AI isn't right for the workflow you'd build?

Accepted Answer

We say so before signing. The First Workflow Live engagement starts after a Phase 1 Workflow Audit Report (run as the AI Ops Review or as Phase 1 of the Operating Plan) ranks pains and recommends a build. If the highest-ranked pain doesn't have a defensible AI shape, we recommend against the build, and we don't take the $50K. The engagement opens only when the recommended first build holds up under the deeper Phase 1-3 evidence set.

Question 8

Should I start here or with the Operating Plan?

Accepted Answer

If you've already had an Operating Plan and you know the workflow you want, start here. If you don't, start with the AI Ops Review ($4,950) or Operating Plan ($20K) so the recommended first build is defensible before we commit to shipping it. The First Workflow Live tier is the build engagement; the audit/strategy work that defines what to build is upstream.

One workflow.
Live in production.
Twelve weeks. Guaranteed.

Audit, plan, design, ship.

Workflow Audit Report

AI Opportunity Matrix + Roadmap

Architecture Blueprint + Business Case

Shipped workflow

When the build is what's left.

You've already had a Review or Operating Plan and you know the workflow you want to build first.

You could build it in-house, but the calendar says otherwise.

An earlier AI initiative stalled. You need someone who'll commit to a finish line.

What you walk away with.

If your workflow isn't live in production in 12 weeks, we cut your final invoice in half and keep working free until it is.

The first questions we hear.

Ship one workflow you've been waiting on.

One workflow.Live in production.Twelve weeks. Guaranteed.