Solanasis Docs

solanasis_fractional_retainer_playbook_handoff_2026-03-18

30 min read

Solanasis Fractional Retainer, Billing, Pricing, and Scope-Control Playbook

Research-grade extraction, verification pass, and AI handoff artifact
Created: 2026-03-18
Scope of source discussion: This artifact extracts and improves the current conversation about retainers, fractional COO/CIO positioning, billing, pricing, scope control, and how Solanasis should protect margin while increasing recurring revenue.

How to use this artifact

This document is not a light summary. It is a structured operating memo for a founder, operator, salesperson, legal drafter, pricing strategist, or another AI that needs to continue the work without the original chat.

Each important point is labeled as one of the following:

  • Verified — supported by a cited source, usually official or primary where possible.
  • User-stated — stated by Dmitri or available from project context, but not externally verified in this artifact.
  • Assistant-stated but unverified — recommendation or claim made in the discussion that was not fully verified, or where only weak market evidence exists.
  • Tentative / speculative — a proposed model, synthesis, or strategy that may be smart, but still needs market validation or legal review.

1. Executive Brief

User-stated: Solanasis is a new fractional CIO/CISO/COO-style consulting firm in Boulder, Colorado, focused on SMBs and nonprofits, with services including cybersecurity assessments, disaster recovery verification, data migrations, CRM setup, systems integration, and responsible AI implementation. The user wants the business to maximize recurring revenue while staying premium, lean, and protected from scope creep.

User-stated: The user wants a commercial model that avoids getting dragged into underpriced work, avoids excessive one-off project planning, protects a minimum effective floor of $250/hour, and still gives clients ways to buy additional help when they genuinely need more.

Assistant-stated but unverified: The central commercial answer from the discussion is that Solanasis should not sell pure hourly work and should not sell vague unlimited retainers. The recommended sweet spot is a value-positioned retainer with tightly bounded capacity, pre-priced expansion layers, and major-project SOWs only when truly necessary.

Verified: Current Stripe documentation supports automatic subscription charging, first-invoice incomplete states, manual invoicing, default payment methods, failed-payment emails, retry logic, and both card and ACH collection methods. That makes it viable for Solanasis to require prepayment before monthly service begins, especially for SMB clients using cards.
Evidence: Stripe subscription overview, Stripe collection methods, Stripe pricing, Stripe Billing pricing, Stripe automatic collection.

Verified: Umbrex’s current fractional executive playbooks explicitly recommend guardrails such as change-order thresholds, hour-cap alerts, strategic-time ratios, signed charters, decision-rights clarity, and renegotiation when the engagement drifts materially from plan.
Evidence: Fractional COO Playbook, Fractional CIO Playbook, Fractional CEO / Interim CEO Playbook, Understanding the Fractional Executive Model.

Verified: The economics argument for “fractional vs full-time” is directionally real. BLS reports that median annual pay for computer and information systems managers was 32.37/hour wages + $13.68/hour benefits in September 2025, which means benefits add substantial cost beyond wages. This is not a perfect proxy for a full-time CIO/COO, but it strongly supports the argument that a full-time executive hire carries materially more fixed cost than salary alone.
Evidence: BLS Occupational Outlook Handbook — Computer and Information Systems Managers, BLS Employer Costs for Employee Compensation — September 2025.

2. Context, Goals, Constraints, and Preferences

2.1 Core business context

  • User-stated: Solanasis is trying to operate as a premium, high-trust, founder-led fractional firm rather than a commodity MSP or generic “help with whatever” consulting shop.
  • User-stated: Solanasis wants to maximize recurring revenue, not just one-off projects.
  • User-stated: The business wants pricing that filters out low-quality buyers and avoids clients who consume disproportionate time and attention.
  • User-stated: The business wants a model that works for organizations of different sizes and needs without becoming too cheap or too custom.
  • User-stated: The user wants to avoid falling below an effective floor of $250/hour.
  • User-stated: The user wants to avoid doing bespoke project planning every time a client needs more work.
  • User-stated: The firm needs a structure where clients can “step up” into more help or a higher level of service when needed.

2.2 Operating constraints implied by the discussion

  • Assistant-stated but unverified: Solanasis appears to be lean and founder-led, which means capacity is scarce, context switching is expensive, and over-promising would quickly damage both margin and execution quality.
  • Assistant-stated but unverified: Because Solanasis spans technology, operations, security, and vendor/process cleanup, it is especially vulnerable to becoming a catch-all “miscellaneous executive labor” provider unless the commercial model is disciplined.
  • User-stated: The user wants this to feel like an unusually strong value to the buyer, especially relative to a full-time employee, while still requiring payment up front.

2.3 User communication preferences relevant to future work

  • User-stated: The user prefers downloadable Markdown artifacts for complex strategic work and handoff workflows.
  • User-stated: The user prefers practical, thorough, clearly structured material that another AI can continue without ambiguity.
  • User-stated: The user wants explicit separation of verified facts, recommendations, weak claims, and open questions.

3. Material Claim Audit

This section audits the most important claims made during the discussion.

3.1 Billing and payment-processing claims

