What Does a Fractional CTO Actually Do? (Week by Week)

The Short Version

A fractional CTO is a part-time Chief Technology Officer. You get senior technical leadership — architecture, strategy, team guidance, vendor evaluation — without the $300K+ fully-loaded cost of a full-time hire. I typically work with 2-3 companies at a time, embedded in each one deeply enough to make real decisions, not just give opinions.

But that job description is abstract. Let me show you what it actually looks like.

What a Typical Week Looks Like

I’m currently CTO at JET Hospitality, a 10-property glamping and boutique hotel group. Here’s a realistic breakdown of what my week looks like there.

Monday: Architecture and Planning

The week starts with reviewing what’s in flight. I check monitoring dashboards (self-hosted Uptime Kuma), review any overnight alerts, and scan the task board in our CRM. Then I’m making architecture decisions — this week it’s evaluating whether to move a batch processing job from a cron script to a proper queue system.

This is the kind of decision that seems small but compounds. Pick the wrong abstraction now and you’re refactoring in six months. Pick the right one and the team barely notices because it just works.

Tuesday: Building

I build things. This is where most fractional CTOs differ from traditional consultants. I don’t hand off architecture diagrams and disappear. I write code, deploy infrastructure, and ship features.

At JET, I built the entire CRM from scratch — Django, HTMX, Tailwind, PostgreSQL. Contact management, deal pipeline, email campaigns, hiring pipeline, project management, and Level 10 meeting facilitation. All in one tool instead of five SaaS subscriptions.

Wednesday: Team Sync and Mentorship

Weekly sync with the leadership team. We review metrics, discuss priorities, and I translate business goals into technical roadmap items. If the CEO says “we need to close more group bookings,” I’m the one figuring out what that means technically — better lead capture, automated follow-up sequences, analytics on conversion rates.

I also spend time with individual team members. Teaching a marketing coordinator how to use the CRM effectively. Helping a property manager understand why we structured the booking data the way we did. This isn’t glamorous work, but it’s what makes technology actually get adopted.

Thursday: Infrastructure and DevOps

Infrastructure day. Reviewing AWS costs, applying security patches, updating Docker containers, checking backup integrity. I migrated JET off a patchwork of GoDaddy, IONOS, and Wix hosting onto unified AWS EC2 + S3 infrastructure. That migration doesn’t end on deploy day — it requires ongoing care.

This is also when I handle DevOps tasks: CI/CD pipeline maintenance, monitoring configuration, and capacity planning. When you’re managing infrastructure for 10 properties across multiple states, there’s always something to tune.

Friday: Strategy and Future Planning

End of week is for strategic work. Evaluating new tools, researching approaches to problems we’ll face in 6-12 months, documenting architectural decisions, and planning the next sprint’s priorities.

This is where the “fractional CTO” part differs most from “senior developer.” A developer builds what’s in front of them. A CTO is thinking about what the company will need next quarter and making sure the foundation is there when it’s needed.

The Six Core Responsibilities

Beyond the weekly rhythm, here’s what the role breaks down into.

1. Technology Strategy and Roadmap

You can’t build what you haven’t planned. I create and maintain a technology roadmap that aligns with business goals. This isn’t a PowerPoint that sits in a drawer — it’s a living document that gets reviewed monthly and adjusted based on what we learn.

The roadmap answers: What are we building next? Why? What does it depend on? What do we need to be true before we start?

2. Architecture Decisions

Every technology choice is a bet. Database selection, framework choice, cloud provider, deployment strategy — each one has tradeoffs that aren’t obvious until you’ve made the wrong choice at scale. I’ve spent 20+ years at Salesforce and CVS Health learning what those wrong choices look like, so my clients don’t have to learn the hard way.

3. Vendor and Tool Evaluation

Startups get pitched constantly. Every SaaS vendor has a slide showing how they’ll solve your problems. A fractional CTO cuts through the noise — I’ve evaluated hundreds of tools and I know which ones are worth the contract and which are solving a problem you don’t have.

At JET, I replaced over $50K/year in SaaS spend with open-source alternatives. Not because open source is always better, but because for their specific workflows, the off-the-shelf tools were solving the wrong problems at premium prices.

4. Security, Compliance, and Risk

This is where enterprise experience matters. I’ve done FedRAMP at Salesforce (Government Cloud) and PCI-DSS at CVS Health (7,500 retail servers). When your startup needs SOC 2 to close an enterprise deal, or HIPAA to serve healthcare customers, you need someone who’s actually implemented compliance — not just read about it.

5. Team Leadership and Hiring

Even if your team is small, someone needs to set direction. I run sprint planning, code reviews (when there are developers), and help with hiring when the company is ready to bring on full-time engineers. I’ve helped define job descriptions, conduct technical interviews, and onboard new hires.

6. Stakeholder Communication

I translate between technical and non-technical. Board members want to know if the platform is secure. Investors want to know if the architecture can scale. The CEO wants to know if we’re on track. A CTO answers all of these in language each audience understands.

What a Fractional CTO is NOT

Let me be direct about what this role isn’t.

It’s not a one-time consultant. I don’t do a two-week assessment, hand you a PDF, and vanish. I’m embedded in your company. I’m in your Slack. I know your team by name.

It’s not a part-time developer. I build things, yes. But the value isn’t in my code output — it’s in the decisions I make about what to build, how to build it, and what not to build.

It’s not a temp CTO. Some companies hire fractional CTOs as a bridge while they recruit a full-time CTO. That’s a valid use case. But many of my clients keep me on long-term because the fractional model works better for their stage — they get CTO-caliber thinking at a fraction of the cost, and they can invest the savings in other areas.

Is a Fractional CTO Right for Your Company?

You’re a good fit if:

• You have 10-80 people and technology is core to your business but you don’t have technical leadership
• You’ve raised funding (or are profitable and growing) and need to deploy capital into infrastructure
• You have developers but no direction — engineers building features with nobody making architecture decisions
• You need compliance (SOC 2, HIPAA, PCI) and nobody on the team has done it before
• You’re spending $10K+/month on SaaS and suspect there’s a better way

If that sounds like your situation, let’s talk. I offer a free 30-minute assessment where we’ll review your current setup and I’ll tell you honestly whether a fractional CTO is what you need — or if something else makes more sense.

Ready to Talk?

Book a free technical assessment — 30 minutes, no obligation. We’ll discuss your technical challenges and I’ll give you a clear picture of what working with a fractional CTO would look like for your specific situation.

You can also see my pricing or read about how this worked for JET Hospitality.