You've made the call. You've brought on a fractional CTO. Now what?

Most founders I work with expect the typical consultant thing: big presentation, shiny slides, promises about "alignment" and "maximizing value." Then they're surprised when I show up asking basic questions instead.

Here's what actually happens in your first month with a fractional CTO, what it means, and why it matters. If you understand this timeline, you'll know whether you've got a partner who's serious or someone wasting your time.

Week 1: Discovery and Truth-Telling

The first week is about getting oriented. I'll want to meet your team, see your infrastructure, understand what you're actually running right now. Not what you think you're running. What you're actually running.

I'll ask the same questions multiple ways. Who owns this? Where are the databases? How do you deploy? You'll probably discover your team disagrees on the answers. That's normal. And it's useful.

I'll also sit with your leadership team. What does winning look like? Where's the revenue pressure? What keeps you awake? Tech decisions come from business reality, not the reverse.

By the end of week one, I'll have a lot more context. You'll probably realize nobody actually knows your full stack. That's fine. We're building a shared picture.

Week 2: Audit and Quick Wins

Now I'm digging deeper. I'll review code, check infrastructure, test deployments. Looking for problems and quick wins.

Most companies have obvious wins they're missing. Maybe you're overpaying for cloud. Maybe there's a security hole. Maybe deploys take 45 minutes when they should take 5. I document these.

I'm also getting to know your engineering team. Who actually knows how things work? Who's hungry to fix things? Who'll push back? The people matter as much as the code.

By the end of week two, I should spot 2-3 quick wins. Not the most important stuff. Just fast, visible wins to build momentum. You need proof early.

Week 3: Strategy Formation

By week three, I'm seeing patterns. I understand your debt. I know what your team can do. I've got a realistic sense of what's possible given your timeline and budget.

Here's the hard part: picking what actually matters. You've got a list of ten things. You can realistically do three. My job is helping you figure out which three.

This is where partnership beats consulting. I'm not telling you what to do. I'm asking hard questions and showing trade-offs. "Build that feature, you can't upgrade the database. Upgrade the database, you fix the slow queries killing your sales team." Real choices, real consequences.

I'll start drafting a roadmap. Not some five-year fantasy. A 90-day plan with real milestones and clear ways to measure progress.

Week 4: Execution Plan and First Deliverables

Week four is about making decisions. I'll present findings and the roadmap. Here's what I found. Here's what I think we should do. The order. The timeline. What breaks if we don't act.

If things went well, we'll have already started one of those quick wins. A deployment fix. A security patch. Something concrete, not just conversation.

We'll also set 90-day goals. By April, done X. By May, done Y. Real, measurable work. Not aspirational dreaming. Actual changes to how your business runs.

By the end of month one, you should feel like someone actually gets your situation. Not from asking the right questions. From digging in and understanding what's really happening.

What You Should Prepare Before Day One

Prep work matters. A few things make month one way more productive.

• Access. Your CTO needs access upfront. Code repos, cloud accounts, logs, recordings. Don't make them ask multiple times.
• Your time. Block your calendar for your CTO. If they can't get 30 minutes with you in month one, this won't work.
• Write down your problems. What breaks? What takes forever? What makes customers mad? Share this before day one.
• Introduce them properly. Have someone bring your CTO into the room with the team. Signal that you're serious about this partnership, not hiring a spy.

Red Flags: What Bad Onboarding Looks Like

Not all partnerships work. Sometimes it's a bad fit. Sometimes you hired wrong. Watch for these signs.

• Instant answers. If they're telling you what to do on day three without looking at anything, run. Good diagnosis takes time.
• No pushback. If they're not challenging you, they're not thinking. Real partnerships have friction.
• Radio silence. No updates, no findings, no questions, they're checked out. You need weekly check-ins.
• Blame instead of solutions. "Your code is a mess" isn't strategy. "Your code is a mess because X, which means we should do Y" is a partnership. Watch the difference.
• No roadmap by week four. You should know what 90 days looks like. If it's still vague, something's wrong.

Realistic Expectations

Month one shouldn't be dramatic. No big rewrites. No reinventing everything. It's about building trust and understanding what's actually going on.

What you get is clarity. You'll understand your situation better. You'll have a plan. A few small wins under your belt. Most importantly, you'll know if this person actually gets it.

The real work starts in month two. Month one is about setting up something that can actually work.