Claim: Solanasis can use Stripe so clients prepay before the month begins.

  • Status: Verified
  • Assessment: Stripe supports recurring subscriptions, automatic charging of a saved payment method, and manual invoicing. When using collection_method=charge_automatically, the first invoice is finalized as part of subscription creation, and payment behavior settings can leave the subscription incomplete until payment succeeds.
  • Why it matters: Solanasis can structure retainers so service does not begin until payment succeeds.
  • Evidence: Stripe subscription overview, Create a subscription API reference, Billing collection methods.

Claim: The first subscription invoice can remain incomplete until paid, which helps enforce “no work until payment clears.”

  • Status: Verified
  • Assessment: Stripe docs say the initial invoice can remain open and the subscription incomplete; if payment is not made within about 23 hours, the subscription can become incomplete_expired.
  • Evidence: Stripe subscription overview, How subscriptions work.

Claim: Stripe supports automatic retries and failed-payment email notifications.

Claim: ACH is much cheaper than cards on Stripe, but slower and less final.

  • Status: Verified
  • Assessment: Stripe’s published US ACH Direct Debit pricing is 0.8% capped at $5, with default confirmation and settlement timing shown as about 4 business days. Domestic online card pricing is shown as 2.9% + 30¢. ACH is therefore cheaper for larger retainers, but timing and failure/return risk make it less convenient than cards for “payment certainty before work starts.”
  • Evidence: Stripe pricing, Stripe Billing pricing, US bank debits / ACH page.

Claim: Cards are cleaner for strict “do not start until paid” workflows, while ACH should be used selectively.

  • Status: Assistant-stated but unverified
  • Assessment: This is a practical recommendation derived from verified Stripe timing and pricing, not a formal Stripe policy statement.
  • Comment: Reasonable and probably correct for many SMB service firms, but still a business judgment.

3.2 Contract-structure claims

Claim: Solanasis should use MSA + retainer SOW + separate project/change-order path rather than a vague monthly support agreement.

  • Status: Verified for the legal structure distinction, Assistant-stated but unverified for “should”
  • Assessment: Ironclad’s contract guidance supports using MSAs for baseline relationship terms and SOWs for specific deliverables, timelines, and commercial terms. The recommendation that Solanasis adopt this structure is a strong best-practice judgment rather than a statutory requirement.
  • Evidence: MSAs and SOWs: Managing the Contract Relationship, MSA vs SOW, What is an SOW?, What is an MSA?.

Claim: A retainer should define response windows, included work, exclusions, term length, and how extra work gets approved.

  • Status: Assistant-stated but unverified, but strongly supported by practitioner guidance
  • Assessment: This is standard operating advice, and practitioner sources explicitly warn that vague boundaries create unlimited consulting for a fixed fee.
  • Evidence note: See Consulting Retainer Guide in 2025. This is not a primary legal source, but it is directionally aligned with common consulting practice.

3.3 Fractional-model claims

Claim: Fractional leaders are usually engaged part-time, often one to three days a week, for a bounded period such as six to eighteen months.

Claim: Strong fractional executives use signed charters, decision-rights documents, KPI targets, scope thresholds, and mid-course renegotiation triggers.

Claim: Fractional CIOs bring outside pattern recognition and an independent viewpoint.

  • Status: Verified
  • Assessment: CIO.com coverage explicitly discusses the independent, temporary or part-time nature of fractional CIOs and the different perspective they bring.
  • Evidence: How to succeed as a fractional CIO.

Claim: The best pitch is “capital-efficient access to executive leadership now,” not “cheap labor.”

  • Status: Assistant-stated but unverified
  • Assessment: This is a synthesis from salary/cost evidence plus practitioner playbooks. It is sound positioning advice, but not a verifiable “fact.”
  • Comment: Keep this; it is strategically important.

3.4 Full-time employee vs fractional economics claims

Claim: The real comparison is not just salary; it is salary plus benefits, recruiting, onboarding, delay, and the risk of a wrong hire.

  • Status: Verified in part, Assistant-stated but unverified in part
  • Assessment: BLS verifies that compensation costs exceed wages alone, and Umbrex verifies that part of the model’s appeal is preserving capital and avoiding premature full-time hires. Recruiting cost, onboarding drag, and mis-hire risk are commercially real but not fully quantified in this artifact.
  • Evidence: BLS ECEC September 2025, Understanding the Fractional Executive Model.

Claim: Median pay for computer and information systems managers was $171,200 in May 2024.

Claim: Benefits add roughly 42% on top of wages for private industry workers.

  • Status: Verified, but note nuance
  • Assessment: BLS reports 13.68 benefits in September 2025, so benefits were approximately 42.3% of wages and about 29.7% of total compensation. Use the correct denominator depending on context.
  • Evidence: BLS ECEC September 2025.

Claim: This BLS salary data is a perfect proxy for a full-time CIO or COO.

  • Status: Not supported
  • Assessment: It is not a perfect proxy. It is only a directional benchmark for the cost of senior internal technology leadership.

3.5 Worker-classification claims

Claim: Fractional consultants must be careful not to drift into quasi-employee status.

