Sierra IT Transition · prepared by CWIT Confidential · Prepared for Slade Schiffner
Internal proposal · May 2026

The case for moving Sierra Dental's IT
from iTeam to CWIT.

Three internal audits — the 2022 server-upgrade fiasco, the current monthly invoices, and the iTeam agreements — converge on the same conclusion. Each section below has a quadrant control: pick the length and depth that fits how you want to read it.

$60–90K
Conservative annual recurring savings, 7 clinics
$15–25K
Avoided overpayment per future hardware refresh cycle
12–18 mo
Realistic full-migration timeline, all 7 clinics
Section 1

1The summary, in one read.

Length Depth

The verdict, in one sentence

iTeam isn't committing fraud — they're systematically overcharging across every line item, and the contract makes it hard to push back.

The case for moving comes to roughly $60–90K/year in recurring savings across the seven clinics, plus avoided one-off overcharges on the next hardware refresh. The case against moving comes down to one thing: CWIT is small, iTeam is bigger. The recommendation: pilot one small clinic first, decide from there.

The verdict, in one sentence

iTeam runs a typical reseller-margin-plus-quota MSP model — legally defensible, structurally biased toward vendor revenue maximisation.

Conservative recurring overpayment: $35–55K/year across the four observed clinics, scaling to $60–90K/year across seven. One-off Server Fiasco overpayment: ~$20K. Contract structure (auto-renewal, 90-day invoice deadline, 5% silent annual increase, 50% non-solicit liquidated damages, 25-item out-of-scope exclusion list) makes none of this easy to renegotiate inside the relationship. Recommendation: pilot the smallest clinic on its next contract anniversary; preserve full optionality on solo vs Forbes partnership until evidence justifies the call.

The verdict, plainly stated

iTeam is not committing fraud. They are operating a typical IT-company-with-salespeople model that is professionally drafted, legally defensible, and built to extract maximum revenue from each line on the invoice.

Across the three audits, the conservative estimate of Sierra's annual overpayment on the recurring relationship is $35–55K/year across four observed clinics — which scales to roughly $60–90K/year across the seven-location footprint. The 2022 server-upgrade overpayment was a one-off of about $20K. The contractual lock-in means none of this is easy to renegotiate inside the relationship.

The decision in front of you is not whether iTeam is "ripping us off." It's whether the real, measurable cost of staying outweighs the real, measurable risk of leaving — including the risk that CWIT can't, on its own, fully replace a team of iTeam's size.

What changes if Sierra moves

  • Hardware goes from one-brand markup to commercial-grade parts at distributor cost plus a transparent margin. Server quotes that today cost $35K should run closer to $18K.
  • Hosted backup goes from a very expensive monthly per-GB rate to verified cloud backup at roughly $300/mo for Signal Hill's full capacity.
  • Server warranty goes from "estimated" monthly fees with built-in flexibility upward to fixed-price three-year coverage.
  • Out-of-scope work — the 15-min phone calls, user training, routine small projects — moves inside the monthly plan rather than being billed at $140/hour.
  • Workstations stay roughly the same because of Sierra's existing volume discount with iTeam. The workstation line is not where the savings live.
  • The contract structure flips: no auto-renewal trap, no 90-day invoice deadline, no 50% non-solicit clause, no silent annual increase.

The verdict, with specifics

iTeam is not committing fraud. They are operating a professionally-drafted reseller-margin-plus-quota managed-services model that is legally defensible, structurally biased toward vendor revenue maximisation, and protected by an asymmetrical contract that makes the relationship structurally easier to enter than to leave.

Across the three audits, Sierra's conservative annual recurring overpayment is $35K–55K/year across four observed clinics, scaling to $60K–90K/year across the seven-location footprint. One-off Server Fiasco overpayment in 2022: ~$20K. Hardware refresh markups recur on a 5–7 year cycle at an estimated $15–25K per cycle.

Specific changes on transition

  • Hardware procurement: HPE-locked (with documented 3–5× retail markup on RAM and SSDs) → brand-neutral commercial-grade off-the-shelf at distributor cost + transparent margin. Server quote of $35,843 in 2022 → equivalent Dell build was $18,525 at the time.
  • Hosted backup: $10.40 per 100GB ($104/TB) → Backblaze B2 / Wasabi at $6/TB + CWIT management at flat ~$300/mo for 15TB. Signal Hill saving alone: ~$15K/year.
  • Server warranty: HPE Pointnext / Foundation Care at "estimated $75–$211/mo" (unilaterally adjustable) → CWIT Complete Care at fixed $199/mo per server, 3-year defined term.
  • Reseller software (Sophos, Veeam, Duo, SonicWall, Microsoft): industry-standard reseller margin → distributor cost + 5–10% handling margin.
  • Out-of-scope absorption: $140–$210/hr granular billing → wider routine-work absorption into monthly plan. 15-min RDP question ($37) and "how to" calls move from billable to included.
  • Workstation rate: $43.68/seat (iTeam volume-discounted) → $49/seat (CWIT published). Slight cost-up of ~$5K/year at Signal Hill, offset many times by the other lines.
  • Contract: 60-day non-renewal window + 90-day invoice deadline + 50% non-solicit + 5% silent increase + 25-item exclusion list → 30-day rolling + 12-month invoice window + no non-solicit + CPI-linked adjustment + narrow capital-projects-only exclusions.
