Skip to content

Support, changes and care plans

Schedule ID: PS-CARE-2026-11-15-v1 · Version 1 · 15 November 2026

This schedule applies only when incorporated into an accepted order.

The accepted go-live baseline, incidents and change orders must be recorded. The order records the applicable tier/plan, actual dates, business-day calendar and time zone. The 90-day build defect warranty starts at go-live; each delivered change has its own 90-day defect warranty from delivery. Plans start after the initial support window.

At a glance

1. Who pays when something stops working

Baseline: the build as accepted at go-live. It includes the acceptance test record, the run log, and the outside systems as they were then (API and model versions, the client's settings and data formats), all recorded in the handover docs.

Deciding the cause (in this order):

  1. Replay the failing case against the baseline. If it fails on the baseline, it's a defect. If it passes on the baseline and fails only since then, it's upkeep.
  2. If the baseline can't be replayed (for example, the vendor retired that API or model version), we decide from documented evidence. If there's an outside change notice dated after acceptance, and the run log or acceptance record shows this case passing after go-live, it's upkeep. Without both, it's a defect: when the evidence is unclear, the client gets the benefit of the doubt.
  3. Unhandled cases: Build Schedule PS-BUILD-2026-11-15-v1 promises that anything outside the handled edge cases goes to a human.
    • If such a case wasn't routed safely (it was auto-processed, dropped, or no alert went out), that's a defect, and the fix is to route it correctly.
    • Teaching the build to handle that case automatically is a change.

Who pays (one payer per row):

Plans start when the support window ends, which is why the support-window column has no plan split. The 90-day warranty runs whether or not the client has a plan.

2. Changes before go-live: recount, ledger, pay the difference

Two separate numbers on every change order:

Build total = the higher of the scope value and billed. Outstanding = build total − billed, spread over the remaining milestones in proportion to their original sizes. The final milestone is always billed at go-live, so before go-live there is always one left to adjust.

Each order:

  1. Recount the active scope after the change, using the Build Schedule PS-BUILD-2026-11-15-v1 criteria, then work out the new charged scope (active + held units).
  2. Change in build price = new build total − old build total. A positive number is added to outstanding. A negative number is a credit that reduces outstanding. It never becomes a refund.
  3. Order charges, invoiced on approval: $250 fee if the order adds or rebuilds a unit, plus rework (at the section 3 list price) for any started or built unit that has to be done again.

What the client can rely on: the build total equals a fresh Build Schedule PS-BUILD-2026-11-15-v1 quote of the final scope, whatever order the requests come in and whether they're made one at a time or together, with two exceptions:

Fees, rework and Build Schedule PS-BUILD-2026-11-15-v1 adders come on top. Build Schedule PS-BUILD-2026-11-15-v1's bump rule still applies, and so does its option to split the work into phases.

Count-neutral changes (replace or redesign a unit, with the same counts; anything that isn't a minor tweak, see below):

Minor tweak (definition). A tweak changes a value inside an existing unit and passes all 4 tests: (1) the counts are unchanged; (2) no new API call, endpoint, data source or destination; (3) no change to what an AI step extracts, classifies or decides, or to a workflow's branching; (4) the existing test set still passes, with only the edited value changed in its expected outputs.

Removals don't carry a fee. On a flat S or M tier, removing a unit inside the band leaves the scope value the same, so the credit is $0.

3. Changes after go-live: unit list

The accepted build is the baseline, and its tier band is used up. The support window counts as after go-live.

Scheduling (one formula for every order, before or after go-live):

4. Plans after go-live

Plans start when the tier's support window ends.

Points: Improve = Keep + 75% of the points' value, so changes paid with points cost 25% less than list. Unused points roll over 1 month, then expire. There are no advances, so a shortfall means staging or a cash top-up (section 3). Unused tweak allowances don't roll over.

Terms:

5. Worked examples

Counts are shown as workflows · system units · AI steps · edge cases, all checked against Build Schedule PS-BUILD-2026-11-15-v1. Days are business days.

Before go-live: pricing and dates (nothing billed beyond the first milestone, so the build total = the scope value)

Before go-live: removal, then adding it back (L 6·6·3·12 = $21,000, milestones 30/30/30/10)

After go-live: pricing, points and dates (approval is on day 0)

Minor tweaks (definition in section 2)

Who pays (S build, 14-day support window)