Claim: The current DOL framework is settled and should be treated as stable.

  • Status: Not supported
  • Assessment: As of 2026-03-18, the DOL has issued a proposed rule to rescind the 2024 final rule, so this area is not stable.

3.6 Pricing-range claims from the discussion

Claim: Solanasis should keep assessment pricing around 7.5K, with a higher band for messier or regulated clients.

  • Status: Assistant-stated but unverified
  • Assessment: This was a recommendation from the discussion. It may be strategically sound but was not independently benchmarked here against direct local competitors.

Claim: Solanasis should avoid normal retainers below 5K/month+, target a core band of 8.5K/month, and reserve 15K/month for embedded fractional work.

  • Status: Assistant-stated but unverified
  • Assessment: This is the central pricing recommendation from the discussion, but it is not backed here by a rigorous market study of Colorado SMB/nonprofit fractional consulting rates. Treat it as a strong hypothesis, not proven fact.
  • Status: Weakly supported / not fully verified
  • Assessment: The discussion referenced public market ranges from vendor or practitioner sources such as Cynomi and Umbrex. Those are directional, but they are not a robust market census. If Solanasis wants to publish or rely heavily on those numbers, they need stronger benchmarking.

4. Extracted Core Recommendations from the Discussion

This section captures the substantive recommendations made during the conversation, whether or not they were independently verified.

4.1 Commercial model

  • Assistant-stated but unverified: Do not sell “access to us for anything.” Sell reserved senior capacity, governance cadence, priority access, and bounded execution.
  • Assistant-stated but unverified: The retainer should buy continuity and momentum, not unlimited implementation.
  • Assistant-stated but unverified: The offer should be framed as standing-capacity retainer, not generic monthly support.
  • Assistant-stated but unverified: The cleanest client journey is:
    1. paid assessment / baseline
    2. remediation / quick wins
    3. ongoing retainer
    4. separate project or upgrade when new work becomes material
  • Assistant-stated but unverified: Solanasis should position itself as Operational Resilience Leadership, Fractional CIO/CISO/COO Oversight, or Technology, Security, and Operations Continuity, not commodity IT support.

4.2 Scope-control model

  • Assistant-stated but unverified: A request should stop being “base retainer work” when it:
    • creates a new deliverable,
    • creates a new workstream,
    • crosses teams or vendors,
    • exceeds a threshold such as 4–8 hours,
    • introduces deadline-driven implementation,
    • or materially changes monthly priorities.
  • Verified as directionally aligned: Umbrex’s playbooks use >8-hour thresholds, 90% hour-cap alerts, and strategic-time ratio rules.
  • Assistant-stated but unverified: Solanasis should cap not just time, but simultaneous active workstreams.
  • Tentative / speculative: Suggested workstream caps from the discussion:
    • Tier 1: 1 active workstream
    • Tier 2: 2 active workstreams
    • Tier 3: 3 active workstreams

4.3 Expansion-path model

  • Assistant-stated but unverified: The preferred structure is:
    • base retainer,
    • pre-priced monthly expansion packs,
    • time-boxed “sprints” for larger but still repeatable needs,
    • full project SOW only for genuinely large work.
  • Assistant-stated but unverified: The client should usually have three choices when they need more:
    1. queue it,
    2. upgrade or buy additional capacity,
    3. scope it as a sprint/project
  • Tentative / speculative: Example expansion lanes proposed in the discussion:
    • Capacity Boost
    • Priority Access Upgrade
    • Additional Workstream Add-On
    • Vendor Stabilization Sprint
    • Backup/DR Verification Sprint
    • CRM Cleanup Sprint
    • Systems Integration Sprint
    • Incident Readiness Sprint

4.4 Internal economics

  • User-stated: The user wants to preserve a minimum floor of $250/hour.
  • Assistant-stated but unverified: Solanasis should not design packages using exactly 300–$350/hour equivalent** to absorb invisible overhead.
  • Assistant-stated but unverified: A practical formula is:
    • Realized effective rate = Monthly fee / actual all-in time
    • Package design rate = expected max real hours × 350
  • Assistant-stated but unverified: This means the $250/hour floor becomes a red-line realized floor, not the number used to build packages.

4.5 Billing policy

  • Assistant-stated but unverified: Retainers should be billed monthly in advance.
  • Assistant-stated but unverified: Autopay should be the default for most SMB and nonprofit clients.
  • Verified: Stripe can technically support this.
  • Assistant-stated but unverified: Work for the month should begin only after payment succeeds.
  • Assistant-stated but unverified: No standard retainers should be billed in arrears.
  • Assistant-stated but unverified: For larger or more procurement-heavy clients, invoice + ACH/AP may be acceptable, but only with terms that protect cash flow and pause work if unpaid.
  • Assistant-stated but unverified: Assessment work should be paid before scheduling starts.
  • Assistant-stated but unverified: Projects should be 50% up front / 50% milestone, or 100% up front if small and fixed-fee.