Section 2

2What the three audits found.

Length Depth

1 · Server Upgrade Fiasco (2022)

Paid $35,843 for a build that could have been done for $18,525. Net overpay: ~$17–20K, one-off.

2 · Monthly Bills

About $13,205/month, $158K/year across 4 clinics. Conservative annual overpay: $35–55K (4 clinics), $60–90K (7 clinics).

3 · The Agreements

Professionally written, fully legal, uniformly vendor-favourable. Auto-renewal, short dispute window, big non-solicit damages, silent annual increase, long out-of-scope list. Not the rip-off — the legal scaffolding that makes the other two findings sustainable.

1 · Server Fiasco

4 iTeam revisions: ITMQ7234 ($32,847), 7306 ($35,452), 7307 ($40,230), 7332 ($35,843). Dell-equiv: ~$18,525. HPE RAM 3–5× retail. Warranty "estimated $75–$150/mo". Same drive $574 / $840 on same quote. Net overpay: $17–20K.

2 · Monthly Bills

Signal Hill $9,088, Airdrie $1,689, Seton $1,288, SBH $1,140 = $13,205/mo. Overpay lives in: hosted backup ($104/TB vs $6/TB cloud), HPE warranty, reseller software margin, out-of-scope absorption. Workstation $44/seat is volume-discounted — wash with CWIT $49.

3 · Agreements

2 formats (2020 ISSA + Statement of Services). Notable clauses: 60-day non-renewal window; 90-day "conclusively correct" invoice deadline; 5% silent annual increase; 50% liquidated damages on hiring iTeam staff; 25-item out-of-scope exclusion list; "Minimum Requirements" audit-and-bill loop; HPI/HPE procurement anchor; Fair Usage Policy at iTeam's sole discretion.

Audit 1 · Server Upgrade Fiasco (2022)

$35,843 paid; $18,525 was on the table. Four quote revisions from iTeam, all on the same brand of server, with very high markups on RAM and SSDs and a warranty quoted as a monthly "estimate" rather than a fixed price. Pricing inconsistencies even within the same quote.

The pattern: filibustering, manufactured urgency, and relationship leverage applied to discourage Sierra from shopping around. Sierra accepted the iTeam quote in the end partly to keep the broader IT relationship from souring. Net overpayment: about $17–20K on a single transaction.

Audit 2 · Monthly Spend

About $13,205/month, $158K/year across four observed clinics. Signal Hill alone is $9,088/month. No single charge is fraudulent; almost every line sits at the top of competitive market pricing.

The savings on transition don't come from workstations (iTeam already gave Sierra a volume discount there). They come from four other lines: hosted backup pricing, server warranty consolidation, reseller software margin, and the out-of-scope billing that adds up at $140/hour.

Conservative annual overpayment: $35–55K (4 clinics), $60–90K (7 clinics).

Audit 3 · The Agreements

Five executed contracts. Professionally drafted, fully legally defensible, and uniformly written to favour iTeam in every clause where they had a choice: auto-renewal with a tight 60-day notice window, a 90-day deadline to dispute any invoice, a 5% annual increase right with no notice required, a 50% liquidated-damages clause on hiring iTeam staff, and a 25-item list of activities that fall outside the monthly plan and become billable at hourly rates.

The contract isn't the rip-off. It's the legal scaffolding that makes the other two findings sustainable — it's the reason iTeam's pricing sticks and the monthly bill creeps up year after year without effective challenge.

Audit 1 · Server Upgrade Fiasco (2022)

$35,843 paid (ITMQ7332); $18,525 was the like-for-like Dell-equivalent build (per Sean Picard, Titanium Networks). iTeam revisions: ITMQ7234 ($32,847.90), ITMQ7306 ($35,452.63), ITMQ7307 ($40,230.53), ITMQ7332 / -7332-rev1 ($35,843.29).

HPE SmartMemory 32GB DDR4 quoted at $515–$669/stick vs Kingston Server Premier ECC retail at ~$150 (3.4–4.5× markup). HPE 2.4TB SAS drives quoted at $840 vs market ~$300 (2.8×). Same quote priced the same 2.4TB drive at $574.67 on one line and $840 on another.

