Skip to content
Jon BrydenFractional CTO

Operational Technology Sprints

A focused engagement that takes one specific problem and delivers a working improvement. Most sprints run about three weeks, typically $5,000 to $10,000 depending on the problem. Best when you can name the thing that's broken.

This can include

  • Automating a manual, spreadsheet-run process so it stops depending on one person
  • Connecting tools that don't talk, so people stop retyping the same data between them
  • Standing up a virtual assistant on a VoIP platform to handle routine calls
  • Streamlining an ecommerce or fulfillment operation that's gotten heavy and manual
  • Building a web app, mobile app, or marketing site
  • Building an internal AI knowledge library your team can actually search
  • Stabilizing a platform that's become slow, fragile, or unreliable

Fractional Technology Leadership

One senior owner for your technology strategy, security, applications, vendors, and internal IT function, at a fraction of the cost of a full-time CTO. Best when responsibility is spread across several people and partners, but nobody owns the whole picture.

What I own

  • Technology roadmap, annual budget, build-or-buy decisions, and quarterly priorities tied to your growth plan
  • Security program oversight, HIPAA-aligned controls, and SOC 2 readiness alongside an audit partner
  • Business continuity and disaster recovery plans that are documented, owned, and tested
  • Priorities and architecture across EHR, HRIS, Microsoft 365, finance systems, and custom applications
  • MSP and vendor selection, service levels, accountability, and transitions without service gaps
  • Hiring and guiding internal IT staff while keeping developers focused on building

Who it is for

Growing organizations, often 50 to 250 people, where technology decisions are spread across the COO, a developer, an MSP, and several vendors. It fits especially well when you are expanding into new locations or markets, changing your support model, or getting asked hard security questions.

Ongoing leadership

A steady cadence starting at about 5 hours a week, or up to roughly 20 hours a month, and scaling to roughly 30 hours a month for deeper Fractional CTO involvement. I plug into how you already run: quarterly priorities, a technology scorecard, monthly vendor and budget reviews, and a roadmap refreshed each quarter. If you run EOS, I work in Rocks and Scorecards.

Project work, scoped separately

MSP exit or transition, SOC 2 readiness, BCP/DR programs, Microsoft 365 and identity cleanup, integration architecture, or a major vendor selection are scoped separately.

Recommended first step

Technology Operating Model Review

A fixed-scope review over 2 to 3 weeks. I map who owns what today across your team, MSP, and vendors, find the gaps and the spend that is not earning its keep, and give you a clear plan: what to keep, what to fix, and what to change first.

What it is not

This is not outsourced IT or a help desk. I do not replace your MSP's technicians or your internal staff. I make sure the right people and partners own the right work, and I am accountable for the result.

Investment

It starts with the operating model review, a $1,500 fixed fee. Ongoing leadership starts at $3,500 a month as an Operating Partner, working alongside the CEO or COO who still owns technology, for up to roughly 20 hours a month. It starts at $6,500 a month as a Fractional CTO, where I am your accountable technology executive, for up to roughly 30 hours a month. The monthly fee depends on what I am responsible for, not a timesheet.

Technology & AI Advisory

Practical guidance on what to build, buy, integrate, automate, or leave alone. Best when the decision matters more than the build.

This can include

  • AI adoption and governance, so AI becomes real systems under real rules
  • Build, buy, or integrate decisions, with a clear recommendation and the reasoning behind it
  • Vendor, platform, and MSP selection and evaluation
  • A technology roadmap tied to business outcomes, not a wish list
  • Architecture decisions on systems you're about to commit real money to
  • Trusted-advisor support for a CEO or exec team with no senior technology voice in the room
  • Translating between the technology work and the business, so leadership understands what's happening and why

Pricing

Start small. Earn the next step.

Every engagement starts with a defined scope and a price you know up front. Trust gets earned on the first piece of work, not assumed. My standard is simple: the work should be worth far more to you than it costs.

Operational Technology Sprints

  • Focused Sprint

    $5,000fixed fee

    One bounded workflow or problem. Two to three weeks.

  • Accelerated Sprint

    $10,000fixed fee

    A larger, urgent, or cross-team problem, worked at a faster pace. Two to three weeks.

Fractional Technology Leadership

  • Operating Model Review

    $1,500fixed fee

    Two to three weeks. Who owns what, where the gaps and wasted spend are, and a plan. The first step before either role below.

  • Operating Partner

    from$3,500per month

    Your CEO or COO still owns technology. I work alongside them to set priorities, coordinate vendors and initiatives, and keep the roadmap moving. Up to roughly 20 hours a month.

  • Fractional CTO

    from$6,500per month

    I own technology as your accountable executive: strategy, security, architecture, budget, your IT team and vendors, and executive reporting. Up to roughly 30 hours a month.

Technology & AI Advisory

  • Advisory session

    $200per session

    One hour on a specific decision, including prep and a short written follow-up.

  • Monthly advisory

    from$1,500per month

    An ongoing senior technology advisor, typically around 10 hours a month of working sessions and on-call guidance.

Fixed fees are set before any work starts. Monthly roles pay for an agreed responsibility, outcomes, and level of involvement, not a prepaid block of hours, and are reviewed every quarter. "From" prices are where smaller organizations start; larger or more complex ones are quoted after a first conversation.

The bigger build

AI-Ready Foundation

The groundwork that has to exist before automation and AI actually pay off. A knowledge library your team and your tools draw on from one source of truth, documented processes, and a system architecture that connects your data instead of leaving people to move it by hand. Best when you already believe AI should be helping and it isn't, because there is nothing solid under it yet.

Most engagements build toward this. You can start with the whole foundation, or with one problem and grow into it.

  • A searchable knowledge library built on the systems you already run, so your team and your AI tools work from the same source of truth
  • Documented operating processes, so the rules live in the system instead of in people's heads
  • System and data architecture that connects your tools, so information stops moving by hand
  • Automation and agent workflows built on that foundation, with a human in the loop where judgment matters
  • AI governance you can live with: a clear policy, and who decides what
  • Adoption support, so the team uses what gets built

Fit

Who this is for, and who it isn't.

Being specific about the second list is the fastest way to respect everyone's time.

Good fit

  • Healthcare and behavioral health
  • EMS and public safety organizations
  • Certification, credentialing, licensing, and associations
  • Logistics, fulfillment, and eCommerce operations
  • Founder-led or owner-led SMBs
  • Lower-middle-market and growth-stage companies
  • Regulated or operationally complex environments
  • Companies with no senior internal technology leader

Not a fit

  • Pure staff augmentation
  • Offshore team management on its own
  • A company that wants a deck and no delivery
  • An AI initiative with no business outcome attached

Start with one problem.

Bring me the thing that's eating your week. We'll figure out whether it's worth solving and what it would take.