4.6 Positioning and sales framing

  • Assistant-stated but unverified: Do not pitch Solanasis as discounted labor. Pitch it as capital-efficient access to executive-grade leadership now.
  • Verified in spirit: Umbrex and CIO.com both support part-time executive access, preservation of capital, and outside perspective as part of the fractional model.
  • Assistant-stated but unverified: The strongest value story is:
    • fast access,
    • lower fixed-cost commitment,
    • outside pattern recognition,
    • fewer hiring mistakes,
    • and a stronger operating cadence
  • Assistant-stated but unverified: Solanasis should emphasize that one internal employee usually does not bring the same cross-company pattern recognition and objective outside perspective.
  • Assistant-stated but unverified: The first 30 days must feel tangible, not abstract. The discussion recommended:
    • stakeholder interviews,
    • current-state memo,
    • risk/bottleneck register,
    • vendor/system map,
    • top-10 priorities,
    • 30/60/90 plan,
    • cadence calendar,
    • and quick wins

5. Improved Solanasis Playbook

This section is the improved operating model synthesized from the discussion plus the verification pass.

A. Engagement ladder

  1. Operational Resilience Baseline / Assessment
  2. Immediate remediation or quick wins
  3. Retainer for ongoing leadership and bounded execution
  4. Expansion packs / sprints / tier upgrades
  5. Major project SOW only when the work truly deserves it

Why this is the best fit: It gives the client a low-friction but paid entry point, creates visible early value, and avoids pricing blind. It also preserves the ability to convert into recurring revenue without promising unlimited implementation.

B. Documents

  • Verified / recommended: Use a Master Services Agreement (MSA) for core legal terms.
  • Verified / recommended: Use a retainer SOW for the specific monthly operating model.
  • Verified / recommended: Use a project SOW or change order for major expansions.
  • Tentative / speculative: Use a separate one-page Governance Charter or Operating Charter to define decision rights, escalation, primary contacts, and priority rules.

5.2 What a Solanasis retainer should include

Included

  • recurring executive or operating cadence,
  • priority tracking and follow-through,
  • risk register / roadmap ownership,
  • vendor coordination,
  • limited asynchronous advisory,
  • limited bounded implementation capacity,
  • periodic reporting or review artifacts.

Excluded unless separately priced

  • large migrations,
  • deep system cleanups,
  • net-new platform implementations,
  • broad cross-functional rollout projects,
  • after-hours incident handling,
  • help desk/end-user support,
  • large procurement processes,
  • unlimited tactical admin.

Assistant-stated but unverified: This “leadership + governance + bounded execution” framing is one of the most important strategic takeaways from the discussion.

The following is a working pricing hypothesis, not a verified market benchmark.

Tier 0 — Baseline / Assessment

  • Assistant-stated but unverified: 7.5K for straightforward SMB/nonprofit clients
  • Assistant-stated but unverified: 12K for messy, regulated, higher-risk, or multi-location clients

Tier 1 — Advisory / Light Oversight

  • Assistant-stated but unverified: 5K/month
  • Best for organizations needing strategy, oversight, prioritization, and accountability more than implementation.
  • This tier should be intentionally narrow so it does not become disguised cheap labor.

Tier 2 — Core Operational Resilience Partner

  • Assistant-stated but unverified: 8.5K/month
  • This should likely be Solanasis’s default target tier.
  • Suitable for firms that need biweekly cadence, operational follow-through, vendor coordination, and bounded execution.

Tier 3 — Embedded Fractional CIO/CISO/COO

  • Assistant-stated but unverified: 15K/month
  • Weekly cadence, stronger responsiveness, broader accountability, more embedded leadership.

Tier 4 — Custom / High-Complexity

  • Tentative / speculative: $15K+/month
  • Use only for unusually messy environments, multi-entity coordination, significant regulatory friction, or near-half-time embedded leadership.

5.4 Internal economics guardrail

Rule 1: Design rates higher than your floor

  • User-stated: Floor = $250/hour
  • Assistant-stated but unverified: Internal package design should be built around roughly 350/hour equivalent

Rule 2: Track all-in time

Track:

  • meetings,
  • prep,
  • follow-up,
  • async messaging,
  • internal coordination,
  • context switching,
  • proposal spillover,
  • and hidden admin.

Rule 3: Monitor realized rate monthly

Use: Realized effective rate = revenue collected / all-in time consumed

Rule 4: Reprice or re-tier when actual economics drift

  • Verified as conceptually aligned with Umbrex: renegotiate when engagements drift materially from the original plan.
  • Tentative / speculative: Solanasis should treat repeated realized rates below target as a trigger for re-tiering or changing the engagement design.

5.5 The best scope-control system

Capacity + workstream + urgency, not just time

A retainer should not be controlled only by a hidden hour bucket. It should also be controlled by:

  • number of active workstreams,
  • response-time promises,
  • stakeholder count,
  • and deliverable thresholds.

Suggested practical thresholds

These are proposed thresholds derived from the discussion and informed by Umbrex’s playbooks:

  • Tentative / speculative: New deliverable over 4–8 hours → expansion path or sign-off
  • Verified as externally similar: Umbrex uses >8-hour thresholds in current playbooks
  • Tentative / speculative: Cross-functional or cross-vendor workstream → usually not base retainer
  • Tentative / speculative: Deadline-driven implementation → usually sprint or project lane
  • Tentative / speculative: More than agreed number of active workstreams → upgrade/add-on