HPE Pointnext warranty quoted as "ESTIMATED $75/server/mo" (Studio) and "ESTIMATED $150/server/mo" (Centre). Dell ProSupport 4hr mission critical equivalent: ~$50/mo. Up-front pricing only offered when explicitly requested.

Documented pressure tactics include James Wagner's "give them up in a day or so" parts-hold deadline (which silently expired without consequence); Robert Covell's oil-in-engine analogy on third-party parts; the explicit "long-term service relationship" framing as a reason to stop questioning the quote.

Audit 2 · Monthly Spend

$13,205/month, ~$158K/year across the four observed clinics. Composition: Signal Hill $9,088, Airdrie $1,689, Seton $1,288, Springbank Hill $1,140.

Largest line at Signal Hill: workstation management at $43.68/seat × 85 = $3,712.80/mo. This is Sierra's volume-discounted rate; CWIT's published rate is $49/seat. Workstation line is essentially a wash for Sierra.

Where overpayment lives: (a) hosted backup at $10.40/100GB = $104/TB vs Backblaze B2 at $6/TB (~$15K/year saving at Signal Hill); (b) HPE Tech Care warranty at $58–$211/mo replicating the "estimated" structure across all servers (~$6K/year); (c) Sophos/Veeam/Duo/Microsoft reseller margin (~$4.5K/year); (d) out-of-scope absorption (~$20K/year potential).

Out-of-scope sample (5 invoices, 3-week window): $36.75 for 0.25hr remote support (15-min call), $1,355 for a Lenovo workstation, $7,497 for Exchange migration (49 staff hrs @ $140–$210/hr), $1,340 × 2 for Microsoft Office 2024 licenses ($319/seat vs ~$249 retail).

Net conservative annual saving on transition: $35–55K (4 clinics), $60–90K (7 clinics).

Audit 3 · The Agreements

Five contracts on file: two SBH (2019 ISSA + 2020 ISSA), Seton (Statement of Services + CompleteCare), Chinook Dental Group (SoS + CompleteCare), SDP. Two structural formats: short 2-page Information Systems Services Agreement (early SBH) and the longer 10+ page Statement of Services format (newer clinics).

Auto-renewal: 12-month auto-renew with 60-day non-renewal notice (SBH) or "contiguous terms equal to initial Service Term" (SoS) — miss the window and you renew for another full term.

Invoice disputes: "conclusively true and correct" after 90 days (SBH clause 5).

Annual increases: Up to 5% with no notice; above 5% triggers 60-day terminate-or-accept (SoS Increases section).

Non-solicitation: 12-month restriction on hiring former iTeam staff; 50% of fees/gross income as liquidated damages on breach (SBH clause 11).

Out-of-scope exclusion list: 25 categories including "Projects," mass installs (>3 machines), hardware repairs, "How to" training, mobile OS upgrades, OU/GPO changes, SharePoint, cabling, UPS battery replacement, equipment relocation, "the cost to bring the Environment up to the Minimum Requirements."

Procurement: "The ITeam is a warranty service provider for limited product lines from HPI and HPE" — explicit brand anchor.

Fair Usage Policy: "excessive" defined at iTeam's sole discretion.

Termination paths: 30-day for non-performance + 90-day no-cause (SBH); SoS relies primarily on renewal-window mechanic.

Section 3

3Contest iTeam now — while you still can.

Length Depth

The contract gives Sierra 90 days to dispute any invoice — and Sierra has never used that right. Whatever Sierra decides about transitioning, the tool below builds a professional email that puts iTeam on notice on specific items. Even if Sierra stays, this resets the relationship to "watched" instead of "trusted."

SBH ISSA clause 5 ("conclusively true and correct 90 days following rendering thereof"): any invoice older than 90 days is deemed binding. The tool below generates a written dispute that preserves Sierra's rights on specific items within that window. Raising specific issues now also affects pricing posture at next renewal.

What "contesting" looks like

The contract says any invoice older than 90 days is binding — so anything Sierra wants to push back on needs to be raised in writing within that window. Raising specific, documented issues early signals to iTeam that the relationship is being scrutinised, which historically results in (a) more accommodating pricing on the next renewal, (b) more carefully-scoped out-of-scope billing, and (c) a more collaborative tone on the next major project. Even if Sierra ultimately stays, contesting now improves the terms.

The tool below builds an email Sierra can send this week. Pick the issues, pick the tone, copy or open in your mail app.

The legal context

Under SBH ISSA clause 5, invoices and statements "shall be conclusively be deemed to be true and correct 90 days following rendering thereof, unless [client] takes written exception thereto within the said 90 days and makes claim to TheITeam Ltd. for adjustment." The Seton/CDG SoS does not include identical language but does include the 5% silent annual increase and the Fair Usage Policy as iTeam's discretion levers.

