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
| Defect (our implementation is wrong, including failing to send an unhandled case to human review) | Free for 90 days after go-live, whatever the fix takes |
| Upkeep (an outside system changed after acceptance) | Free in the support window (S: 14 days, M/L: 30 days), then a plan covers it or it costs $400 per incident |
| Change before go-live | Recount the scope against Build Schedule PS-BUILD-2026-11-15-v1 and pay the difference. There are no refunds of paid amounts, and nothing is charged twice |
| Change after go-live | Unit list, or a stand-alone Build Schedule PS-BUILD-2026-11-15-v1 quote if that's lower |
| Change-order fee | $250 on any order that adds or rebuilds a unit. None on tweaks or removals, and none on Improve |
| Minor tweaks (a value edit inside an existing unit, see section 2) | 3 free from build start to the end of the support window. Then Keep includes 2/mo and Improve 4/mo. Beyond that, $250 (or 1 point on Improve), with no fee |
| Plans | Keep from $350/mo · Improve from $1,100/mo · 3-month minimum |
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):
- 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.
- 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.
- 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):
| What the fix needs | Support window | Window end → day 90 | After day 90 |
|---|---|---|---|
| Defect, no unit rebuilt | Free | Free | Keep/Improve: included · No plan: $400 |
| Defect, unit rebuilt | Free | Free | Keep/Improve: included · No plan: rework at list only (diagnosis included, no $400, no fee) |
| Upkeep, same counts, no rebuild (config, credentials, small API tweak) | Free | Keep/Improve: included · No plan: $400 | Same as previous column |
| Upkeep, same counts, unit rebuilt (new API version, successor model) | Free | Keep/Improve: included · No plan: $400 + rework at list, no fee | Same as previous column |
| Upkeep that adds units (vendor drops its API, so the system becomes "no usable API" = +1 unit) | Diagnosis free. Added units are a change: list + $250 | Keep: diagnosis included, added units list + $250 · Improve: diagnosis included, points, no fee · No plan: $400 + list + $250 | Same as previous column |
| New automatic handling of a case | Change (section 2 or 3) | Change | Change |
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:
- Scope value = the Build Schedule PS-BUILD-2026-11-15-v1 build price (place, bump, price) of the charged scope. The charged scope is the current (active) scope plus any held units. A held unit is a unit whose work had started and that was removed without a replacement: started work is never credited, so it stays charged.
- Replaced units are never held. When a started or built unit is swapped for a new unit of the same type (same counts), the old unit leaves the charged scope and its started work is paid once, through rework at list. It is never both held and charged as rework.
- A held unit later gets a same-type replacement (removed in one order, new unit added in a later one): the new unit takes the held unit's slot, the held unit leaves the charged scope, and rework is charged. That gives the same price as a single swap order.
- The same unit added back: the held unit becomes active again and its work resumes, with no rework.
- Billed = the build milestones invoiced so far. Paid amounts are never refunded.
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:
- 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).
- 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.
- 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:
- (a) a held unit (started work removed without replacement) stays charged, unless the client adds it back (no rework) or replaces it (rework instead of holding);
- (b) if billed already exceeds the scope value, the build total stays at billed. There are no refunds, and that money counts toward any later additions, so nothing is charged twice.
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):
- Unit not started: $250 fee only. Work days = the new unit's days − the old unit's planned days, so a same-type swap adds 0 days.
- Unit started or built: rework at list + $250 fee. The replaced unit is not held, so the charged scope = the active scope and the build total doesn't move. Work days = the unit's days, because the built work can't be subtracted.
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.
- Tweaks: message, email or alert wording; prompt wording that keeps the same output fields and decisions; a threshold or limit; a schedule or time; recipients or alert channel inside an already-connected system; field mapping between fields the build already reads and writes; labels and category names.
- Not tweaks (count-neutral change, or an added unit): swapping a system or account type; a new field to extract or a new decision for an AI step; a new branch or rule path; a new source or destination; anything that needs new test cases.
- Price and date (before and after go-live): within the allowance (3 free from build start to the end of the support window, then 2/mo on Keep or 4/mo on Improve), free. Beyond that, $250 (1 point on Improve), never with a fee. Each tweak takes 1 work day: before go-live it moves go-live +1; after go-live, delivery = start + 1.
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.
| Unit added or rebuilt | Price | Work days |
|---|---|---|
| Workflow | $3,000 | 5 |
| System unit (no usable API = 2 units) | $1,500 | 3 per unit |
| AI step | $1,500 | 3 |
| Edge cases | $1,000 per started block of 5, counted cumulatively since go-live | 2 per started block of 5 in this order |
| Minor tweak (after the allowance) | $250 or 1 point, no fee | 1 |
- Order price = list lines + $250 fee if a unit is added or rebuilt. Improve pays in points with no fee. Tweak-only orders carry no fee.
- Pricing blocks versus work days: price uses the running total since go-live, so five +1 requests cost $1,000 in total. Work days count this order only, so each +1 order takes 2 days and the five together take 10 if sent separately.
- Stand-alone option: an order that adds a workflow is also placed as its own Build Schedule PS-BUILD-2026-11-15-v1 project. Its 4 counts are the new workflows, every system unit they touch (existing and new), their AI steps and their edge cases. That project is placed and bumped per Build Schedule PS-BUILD-2026-11-15-v1. The client pays the lower of the two. If the stand-alone quote wins, the work days are the low end of that tier's typical time (S 10, M 20, L 35 business days).
- Billing: 50% on approval and 50% on delivery, or points on Improve.
- Warranty: each delivered change gets its own 90-day defect warranty from its delivery date.
Scheduling (one formula for every order, before or after go-live):
- Work days = the work days of the units the order adds or rebuilds, + 1 per tweak, − the planned days of any unstarted unit it removes or swaps out (section 2), using the table above. If the stand-alone quote wins, use its tier days instead.
- Before go-live: go-live moves by the order's work days. With the Build Schedule PS-BUILD-2026-11-15-v1 rush adder (+25% of the order), the date stays where it was.
- After go-live:
- Start = the latest of: (a) approval + lead time (5 business days, or 2 on Improve); (b) the end of this client's earlier queued orders; (c) on Improve, the date the points are available (now, or the 1st business day of the month that covers them).
- Delivery = start + work days. The quote states both dates.
- Not enough points: Improve clients can either stage the order (the part covered by today's points now, the rest when next month's points arrive) or top up the shortfall in cash at list ($250 per point, no fee) and start now. We don't advance future points.
4. Plans after go-live
Plans start when the tier's support window ends.
| Keep | Improve | |
|---|---|---|
| S build | $350/mo | $1,100/mo |
| M build | $750/mo | $1,875/mo |
| L build | $1,500/mo, or 8% of the final build total if that's higher | Keep + $2,250/mo |
| Monitoring, alerts and the run log watched by us | ✓ | ✓ |
| Defects after day 90, including rebuilds | ✓ | ✓ |
| Upkeep that keeps the counts the same, including rebuilds (API migrations, model swaps) | ✓ | ✓ |
| Upkeep that adds units: diagnosis | ✓ | ✓ |
| Upkeep that adds units: the added units | Cash at list + $250 | Points, no fee |
| AI quality check: the test set is re-run monthly and on every model change (AI builds only) | ✓ | ✓ |
| Minor tweaks | 2/mo, then $250 each | 4/mo, then 1 point each |
| Change points (1 point = $250 at section 3 list) | – | S 4 · M 6 · L 12 per month |
| Lead time (latest start when nothing is queued) | 5 business days | 2 business days |
| Monthly report | Short | Full, plus a 30-min review call |
| Response to a fault (business days) | Critical: same day · Other: next day | Same |
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:
- Billed monthly in advance. 3-month minimum, then cancel any time with 30 days' notice.
- Price held for 12 months. Plan changes take effect next month.
- Not included: AI and infra running costs (on the client's accounts), licences, and new builds (a fresh Build Schedule PS-BUILD-2026-11-15-v1 quote, with 5% off on an active plan).
- No 24/7 on-call. "Critical" means the flow is down or writing wrong data. We pause it, and the human review step catches items in the meantime.
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)
| # | Case | Start → end counts | Build total | Client pays | Go-live |
|---|---|---|---|---|---|
| B1 | Same tier: S adds a second system | 1·1·1·2 → 1·2·1·2 (S) | $3,500 → $3,500 | $250 fee | +3 |
| B2 | S → M: add a workflow | 1·2·1·2 → 2·2·1·2 (M) | $3,500 → $8,000 | $4,500 + $250 | +5 |
| B3 | Then add a system | 2·2·1·2 → 2·3·1·2 (M) | $8,000 → $8,000 | $250 · running total $8,000 = fresh quote, + $500 fees | +3 |
| B4 | Bump: M adds a 4th system | 3·3·1·5 → 3·4·1·5 (2 at top → L) | $8,000 → $18,000 | $10,000 + $250, or phases | +3 |
| B5 | L headroom | 4·5·3·12 → 5·6·3·12 (inside the base) | $18,000 → $18,000 | $250 | +8 (5 + 3) |
| B6 | Past the L base | 5·6·3·12 → 6·6·3·12 | $18,000 → $21,000 | $3,000 + $250 | +5 |
| B7 | Five separate +1 edge-case orders | 5·6·5·20 → 5·6·5·25 | $18,000 → $19,000 (1st order), then unchanged | $1,000 + 5×$250 = $2,250 | +2 per order = +10 |
| B8 | The same five, batched | 5·6·5·20 → 5·6·5·25 | $18,000 → $19,000 | $1,000 + $250 = $1,250 | +2 (1 block) |
| B9 | Replace Xero with QuickBooks, not started | 2·3·1·4 → same | $8,000 → $8,000 | $250 | 0 (+3 new − 3 planned) |
| B10 | Same, Xero part already built | 2·3·1·4 → same (Xero replaced, not held) | $8,000 → $8,000 | $1,500 rework + $250 | +3 |
| B10b | S build: replace a built Xero system with QuickBooks, across the S/M boundary | Active 1·2·1·2 → 1·2·1·2 · Charged 1·2·1·2 (Xero replaced, not held; holding it would make 1·3·1·2 = M) | $3,500 → $3,500 | $1,500 rework + $250 = $1,750 (one quote) | +3 |
| B10c | Same, in 2 orders: remove built Xero, then later add QuickBooks | Order 1: active 1·1·1·2, charged 1·2·1·2 (Xero held) → $3,500, credit $0, no fee · Order 2: QuickBooks takes the held slot, charged 1·2·1·2 | $3,500 → $3,500 | Order 1 $0 · Order 2 $1,500 rework + $250 = same $1,750 | Order 1: 0 (built work can't be subtracted) · Order 2: +3 |
| B11 | M removes an unstarted workflow | 2·3·1·6 → 1·3·1·6 (still M) | $8,000 → $8,000 | $0 credit, no fee | −5 |
Before go-live: removal, then adding it back (L 6·6·3·12 = $21,000, milestones 30/30/30/10)
| # | Step | Scope value | Billed | Build total | Credit / charge | Outstanding | Fees |
|---|---|---|---|---|---|---|---|
| R1 | Full credit: 1 milestone billed. Remove an unstarted workflow | $18,000 | $6,300 | $18,000 | −$3,000 | $11,700 | $0 |
| Add it back | $21,000 | $6,300 | $21,000 | +$3,000 | $14,700 | $250 | |
| Final (all billed) | $21,000 | $21,000 = fresh quote | $0 | $250 | |||
| R2 | Capped credit: 3 milestones billed. Remove an unstarted workflow | $18,000 | $18,900 | $18,900 (billed is higher) | −$2,100 (outstanding to $0, no refund) | $0 | $0 |
| Add it back | $21,000 | $18,900 | $21,000 | +$2,100 (the $900 already paid counts) | $2,100 | $250 | |
| Final | $21,000 | $21,000 = fresh quote, not $21,900 | $0 | $250 | |||
| R2b | Capped, never added back | $18,000 | $18,900 | $18,900 (exception b: no refund of the $900) | $0 | $0 | |
| R3 | Started work: 1 milestone billed. Remove a workflow that's in progress, no replacement | $21,000 (held, still charged) | $6,300 | $21,000 | $0 | $14,700 | $0 |
| Add it back, the work resumes | $21,000 | $6,300 | $21,000 | $0 (already charged) | $14,700 | $250 | |
| Final | $21,000 | $21,000 | $0 | $250 | |||
| R3b | Started work, never added back | $21,000 | $21,000 (exception a) | $0 |
After go-live: pricing, points and dates (approval is on day 0)
| # | Case | Price | Start | Delivery |
|---|---|---|---|---|
| A1 | S, no plan, month 4: add a Slack alert system | $1,500 + $250 = $1,750 (50/50) | Day 5 | Day 8 (3 work days) |
| A2 | M, no plan: a new workflow on 2 existing systems, 1 AI step, 3 edge cases | List $3,000 + $1,500 + $1,000 = $5,500 vs stand-alone 1·2·1·3 (all S) = $3,500 → $3,500 + $250 | Day 5 | Day 15 (S: 10 work days) |
| A3 | M on Improve: five +1 edge-case requests over 3 months | Running total 0→1 starts 1 block = 4 points on the 1st request. The other four cost 0 | 2 days after each approval | +2 work days each |
| A4 | M on Improve: Slack system + 4 edge cases = 10 points, 6 available, no rollover | Stage: system part (6 points) now, edge cases (4 points) next month | System: day 2 · Edge cases: 1st business day of next month | System: day 5 · Edge cases: 2 work days after their start |
| A4b | Same, with a top-up | 6 points + $1,000 cash (4 × $250) | Day 2 | Day 7 (3 + 2) |
| A5 | Keep client, M build. Order X: a new rule-based workflow from the existing CRM and existing Xero into a new Slack system, approved day 0. Order Y: 1 system, approved day 2 | X list: $3,000 + $1,500 = $4,500 vs stand-alone 1·3·0·0 (3 systems → M, not at top) = $8,000 → $4,500 + $250 (8 work days) · Y: $1,500 + $250 (3 days) | X: day 5 · Y: max(day 2 + 5, X ends day 13) = day 13 | X: day 13 · Y: day 16 |
| A6 | L ($27,000 final build total) on Keep | 8% = $2,160/mo | – | – |
Minor tweaks (definition in section 2)
| # | Case | Price |
|---|---|---|
| T0 | S, before go-live: reword the reminder email (1st tweak) | Free, no fee · go-live +1 |
| T0b | S, before go-live: "also extract the PO number" | Not a tweak (new AI output): count-neutral change, AI step not yet built → $250 fee, go-live +0. If the AI step is already built → $1,500 rework + $250, +3 |
| T1 | S, support window day 5: reword the reminder email (2nd tweak since build start) | Free (within the 3) · start by +5, delivered +6 |
| T2 | S, support window day 12: 4th tweak | $250, no fee · start by +5, delivered +6 |
| T3 | Keep, month 5: 3rd tweak this month | $250, no fee |
| T4 | Improve, month 5: 5th tweak this month | 1 point |
Who pays (S build, 14-day support window)
| # | Case | Cause decided by | Category | No plan | Keep | Improve |
|---|---|---|---|---|---|---|
| D1 | Day 10: Xero API change breaks the sync, small fix | Passes on replay | Upkeep, support window | Free | – | – |
| D2 | Day 60: same | Passes on replay | Upkeep | $400 | Included | Included |
| D3 | Day 200: same | Passes on replay | Upkeep | $400 | Included | Included |
| D4 | Day 60: wrong totals on an accepted test invoice, the AI step must be rebuilt | Fails on replay | Defect, warranty | Free | Free | Free |
| D5 | Day 200: a small defect, no rebuild | Fails on replay | Defect | $400 | Included | Included |
| D5b | Day 200: a defect that needs the Xero system unit rebuilt | Fails on replay | Defect, rebuild | $1,500 (rework only) | Included | Included |
| D6 | Day 60: an unhandled invoice type was auto-posted instead of going to review | Fails on replay (routing) | Defect, warranty | Free routing fix. Automatic handling (+1 block) = $1,000 + $250 | Free fix · auto: $1,250 | Free fix · auto: 4 points |
| D7 | Day 10: vendor retired the API version, so replay isn't possible. Notice dated after acceptance, run log shows passes after go-live | Evidence | Upkeep, support window, rebuild | Free | – | – |
| D8 | Day 200: same, rebuild needed | Evidence | Upkeep, rebuild | $400 + $1,500 = $1,900 | Included | Included |
| D9 | Day 200: same, but no dated notice in the evidence | Evidence missing | Defect (benefit of the doubt) | $1,500 (defect rebuild: rework only, unlike D8's upkeep $400 + $1,500) | Included | Included |
| D10 | Day 200: vendor shuts its API, so the system becomes "no usable API" (+1 unit) | Evidence | Upkeep + change | $400 + $1,500 + $250 = $2,150 | Diagnosis included · $1,500 + $250 = $1,750 | Diagnosis included · 6 points, no fee |