Traffic-light capacity rules

  • Tentative / speculative:
    • Green: under 70% of monthly capacity
    • Yellow: 70–85% used, warn client
    • Red: 85–90%+ used, no more silent absorption
  • Verified as analogous: Umbrex explicitly recommends 90% hour-cap alerts.

This is one of the most important improvements from the discussion.

Expansion Lane 1 — Capacity Boost

A temporary monthly add-on for more executive/implementation capacity.

Expansion Lane 2 — Priority Access Upgrade

Used when the client wants tighter response windows or more immediate involvement.

Expansion Lane 3 — Additional Workstream Add-On

Used when the client wants Solanasis to carry one more standing area of responsibility.

Expansion Lane 4 — Time-boxed Sprint

Used when the client needs a meaningful but repeatable body of work done, and Solanasis wants to avoid full custom project scoping.

Expansion Lane 5 — Major Project SOW

Used only when the work is clearly too large or too unique for the standard lanes.

Assistant-stated but unverified: This is the cleanest way to avoid a fresh custom proposal every time while still keeping commercial discipline.

5.7 Billing playbook

Default policy

  • monthly prepay,
  • autopay required for standard SMB/nonprofit clients,
  • no kickoff until payment succeeds,
  • work pauses if payment fails after defined grace,
  • billing anchor on contract start or the 1st of the month.

Payment-method guidance

  • Verified: Cards are more expensive but operationally cleaner on Stripe.
  • Verified: ACH is cheaper but slower and carries different timing/return dynamics.
  • Tentative / speculative: Default to cards for lower and mid-range retainers; offer ACH or invoice/AP on higher tiers or for clients with formal procurement.

Practical implementation notes

  • Use Stripe subscriptions where possible.
  • Store a default payment method.
  • Turn on failed-payment emails.
  • Use webhook or internal alerts for invoice.payment_failed.
  • Decide in contract language what happens if payment is late, fails, or requires customer action.

5.8 Positioning playbook

What to say

  • You get executive-grade judgment now.
  • You avoid premature full-time fixed cost.
  • You get outside pattern recognition across multiple environments.
  • You get speed, operating cadence, and clearer decisions.
  • You get a defined launch phase and visible artifacts.

What not to say

  • “We’re just cheaper than an employee.”
  • “We can help with whatever you need.”
  • “Unlimited support.”
  • “Part-time employee.”

Better message

Assistant-stated but unverified, but strategically strong:
Solanasis is not a cheaper body. Solanasis is a faster, more capital-efficient way to install resilience, operating discipline, and senior judgment before the company is ready to justify or define multiple full-time leadership hires.

5.9 Tangible value artifacts that help retention

The discussion strongly implied that retainers need visible outputs. This section makes that explicit.

Suggested recurring artifacts:

  • executive scorecard,
  • resilience roadmap,
  • risk register,
  • vendor accountability matrix,
  • backup/DR verification log,
  • systems inventory,
  • decision log,
  • quarterly recommendations memo,
  • renewal-readiness checklist.

Assistant-stated but unverified: These artifacts help the client “feel” the value of the retainer and reduce the risk that the engagement is perceived as expensive conversations plus invisible work.

6. Implementation Workflow for Solanasis

This section converts the playbook into step-by-step operations.

6.1 Sales motion

  1. Discovery call

    • Diagnose pain, urgency, and leadership vacuum.
    • Clarify whether they need stabilization, prioritization, risk reduction, or embedded execution support.

  2. Sell the baseline

    • Do not jump straight to an open-ended retainer.
    • Sell a defined diagnostic / baseline with clear deliverables.

  3. Deliver a current-state memo + 30/60/90 plan

    • This reduces buyer anxiety around prepayment.

  4. Propose one of three retainer lanes

    • narrow advisory,
    • core resilience partner,
    • embedded fractional leadership.

  5. Explain how extra needs work

    • queue,
    • upgrade,
    • or sprint/project lane.

  6. Collect payment before kickoff

    • especially for smaller or founder-led clients.

6.2 Delivery motion

  1. Establish primary contact and governance cadence.
  2. Publish risk/priority tracker.
  3. Confirm decision rights and escalation rules.
  4. Track capacity privately.
  5. Alert client at yellow threshold.
  6. Force a choice at red threshold.
  7. Run quarterly scope/tier review.
  8. Capture artifacts and outcomes for renewal proof.

6.3 Renewal / expansion motion

At renewal or quarterly review, ask:

  • Has urgency increased?
  • Are there more active workstreams?
  • Is tactical work crowding out strategic work?
  • Has the client started using Solanasis as default implementation labor?
  • Is the realized rate still healthy?
  • Would a sprint or tier upgrade reduce friction and improve results?

7. Risks, Pitfalls, and Edge Cases

7.1 Biggest economic risks

  • User-stated / Assistant-developed: falling below the $250/hour floor because “small” asks accumulate invisibly
  • Assistant-stated but unverified: context switching across too many workstreams
  • Assistant-stated but unverified: too many stakeholders routing requests into the retainer
  • Assistant-stated but unverified: tactical firefighting displacing strategic leadership work
  • Assistant-stated but unverified: underpricing lower tiers to “win” early clients
  • Assistant-stated but unverified: letting premium executive retainers get mentally compared to cheap MSP/helpdesk packages