Strategic effect of formally contesting within the 90-day window: (a) preserves Sierra's right to claim adjustment / credit on specific line items; (b) creates a documented record before any future termination decision; (c) signals that the relationship is being audited, which empirically shifts pricing posture at next renewal by 10–20%; (d) gives Sierra grounds for the 30-day non-performance termination clause if iTeam fails to respond constructively. Even absent transition, this is a 10–20% lever on go-forward economics.

Build the email

Pick the issues you want to raise. The email body on the right updates live.

Email preview

To:
Subject:
Pick at least one issue on the left to generate the email body.
Open in mail app

Tip: copy Dmitry on the send. The audit trail + copied-to-management dynamic elicits faster replies from iTeam.

Section 4

4The transition plan.

Length Depth

The contracts auto-renew with 60-day notice. Plan: pilot the smallest clinic first, Signal Hill last, spread across 12–18 months. Each clinic: ~12 weeks from notice to cut-over.

MonthsWhat happens
1–3Smallest clinic — proves the playbook
3–6Second small clinic — validates
6–9Two mid-sized clinics in parallel
9–12Signal Hill (largest, most complex)
12–18Long tail

Two contractual termination paths: 60-day non-renewal notice (clean, anchored to anniversary) or 90-day no-cause termination (any time, 3 months overlap cost). Migration sequence: smallest first, Signal Hill last.

Clinic / ContractOriginal effectiveRenewal cadenceNotice required
SBH (1st ISSA)Feb 1, 202012-mo auto-renew60 days before Feb 1
SBH (2nd ISSA)Apr 1, 202012-mo auto-renew60 days before Apr 1
Seton (SoS)per quote=initial term60 days before anniv.
Chinook DG (SoS)per quote=initial term60 days before anniv.
SDPper quoteper quoteconfirm w/ iTeam

The iTeam agreements auto-renew with 60-day notice. The plan below is anchored to those dates and designed so Sierra de-risks the migration by starting small and ending big.

Two ways out of an iTeam contract

  • Non-renewal (clean): serve written notice 60 days before the anniversary; the contract simply doesn't renew.
  • No-cause termination (any time): 90-day written notice, no reason required. Costs 3 months of vendor overlap.

For most clinics, the right path is non-renewal — wait for the next anniversary, give notice, transition cleanly. For one or two clinics where the anniversary is far off, the 90-day no-cause path may be worth ~$3K of overlap cost to capture a permanent ~$5K/year saving.

Typical clinic migration, week-by-week

  1. Week −12 to −10
    Discovery and inventory. CWIT audits the clinic: workstations, servers, switches, backup state, software stack. Output: a single document Sierra owns.
  2. Week −9 to −8
    Hardware sufficiency review. CWIT confirms whether existing gear is good for another 3–5 years or whether a refresh should happen during migration.
  3. Week −6 to −4
    Service notice to iTeam. Written non-renewal (or 90-day termination) sent.
  4. Week −4 to −1
    Parallel infrastructure stand-up. CWIT provisions monitoring, backup, security alongside iTeam's. This is the overlap-cost period.
  5. Cut-over weekend
    Cut-over. After-hours. Backup verified before iTeam access is revoked.
  6. Week +1 to +2
    Post-cut hardening. Residual agents removed; iTeam-owned equipment returned within 10-day window; two backup cycles verified.
  7. Week +4
    Final reconciliation. Any 90-day-window disputes pushed for resolution. Final iTeam invoice paid.

The 12-18 month sequence

MonthsClinicWhy this order
1–3Smallest, nearest anniversaryLow-risk first migration. Operational muscle on a non-critical clinic.
3–6Second small clinicRefines the playbook.
6–9Two mid-sized clinics in parallelTests parallel-migration capacity.
9–12Signal HillThe hardest one last, with three completed migrations of learning.
12–18Remaining clinicsLong tail. Operationally proven by this point.

Migration plan anchored to actual contract anniversaries with a clinic-by-clinic Commencement Date. Two termination paths available under the agreements; non-renewal preferred where the calendar allows.

Contract calendar (from the agreements on file)

Clinic / ContractOriginal effectiveRenewal cadenceNon-renewal notice required
Springbank Hill (1st ISSA)Feb 1, 202012-month auto-renew (clause 2)60 days before each Feb 1
Springbank Hill (2nd ISSA)Apr 1, 202012-month auto-renew60 days before each Apr 1
Seton (Statement of Services)Per quote Commencement DateTerm equal to initial term60 days before each anniversary
Chinook Dental Group (SoS)Per quote Commencement DateTerm equal to initial term60 days before each anniversary
SDPPer quote Commencement DatePer quoteConfirm with iTeam

Action: pull the executed quote/SoS for each clinic to confirm Commencement Date — the anchor for renewal anniversary calculations.

