The seat at the table you didn't know was empty
It's late. She's at the kitchen table with her laptop open, looking at a quote that arrived in her inbox that afternoon. The number at the bottom is bigger than she expected. Not catastrophically bigger. Just bigger enough that she can't quite tell whether it's fair.
She's read the proposal three times. Some of it she understands. Some of it she half-understands. There's a section about an integration layer that she's read four times now and still couldn't explain to anyone else if she tried. She's not stupid. She's run this business for nine years. She knows how to read a contract, how to negotiate, how to tell when someone's selling her something she doesn't need. But this isn't a contract for office space or a marketing retainer. This is something else, and the something else is in a language she doesn't speak.
She thinks about who she could ask. Her accountant would tell her the number was within reason or it wasn't, and she'd trust him. Her lawyer would read the terms and flag anything that worried him, and she'd trust her too. The operations person who's been with her since the second year would have an opinion on the timeline and she'd take it seriously.
There's no-one like that for this.
It's not that she hasn't tried. She's hired developers. She's worked with agencies. She's sat through demos where men in branded polo shirts walked her through dashboards she couldn't quite parse. The people she's worked with have mostly been competent, mostly been honest, mostly delivered something that mostly worked. But none of them have ever been hers in the way her accountant is hers. None of them have ever sat on her side of the table.
She's thought about hiring a CTO. She's looked at what they cost. She's done the maths and quietly closed the spreadsheet. The number was somewhere between her own salary and double her own salary, and the idea of paying someone that much to do a job she couldn't fully evaluate felt like a particularly expensive kind of guess. So she's carried on making these decisions herself, with the help of whoever she could get on a call, hoping the instincts that work for everything else would stretch to cover this too.
Mostly they have. Sometimes they haven't, and the times they haven't have been expensive in ways that took months to surface.
She closes the laptop. She'll deal with it tomorrow.
She's having coffee with a friend a few weeks later and they get onto the topic of a piece of technical work the friend's company recently finished. She asks how it went. The friend says it went well. She asks how they decided who to use. The friend says, "Oh, we ran it past our fractional CTO first."
She doesn't know what a fractional CTO is.
The friend explains. He is someone they've been working with for about a year. Not full-time. Maybe a day a week, sometimes two. He sits in on the technical decisions, talks to the team, looks at the proposals, gives them an opinion. The friend describes it the way you'd describe a good GP. Someone who knows your situation, who you can call, who'll tell you when something's serious and when you can stop worrying about it.
She says, half-joking, "I didn't know that was a thing you could do."
The friend says, "Yeah. Most people don't."
What surprises her, over the following months, is what doesn't happen.
He doesn't save her from a disaster. There's no dramatic moment where he prevents some catastrophe. The catastrophes she'd been imagining mostly weren't going to happen anyway, and the ones that were going to happen were quieter than that. The kind that show up in budget reviews two years later as line items that should have been smaller.
He doesn't tell her she's been doing it wrong, either. Mostly he tells her she's been doing it about right. The direction she'd been taking the business was sensible. The decisions she'd been agonising over were usually the ones she'd already half-decided correctly. What she'd been missing wasn't direction. It was someone to confirm or push back on the direction, with enough context to be useful.
What changes is smaller and harder to describe than that. When the next quote comes in, she reads it once, forwards it to him, and they talk it through on a call. When she's interviewing a senior developer, he's in the room, and afterwards they compare notes the way she compares notes with her ops person after a hire. When the team says something is going to take three months, she has someone she can ask, privately, whether three months is reasonable, and get an honest answer.
The kitchen table, late at night, with the laptop open and the quote on the screen and the rising sense that she's about to make a decision she can't really evaluate. That mostly stops happening.
She still runs the business. She still makes the calls. The seat at the table is still hers. There's just someone sitting next to her now, who speaks the language she doesn't, and who answers when she asks.