7.2 Biggest sales risks

  • Assistant-stated but unverified: sounding like generic outsourced labor
  • Assistant-stated but unverified: leading too hard with “cheaper than an employee” instead of “capital-efficient executive access”
  • Assistant-stated but unverified: asking clients to prepay for something that feels vague or intangible
  • Assistant-stated but unverified: presenting too many custom options instead of a disciplined model

7.3 Biggest legal / structural risks

  • Verified: worker-classification drift toward employee-like control
  • Tentative / speculative: unclear security/data-handling responsibilities if Solanasis gains admin access across systems
  • Tentative / speculative: unclear liability boundaries if Solanasis is positioned as security leader but incident-response obligations are not tightly defined
  • Tentative / speculative: procurement/AP delay on larger clients if billing assumptions are too SMB-oriented

7.4 Biggest delivery risks

  • Assistant-stated but unverified: failure to create visible artifacts and proof of progress
  • Assistant-stated but unverified: no explicit offboarding or success transition path
  • Assistant-stated but unverified: no distinction between advisory, coordination, and hands-on implementation

8. Missing Considerations Added by This Review

These were not fully developed in the discussion, but another AI should include them in the next round.

8.1 Insurance and risk transfer

  • Tentative / speculative: Solanasis likely needs to review E&O / professional liability and cyber liability coverage before taking on deeply embedded leadership obligations, especially if it is advising on security, DR, vendor selection, or AI.
  • Why it matters: The more Solanasis looks like the senior technology/security decision layer, the more clients may expect reliance and accountability.

8.2 Data access and security clauses

  • Tentative / speculative: Retainer agreements should define:
    • what admin access Solanasis receives,
    • what systems are in scope,
    • MFA and credential-handling rules,
    • subcontractor access rules,
    • client security obligations,
    • and incident-notification expectations.

8.3 Procurement reality on larger clients

  • Tentative / speculative: Some better-funded or more regulated clients may insist on:
    • W-9,
    • COI,
    • MSA review,
    • security questionnaire,
    • AP setup,
    • invoice terms,
    • vendor portal enrollment.
  • Why it matters: “Autopay only” is ideal for small clients, but larger clients may need a more flexible version of the same principle.

8.4 Nonprofit budget cycles

  • Tentative / speculative: Nonprofits may buy on board or grant cycles, which can affect contract start dates, invoice timing, renewal dates, and willingness to commit to multi-month terms.

8.5 Board / leadership reporting

  • Tentative / speculative: If Solanasis is truly acting in a fractional executive lane, it may be valuable to formalize a board-facing or leadership-team-facing reporting template.

8.6 Exit and transition

  • Verified in general from Umbrex: a good fractional model includes preparation for what happens after the engagement ends.
  • Tentative / speculative: Solanasis should define whether it:
    • hands off to internal staff,
    • helps hire a successor,
    • converts to project-only support,
    • or remains in a lower-intensity advisory lane.

8.7 Direct competitor and market benchmarking

  • Open gap: This artifact did not benchmark Solanasis pricing against a rigorous list of Colorado or niche-specific competitors serving SMBs, nonprofits, RIAs, or wealth-management-adjacent firms. That should be done before prices are published externally.

9. Open Questions / What Still Needs Verification

This section is required by the user and should be actively used in follow-on work.

  1. What are actual current pricing bands for fractional COO/CIO/CISO work in Solanasis’s specific niches?

    • Needs targeted market benchmarking by region, industry, and service mix.

  2. What monthly capacity does Dmitri personally want to sell, versus reserve for CEO work, sales, and partnerships?

    • The discussion recommended keeping unsold capacity, but did not size it rigorously.

  3. Should the $250/hour floor apply only to Dmitri’s time, or blended across subcontractors and AI-assisted delivery?

    • This materially changes package economics.

  4. What exact work should count as “bounded execution” for Solanasis?

    • Needs a concrete internal service catalog.

  5. What exact sprint menu should Solanasis standardize?

    • A repeatable sprint catalog would reduce custom scoping and speed proposals.

  6. What exact response-time promises should be tied to each tier?

    • This affects both staffing expectations and price.

  7. What contract language should be used for out-of-scope work, payment failure, pause of service, and no employee relationship?

    • Needs legal drafting and probably counsel review.

  8. Should card autopay be mandatory for all SMBs, or should ACH be allowed when initiated early enough?

    • Needs a deliberate policy, not just default preference.

  9. What is the right minimum term by tier?

    • Discussion suggested 3 months and 6 months, but this was not tested against buyer resistance.

  10. How should Solanasis handle emergency incident work?

    • Separate retainer? Premium add-on? Hourly emergency rate? Dedicated incident SOW?

  11. What artifacts most strongly support renewal in Solanasis’s target segments?

    • Needs customer development and perhaps pilot data.

  12. How should nonprofit clients with procurement, board approval, or grant constraints be handled without weakening cash flow protection?

    • Needs a nonprofit-specific billing variation.

  13. What local / state legal review is needed for contractor classification, limitation of liability, indemnities, and security obligations?

    • Federal guidance exists, but local counsel review is still prudent.

  14. How should AI-assisted delivery be disclosed, priced, and governed?

    • Especially relevant because Solanasis wants to be AI-native.