Termination paths

  • Non-renewal (preferred): 60-day written notice before anniversary date. Zero overlap cost. Per SBH ISSA clause 2.
  • No-cause termination: 90-day notice (SBH ISSA clause 3) without need for performance grounds. ~3 months of dual-vendor overlap cost; worth it for clinics where annual savings exceed 4× overlap.
  • For-cause termination: 30-day notice on documented non-performance. Risk: factual dispute about whether grounds are met.

Typical clinic migration runbook

  1. Week −12 to −10
    Joint discovery and inventory. Workstation count and specs, server hardware/OS/VM topology, switch model and config, firewall rules, backup state (verified vs unverified), software stack with license assignment, M365 tenant ownership, cloud service account ownership map. Output: single Sierra-owned inventory document.
  2. Week −9 to −8
    Hardware sufficiency review. CWIT runs the clinic's existing hardware against 5-year viability criteria. Recommendation: keep, refresh during migration, or refresh after migration. Refresh quotes per CWIT published pricing — no HPE lock-in.
  3. Week −7 to −6
    Backup pre-stage. CWIT stands up parallel backup infrastructure (e.g., Backblaze B2 with Veeam orchestration) and runs first verified replication before any notice is served.
  4. Week −6 to −4
    Service notice to iTeam. Written non-renewal (or 90-day no-cause termination per clause 3) sent to James Wagner with copies to Accounts. Notice cites specific contract clause invoked. Tone: cordial, factual, no grievance language.
  5. Week −4 to −1
    Parallel infrastructure stand-up. Monitoring agent rollout (CWIT preferred RMM), endpoint security stack swap (Sophos → SentinelOne or equivalent CWIT preferred), MFA migration (Duo → Entra MFA where applicable), DNS/firewall config audit.
  6. Cut-over weekend
    Cut-over. After-hours window. Sequence: verify backup → revoke iTeam admin credentials → activate CWIT remote access → verify all clinic systems pre-Monday open. Sierra holds admin credentials throughout.
  7. Week +1 to +2
    Post-cut hardening. Remove residual iTeam software agents (per SoS Removal clause; CWIT to document removal); return iTeam-owned hardware within 10-day SoS window; confirm 2 successful backup cycles + 1 successful recovery dry-run.
  8. Week +4
    Final reconciliation. Any 90-day-window disputes pushed for resolution per ISSA clause 5. Final iTeam invoice reconciled and paid on time to avoid 18%/yr interest. M365 tenant ownership confirmed in Sierra name; domain registrar account confirmed in Sierra name.

Indicative 12–18 month sequence

MonthsClinicRationale
1–3Smallest clinic w/ nearest anniversaryLowest-risk pilot. CWIT builds operational muscle on a non-critical site before tackling Signal Hill.
3–6Second small clinicValidates and refines the runbook. Independent confirmation that the playbook generalises.
6–9Two mid-sized in parallelTests CWIT capacity to run two concurrent migrations. Decision point on Forbes partnership if bandwidth tight.
9–12Signal HillLargest, most complex (85 ws, 5 VMs, 2 VMware hosts, 15TB backup). Three completed migrations of accumulated learning. Highest-risk migration deferred to maximum-readiness point.
12–18Remaining clinicsLong tail. CWIT operationally proven on Sierra stack by this point.

Principle: small and easy first; Signal Hill last. Migration risk concentrates where users and infrastructure concentrate. Take the highest-risk migration after the playbook is proven.

Section 5

5Two execution scenarios.

Length Depth

A · CWIT Solo

Lower cost, higher CWIT execution risk. CWIT does everything. Sierra captures full savings.

Best if: pilot proves CWIT can handle the workload.

B · CWIT + Forbes

Higher coverage, shared margin. CWIT runs the relationship; Forbes adds capacity. Sierra savings unchanged; CWIT margin reduced.

Best if: simultaneous migration of multiple clinics overloads two CWIT techs.

Recommendation: Start solo. Bring Forbes in only if month-6 reality requires it.

A · CWIT Solo

CWIT primary on all 7 clinics. Zeph + Dean as senior techs. Sierra captures $60–90K/yr recurring savings at full margin to CWIT. Risk: 2-tech operation under concentration load (Sierra + 142 existing CWIT clients).

B · CWIT + Forbes IT

CWIT primary contact, billing, accountability. Forbes (BC, 450+ dental clients) provides backup capacity. ~30–40% margin share to Forbes for work covered. Migration cadence: 10–12 months (vs 12–18 solo). No geographic overlap.

Recommendation: Solo to start; introduce Forbes operationally if month-6 evidence shows load constraint. Forbes MOU at modest retainer (~$1,500/mo surge availability) as risk hedge regardless.

Scenario A — CWIT Solo

Lower cost, higher CWIT execution risk.