10. Handoff Notes for Another AI

This section is intentionally explicit so another AI can pick up the work fast.

10.1 What is already decided enough to build on

  • The commercial target is recurring revenue with premium positioning, not bargain consulting.
  • The core structural model should be:
    • Baseline / assessment first
    • Retainer second
    • Expansion packs / sprints third
    • Large project SOW only when needed
  • Billing should default to monthly prepay, preferably through Stripe autopay for typical SMB/nonprofit clients.
  • The model should protect a hard effective floor of $250/hour.
  • The retainer should not be unlimited; it should be built around leadership cadence + governance ownership + bounded execution + explicit expansion paths.
  • The messaging should emphasize capital-efficient executive access, speed, objectivity, and operating discipline, not “cheap outsourced help.”

10.2 What another AI should do next

  1. Draft a client-facing tier matrix with:

    • tier names,
    • outcomes,
    • cadence,
    • included artifacts,
    • exclusions,
    • upgrade paths.

  2. Draft a retainer SOW template that includes:

    • mandate,
    • included services,
    • excluded services,
    • active workstream cap,
    • change-order/expansion triggers,
    • billing terms,
    • pause-for-nonpayment clause,
    • term/renewal language.

  3. Draft MSA language suggestions for:

    • independent contractor status,
    • confidentiality,
    • IP,
    • limitation of liability,
    • payment timing,
    • suspension for nonpayment,
    • use of subcontractors / AI tools,
    • security responsibilities.

  4. Create a pricing calculator that models:

    • expected all-in hours,
    • hidden overhead,
    • target realized rate,
    • workstream count,
    • urgency,
    • complexity modifiers,
    • margin by client.

  5. Create a sales script and proposal section for:

    • why fractional vs full-time,
    • why prepay,
    • why the baseline comes first,
    • how scope and extra work are handled.

  6. Build a standard sprint catalog for repeatable expansions.

  7. Run market research on comparable firms in Colorado and national niche comparables.

10.3 What another AI should not assume

  • Do not assume the suggested pricing is already market-validated.
  • Do not assume every client will accept card autopay.
  • Do not assume generic MSP pricing logic applies to premium fractional leadership work.
  • Do not assume worker-classification rules are stable in 2026.
  • Do not assume that “fractional COO/CIO” means the same thing in every buyer’s mind; always anchor to a clear mandate.

11. Reviewer Pass / Self-Review

What this artifact does well

  • It separates facts, user inputs, recommendations, and speculation.
  • It verifies the most important external claims from the discussion with current sources.
  • It preserves the core strategy logic of the chat while tightening the weak spots.
  • It adds missing implementation and legal/risk considerations that the original discussion only implied.

What remains weak

  • Pricing remains the biggest weak spot. The recommended dollar bands are strategic hypotheses, not yet market-validated.
  • Some practitioner sources used for fractional best practices, especially Umbrex and consulting blogs, are helpful but are still practitioner/vendor sources, not academic or regulatory research.
  • The artifact does not yet include direct legal drafting or local counsel review.
  • The artifact does not yet include a direct competitor matrix for Colorado or Solanasis’s preferred verticals.

Corrections versus the live discussion

  • The discussion’s use of salary and benefit data should be treated as directional, not as a perfect proxy for full-time CIO/COO cost.
  • Worker-classification guidance is less stable than the conversation implied because the DOL has proposed changes in 2026.
  • ACH is cheaper, but the operational realities make it less clean than cards for strict “no work until paid” enforcement.
  • Any public benchmark bands for vCISO/fractional leadership pricing should be treated as weak evidence until independently benchmarked.

12. Source Register