CWIT runs the entire 7-clinic transition with Zeph and Dean as the on-site team.

Pros:

  • Cleanest financial model — savings flow fully to Sierra, full margin stays with CWIT.
  • Single point of accountability.
  • Estimated net annual saving: $60–90K recurring.

Risks:

  • Two-senior-tech operation. Concentration risk if Zeph or Dean unavailable.
  • Migration may stretch to 18 months to protect existing CWIT clients.
  • Sierra carries vendor-concentration exposure.

Scenario B — CWIT + Forbes IT partnership

Higher coverage, shared margin.

CWIT remains Sierra's primary relationship. Forbes IT provides backup capacity.

Pros:

  • ~600 dental practices of combined specialty depth.
  • Coverage redundancy — Sierra never exposed to both CWIT techs unavailable.
  • Migration cadence faster (10–12 months).

Tradeoffs:

  • Margin split (Sierra's savings unchanged; CWIT margin reduced).
  • Two firms = more coordination overhead.

Recommendation

Start solo. Add Forbes if and when the workload demands it. The pilot is small enough that solo execution is safe; mid-migration is when Forbes becomes valuable if needed.

Scenario A — CWIT Solo

Lower cost, higher CWIT execution risk.

CWIT runs the entire 7-clinic transition with Zeph and Dean as the senior tech complement, with Sierra contributing internal IT bandwidth (Dmitry) for project oversight.

Financial:

  • Sierra net annual saving: $60–90K recurring (4-clinic observed → 7-clinic extrapolated).
  • One-off hardware refresh saving: ~$15–25K per cycle.
  • CWIT margin at Sierra steady-state: healthy — sufficient to fund 1 additional senior tech hire within first 12 months, second within 24.

Operational risk:

  • Two-senior-tech operation. Vacation / illness simultaneous unavailability = real bandwidth shock.
  • Sierra (7 clinics) + existing CWIT base (142 clinics) = load concentration.
  • Migration cadence likely 12–18 months to protect existing CWIT client SLAs.
  • Sierra carries vendor-concentration risk: key-person departure at CWIT would expose Sierra acutely.

Scenario B — CWIT + Forbes IT partnership

Higher coverage, shared margin.

CWIT remains primary contact, billing, and accountability point. Forbes IT (BC, ~450 dental practices, AI security stack, 24/7 monitoring infrastructure) provides backup on-site capacity, after-hours coverage, and surge support during migration. No territorial overlap.

Financial:

  • Sierra net annual saving: $60–90K (unchanged from solo scenario).
  • CWIT margin share: ~30–40% to Forbes for covered work, reducing CWIT net to ~60–70% of solo scenario margin.
  • Forbes brings AI security tooling and 24/7 monitoring infra CWIT would otherwise build.

Operational benefits:

  • Combined depth ~600 dental practices.
  • Coverage redundancy — Sierra never has both CWIT techs unavailable.
  • Migration cadence faster — 10–12 months realistic.

Tradeoffs:

  • Two-firm coordination overhead — requires clear RACI on every system.
  • Sierra patient data custody remains with CWIT primary infra (Forbes provides labour + tooling, not data custody).

Recommendation

Start solo; introduce Forbes operationally if bandwidth load requires it.

The solo path is financially optimal for both Sierra and CWIT, and the migration plan (small first, Signal Hill last) is specifically structured to let CWIT prove operational capacity before Signal Hill's complexity hits. Decision point on Forbes activation: month 6, after two completed clinic migrations.

Irrespective of solo vs partnership for active migration work, recommend an MOU with Forbes for emergency continuity coverage at modest retainer (~$1,500/mo surge availability). This costs ~$18K/year against $60–90K annual savings, hedges the key-person risk specifically, and signals to Sierra that the "one-man show" risk is being actively managed.

Section 6

6The "CWIT is a one-man show" concern.

Length Depth

This is the strongest argument for staying with iTeam. CWIT is two senior techs. iTeam has 15+ staff. Sierra's IT depends on coverage if Zeph or Dean is sick or on vacation.

Five mitigations make the risk manageable: (1) Sierra owns the runbook; (2) Sierra holds all admin credentials; (3) backup is in a non-CWIT-controlled location; (4) Forbes MOU for emergency coverage; (5) quarterly "could-anyone-else-step-in" review. Cost: essentially zero. Effect: turns existential risk into manageable risk.

Real risk: 2-senior-tech operation supporting Sierra (7 clinics, ~100 endpoints) + existing CWIT base (142 practices). Single-point-of-failure if both senior techs unavailable simultaneously.

Mitigations: (1) Sierra-owned runbook stored in Sierra document store; (2) Sierra-held DA credentials with break-glass procedure; (3) backup target outside CWIT operational control; (4) Forbes IT operational MOU ($1.5K/mo retainer for 48hr surge); (5) quarterly third-party-readability audit. Net effect: key-person risk reduced from existential to operational; financial case unaffected.

The honest version of the concern

iTeam fields a team of ~15–20 staff: James Wagner, Austin Southerland, Robert Covell, Scott Surridge, plus engineers (Dave Harker, Gavin Ostlund, Taylor Covell, etc.) who appear on Sierra's invoices.

CWIT is, at the time of this proposal, Zeph and Dean — two senior techs. If Sierra moves and one of them is sick, on vacation, or leaves, the practical bandwidth available to Sierra drops by 50% overnight.

That is a real risk, and Sierra is right to weigh it.

The honest answer

Sierra would be CWIT's ~5th–6th largest account. With Sierra, CWIT becomes profitable enough to hire a third senior tech inside 12 months and a fourth within 24.

Forbes IT provides immediate backup during build-up. Forbes MOU at modest retainer (~$1.5K/mo) gives Sierra a real continuity guarantee.

The thing iTeam has today: warm bodies. The thing CWIT has today and will always have: aligned incentives.

Specific mitigations Sierra should require

  1. Sierra owns the runbook. Stored in Sierra's document store, not CWIT's. Hand to anyone if CWIT becomes unavailable.
  2. Sierra holds all admin credentials. Sierra's password manager, Sierra's DA accounts. CWIT operates under Sierra credentials.
  3. Backup verified to a non-CWIT-controlled location. Restore from anywhere if needed.
  4. Forbes IT operational MOU. Written agreement that Forbes will step in within 48 hours of a CWIT continuity event.
  5. Quarterly "could-anyone-else-step-in" check. Dmitry (or third party) opens the runbook and confirms it's current.

These five mitigations cost essentially nothing. They turn the "one-man show" risk from existential into manageable.

The risk, quantified

Staff complement comparison:

  • iTeam: ~15–20 visible staff including James Wagner (President), Austin Southerland (Sales Mgr), Robert Covell (Service Mgr), Scott Surridge, plus billed-engineer roster (Dave Harker, Gavin Ostlund, Taylor Covell, et al.).
  • CWIT: 2 senior techs (Zeph, Dean) at time of proposal.

Sierra workload: 7 clinics, ~100 endpoints, ~15 servers/VMs, 15TB+ replicated backup. Combined with CWIT's existing 142-practice base, this is real load concentration.

Specific risk vectors:

  • Simultaneous Zeph + Dean unavailability (illness, vacation, departure).
  • Key-person departure exposing institutional knowledge gap.
  • CWIT delivery quality degradation under concentrated load.

The risk-mitigation case

Financial profile change with Sierra onboarded:

  • Sierra becomes ~5th–6th largest CWIT account.
  • Recurring revenue uplift sufficient to fund 1 additional senior tech hire within 12 months, 2nd within 24.
  • Forbes IT operational MOU at ~$1,500/mo retainer for 48-hour surge availability — costs ~$18K/yr against $60–90K/yr savings.

Net: short-term risk real; medium-term risk reduces to manageable as headcount scales.

Required mitigations (Sierra contractually mandates)

  1. Sierra-owned runbook with quarterly maintenance. Document store under Sierra control (M365 SharePoint or equivalent). Quarterly maintenance schedule baked into MSA. Defined "third-party-readability" test: any external IT firm can stand up Sierra's operational baseline from runbook alone.
  2. Sierra holds all DA credentials. Sierra's enterprise password manager (1Password Business / Bitwarden / Keeper). CWIT operates under Sierra-owned credentials with logged break-glass procedure. No iTeam-style "iTeam holds the keys" model.
  3. Backup outside CWIT custody. Backblaze B2 / Wasabi / Azure account in Sierra's billing relationship, not CWIT's. CWIT has operational access; account ownership stays with Sierra.
  4. Forbes IT operational MOU. Written memorandum: Forbes commits to 48-hour surge availability at pre-agreed rates in the event of CWIT continuity issue. Cost: ~$1.5K/mo retainer. Triggered by defined events (CWIT >5 day unavailable, key-person departure, etc.).
  5. Quarterly third-party-readability audit. Once/quarter, Sierra (Dmitry or external) opens the runbook and confirms currency. Formal output: pass/fail report archived in Sierra document store.

These mitigations are budgeted at ~$20K/yr (Forbes MOU + occasional audit costs), against $60–90K/yr in realised savings. Net positive financial case preserved while transferring key-person risk from existential to operational tier.

Section 7

7What you'd actually be deciding.

Length Depth

Three decisions, not one.

  1. Contest current iTeam billing now. Email tool above. Zero cost.
  2. Pilot one small clinic with CWIT. ~$3K of overlap cost; full optionality preserved.
  3. Decide solo vs Forbes after the pilot. Don't pre-commit.

The pilot is the path with the most asymmetric upside. Costs ~$3K if CWIT can't deliver. Frees $60–90K/year if CWIT can.

Three discrete decisions with separable risk profiles.

  1. Contest: exercise 90-day dispute right on specific items. Cost: zero. Effect: 10–20% pricing posture shift at next renewal even if Sierra stays.
  2. Pilot: 1 small clinic via 90-day no-cause termination. Cost: ~$3K overlap. Output: empirical evidence on CWIT operational capacity on Sierra stack.
  3. Scale decision: solo vs Forbes-partnered. Triggered by pilot outcome at month 3–4. Default: solo.

Asymmetric payoff: max loss ~$3K (1 failed pilot migration); max gain $60–90K/yr recurring × 5 years = $300–450K NPV. Preserved optionality at every stage.

Three discrete decisions, not one. Each can be made independently of the others.

  1. Contest current iTeam billing now, regardless. The email tool in Section 3 lets Sierra raise specific, documented issues this week. This costs nothing and improves the terms whether Sierra stays or moves.
  2. Approve a pilot migration of one small clinic to CWIT. Target a clinic whose contract anniversary lets the move happen inside 90 days. The lowest-stakes way to validate CWIT's execution on Sierra's stack. Investment: 1–2 weeks of Dmitry's project oversight + ~$3K overlap cost.
  3. Decide solo vs partnership after the pilot. The right time to make the CWIT-solo vs CWIT-Forbes call is when there's evidence from one completed migration. Until then, both options remain open.

The decision framework, condensed

If Sierra does nothing: ~$60–90K/year in continued overpayment, indefinite contractual lock-in, and a structural relationship that has demonstrated it will resort to filibustering and urgency-manufacturing when challenged.

If Sierra contests but stays: probably 10–20% improvement on terms. Still leaves $40–70K/year on the table relative to a true competitive market price.

If Sierra pilots one clinic: low risk, high evidence value, full optionality preserved. The cost of being wrong is ~$3K; the cost of being right is ~$60–90K/year captured.

The pilot is the path with the most asymmetric upside. It costs almost nothing if CWIT can't deliver. It frees $60K+/year if CWIT can.

Conflict-of-interest note: This document was prepared by CWIT, which benefits financially if Sierra moves. The numbers are built from iTeam's own invoices, contracts, and email correspondence — independently verifiable against source documents.

Three discrete decisions with separable risk profiles, sequenceable so that each subsequent decision benefits from evidence collected by the prior one.

  1. Contest current iTeam billing under the 90-day dispute window. Use the email tool in Section 3 to raise the workstation, backup, warranty, out-of-scope, hardware, software, and contract-clarity items in writing. Cost: zero. Outputs: (a) written record preserving Sierra's right under ISSA clause 5; (b) 10–20% pricing posture shift at next renewal even if Sierra stays; (c) signals scrutiny which historically improves subsequent billing accuracy.
  2. Pilot one small clinic to CWIT via 90-day no-cause termination. Target the smallest clinic with the most favourable termination calendar. Cost: ~$3K overlap (3 months of dual-vendor billing at ~$1K/mo). Outputs: empirical evidence on CWIT's operational capacity on Sierra's specific stack (PMS configuration, network topology, security tooling); validated migration runbook; updated estimates for the remaining 6 clinics.
  3. Scale decision: CWIT solo vs CWIT + Forbes partnership. Trigger: pilot complete (month 3–4). Decision criteria: (a) CWIT load capacity demonstrated; (b) Sierra-CWIT operational fit demonstrated; (c) Forbes operational MOU in place regardless. Default: solo with Forbes MOU. Override to active partnership only if pilot reveals load constraint.

Decision framework, expected-value form

PathYear 1 costYear 1+ recurring5-yr NPV est.
Do nothing$0$0 saved$0
Contest only$0$15–30K saved$60–120K
Pilot one clinic$3K$8–15K saved (1 clinic)$35–70K
Pilot + scale (12–18mo)$15K total overlap$60–90K saved$285–435K

Maximum information value per dollar spent is in the pilot. ~$3K buys empirical answer to the key uncertainty (CWIT operational fit). Either it confirms scale-up worth ~$300K NPV, or it tells Sierra to stay and capture the Contest-only $60–120K NPV. Both outcomes are net positive.

Conflict-of-interest disclosure: This document was prepared by Calgary Wide IT, which would benefit financially if Sierra Dental transitions away from iTeam. The numbers herein are built from iTeam's own invoices, contracts, and email correspondence (source documents on file). Dmitry has internal authority to validate any figure here against source documents. The recommended sequencing (contest → pilot → scale) is structured to preserve Sierra's optionality at every stage and minimise the cost of error in either direction.