Primary / official sources

  1. Stripe — How subscriptions work
    https://docs.stripe.com/billing/subscriptions/overview
    Used for: subscription incomplete state, first invoice behavior, retry behavior.

  2. Stripe — Create a subscription API reference
    https://docs.stripe.com/api/subscriptions/create
    Used for: collection_method=charge_automatically, first invoice finalization, payment behavior.

  3. Stripe — Billing collection methods
    https://docs.stripe.com/billing/collection-method
    Used for: automatic charging vs send-invoice/manual methods.

  4. Stripe — Pricing
    https://stripe.com/pricing
    Used for: domestic card pricing and ACH pricing overview.

  5. Stripe — Billing pricing
    https://stripe.com/billing/pricing
    Used for: card and ACH pricing under Billing.

  6. Stripe — US bank debits / ACH
    https://stripe.com/payments/us-bank-debits
    Used for: ACH price, confirmation time, settlement timing.

  7. Stripe — Automatic collection
    https://docs.stripe.com/invoicing/automatic-collection
    Used for: failed-payment notifications and retries.

  8. Stripe — Using webhooks with subscriptions
    https://docs.stripe.com/billing/subscriptions/webhooks
    Used for: payment-failure events and status-change handling.

  9. BLS — Computer and Information Systems Managers
    https://www.bls.gov/ooh/management/computer-and-information-systems-managers.htm
    Used for: median annual wage for a senior internal IT-management benchmark.

  10. BLS — Employer Costs for Employee Compensation, September 2025
    https://www.bls.gov/news.release/pdf/ecec.pdf
    Used for: wages vs benefits costs.

  11. IRS — Independent contractor or employee
    https://www.irs.gov/businesses/small-businesses-self-employed/independent-contractor-self-employed-or-employee
    Used for: behavioral control, financial control, relationship factors.

  12. IRS — Worker classification 101
    https://www.irs.gov/newsroom/worker-classification-101-employee-or-independent-contractor
    Used for: simplified worker-classification framing.

  13. DOL — 2026 proposed rule release
    https://www.dol.gov/newsroom/releases/whd/whd20260226
    Used for: current instability in federal independent-contractor rulemaking.

  14. DOL — 2026 rulemaking FAQs
    https://www.dol.gov/agencies/whd/flsa/misclassification/2026rulemaking/faqs
    Used for: current rulemaking status and rationale.

  15. DOL — current rulemaking page / final rule context
    https://www.dol.gov/agencies/whd/flsa/misclassification/rulemaking
    Used for: context on the current federal rule structure.

Practitioner / industry sources (useful, but not primary law or market census)

  1. Umbrex — Understanding the Fractional Executive Model
    https://umbrex.com/resources/fractional-executive-playbook/understanding-the-fractional-executive-model/
    Used for: retainer/day model and preservation of capital framing.

  2. Umbrex — Fractional Chief Operating Officer Playbook
    https://umbrex.com/resources/fractional-executive-playbook/fractional-chief-operating-officer-playbook/
    Used for: scope guardrails, 8-hour change-order threshold, 90% hour-cap alert, strategic-time ratio.

  3. Umbrex — Fractional Chief Information Officer Playbook
    https://umbrex.com/resources/fractional-executive-playbook/fractional-chief-information-officer-playbook/
    Used for: charter/decision-rights ideas, strategic-time ratio, initiative sign-off threshold.

  4. Umbrex — Fractional CEO / Interim CEO Playbook
    https://umbrex.com/resources/fractional-executive-playbook/fractional-ceo-interim-ceo-playbook/
    Used for: renegotiation when engagement drifts >15%.

  5. Umbrex — Delivering Exceptional Value
    https://umbrex.com/resources/fractional-executive-playbook/delivering-exceptional-value/
    Used for: value artifacts and exit-phase discipline.

  6. CIO.com — How to succeed as a fractional CIO
    https://www.cio.com/article/473360/how-to-succeed-as-a-fractional-cio.html
    Used for: outside perspective and part-time/temporary framing.

  7. Ironclad — MSA/SOW resources
    https://ironcladapp.com/journal/contracts/msas-and-sows-managing-the-contract-relationship
    https://ironcladapp.com/journal/contracts/msa-vs-sow
    https://ironcladapp.com/journal/contracts/what-is-an-sow
    https://ironcladapp.com/journal/contracts/what-is-an-msa
    Used for: practical contract-structure distinctions.

  8. Consulting Success — Consulting retainer guide
    https://www.consultingsuccess.com/consulting-retainer
    Used only as practitioner support for scope-creep warnings, not as a primary authority.

  9. Productive — What is a retainer in business
    https://productive.io/blog/what-is-a-retainer-in-business/
    Used only as practitioner support for retainer definitions and rollover-policy considerations, not as a primary authority.

  10. Clutch — Managed IT services guide / rankings
    https://clutch.co/it-services/msp/service-guide
    https://clutch.co/it-services/msp
    Used only for directional market framing, not for authoritative pricing.

13. Condensed Action Plan

Immediate next documents to create

  1. Client-facing pricing/tier sheet
  2. Retainer SOW template
  3. Expansion-pack menu
  4. Sprint catalog
  5. Discovery-call script
  6. Proposal section: “Why fractional vs full-time”
  7. Internal profitability tracker

Immediate decisions to make

  1. Minimum monthly retainer floor
  2. Card vs ACH default policy
  3. Minimum term by tier
  4. Scope threshold rules
  5. Active workstream caps
  6. Emergency-support policy
  7. Which artifacts are delivered monthly vs quarterly

Immediate research gaps to close

  1. Colorado/local market pricing
  2. Niche competitor positioning
  3. Legal review of agreements
  4. Insurance requirements
  5. Nonprofit procurement/budget realities

14. Bottom Line

Assistant-stated but unverified, but highly actionable:
The strongest version of Solanasis’s model is not “we don’t bill by the hour.” It is: we sell premium executive cadence and resilience leadership, we track time and scope ruthlessly behind the scenes, and we force meaningful extra demand into pre-priced expansion paths instead of silently eating it.

Assistant-stated but unverified:
That is the commercial sweet spot that protects margin, preserves premium positioning, reduces proposal churn, and still gives clients a humane path to buy more help when they genuinely need it.

Graph View