The job, itemized
What a Fractional CTO Does: One Month in the Seat and the Paper It Leaves Behind
Ask ten vendors what a fractional CTO does and you will hear ten versions of "strategic guidance," a phrase that has never once restored a backup. Here is the actual work: a month in the seat, five documents to demand, and the requests a good one turns down.
November 5, 2026 · 8 min read
The short answer
A fractional CTO owns a company's technology plan and budget part time: auditing systems and vendors, deciding what to build, buy or leave alone, writing specifications, managing developers and setting rules for security, backups, integrations and AI. A buyer should receive a systems map, a risk list, a roadmap, vendor scorecards and a tested backup.
On this page
Four made-up weeks at a 25-person roofing company
Say a 25-person roofing company has a custom quote tool, one freelance developer, a field service platform, an IT company and a website nobody has touched in a while. The owner has bought a part-time seat for a set number of hours a month. The company is made up, and so are the particulars below. The shape of the work is what we are showing you.
| What the lead does | What the owner sees | |
|---|---|---|
| Week 1 | Reads twelve months of invoices, meets the developer, gets added to every account | A first list of what the company pays for, longer than anyone guessed |
| Week 2 | Reads the quote tool's code, calls the IT company, asks to see the last backup restored | A short list of questions the vendors could not answer |
| Week 3 | Writes a specification for the quote tool change, compares scheduling options, runs a restore test | A decision memo: build, buy or leave alone |
| Week 4 | Scores the vendors, updates the risk list, holds the standing meeting | The monthly page of numbers and two decisions to sign |
Notice how little of that is typing code. The title suggests architecture diagrams on glass walls. The job is more often reading an invoice closely and asking a vendor the same question twice. A large share of the value is in the order of things: nobody writes a roadmap in week one, because nobody yet knows what the company owns. The first 90 days page lays out that order in full.
Week 2 is where a builder pays off. Reading a quote tool's code only helps if the reader has written such things. At DataCram that reader is Casey Kinnison, a builder of custom software applications who does full stack development and relational database management. If a developer says the quote table cannot change without a rewrite, Casey can open the database and check.
Who owns what once the seat is filled
The seat owns
- The written technology plan and the proposed budget
- The audit of systems, code and vendors
- The call on build, buy or leave alone, within limits you set
- Specifications and the management of developers and vendors
- Security basics and backups, each with a written owner
- Integrations, data flow and the rules for AI
You keep
- The final say on money and on direction
- Every account, repository and domain, in the company's name
- Hiring and firing of your own staff, with advice if you want it
- Legal and compliance decisions, with your attorney
- The right to end the arrangement
Big companies have produced a familiar character: the CTO who has never been told no and has a full rewrite planned. A part-time seat comes with a built-in cure. You sign the budget, you can overrule the plan, and you can stop. That only works if the lead's recommendations are in writing, with costs attached, so you know what you are saying no to.
Five documents to demand by name, in writing
A buyer cannot audit judgment, but a buyer can audit paper. These five documents are the minimum evidence that a seat is occupied. Ask what each one looks like before you sign. A blank template is a fine answer. A shrug is not.
Systems map
Every system, what it does, what it connects to, who pays, who can log in and what stops if it goes down. If a website health check turns up something this map missed, the map is wrong.
Risk list
Each risk in a plain sentence, how bad it would be, what fixing it costs and one person's name beside it. Risks without an owner are decoration.
Roadmap
What happens now, what happens next and what you have decided not to do. The last list is the one that saves money.
Vendor scorecards
What each vendor was paid, what it promised, what it delivered and the recommendation: keep, fix, replace or stop. The same columns for everyone.
Backup test record
The date a backup was restored, what came back, how long it took and who did it. Being told that backups run is a different document, and a less useful one.
A sample monthly page, with every number invented
Here is the one page an owner should get each month. This sample continues the made-up roofing company, and no number on it comes from a real business.
| This month | Plan | Note | |
|---|---|---|---|
| Vendors, licenses and cloud | $11,400 | $12,000 | Dropped nine unused seats |
| Freelance developer | $4,200 | $3,500 | Quote tool change ran over; see the specification |
| Managed IT company | $2,100 | $2,100 | Restore test passed on the second try |
| Open high risks | 3 | 2 | Former employee's admin login still being traced |
| Last successful restore | This month | Quarterly | Ninety minutes, payroll export included |
Read it the way you would read a job cost report. Each line has a dollar or a date. There is no "digital maturity score" and no chart of a number nobody can define. If anyone hands you something prettier that you cannot act on, ask for this instead. The marketing version of this role reports the same way on that budget.
Requests a good lead turns down, even from the person paying
- Calling the product AI-powered on an investor slide when it is not. Sooner or later someone technical reads the code. A lead will help you describe what you have.
- Promising a customer that a breach cannot happen. Nobody can sign that honestly. A lead can describe the controls in place and who owns them.
- Keeping the admin passwords in the lead's own account. Credentials live in a company-owned manager. Anyone who wants them held personally is building a hostage situation, even if by accident.
- Skipping the specification because the change is small. Small changes without a written description are where the "we'll fix it later" bills come from.
- Taking an undisclosed referral fee from a vendor they recommend. Without disclosure, the recommendation means nothing.
- Signing a security questionnaire for something never tested. Saying "we do not know yet" costs a little. A false answer can cost much more.
A good lead should also tell you when the answer is to do nothing. A working system that is merely old is often better left alone, with a backup and a written owner. The itch to rewrite is strong in this profession, and it has paid for a lot of boats.
The same job with Casey Kinnison in the seat
At DataCram, Casey Kinnison holds the fractional CTO seat for hours agreed before work starts. You name a point of contact on your side. There is a standing weekly or biweekly meeting, a written plan and the monthly page shown above. The seat starts at $5,500 for 15 hours a month.
Casey worked as a trader, and it shows in the risk list. Each line is treated like a position: how large it is, what gets you out, and what the actual number says today. A sole developer or a sole copy of the data is a position nobody meant to take at that size, and it goes on the list as one.
DataCram also offers web app development, an API integration that goes live the same day, workflow automation and AI integration. Published prices sit on the pricing page.
Questions owners ask about a fractional CTO
Sometimes, but it should not be the main thing you pay for. The role reads code, reviews it and writes specifications so other people can build well. If you mostly need more hands, hire a developer. Casey Kinnison is DataCram's lead developer and can write the code, but the seat and the hands-on work are separate purchases.
At minimum, a first version of the systems map, a list of who owns which accounts, a short risk list, an honest answer on whether backups restore, and one monthly page of numbers. The full roadmap usually comes later, because it depends on what the audit finds. Be wary of a polished strategy deck in week two.
Usually the owner or general manager, with one point of contact on your side handling logins and scheduling. Reporting to someone below the person who signs the budget tends to fail, because the lead ends up recommending things nobody present can approve. A standing weekly or biweekly meeting keeps decisions from drifting between invoices.
The basics, yes: a written owner for each control, patching, multifactor logins, access reviews and tested backups. Deep work such as penetration testing or incident forensics usually goes to specialists the lead helps select and manage. No fractional leader can guarantee you will not be breached, and DataCram does not offer that guarantee.
A consultant is usually paid for advice on one question and then leaves. A fractional CTO holds ongoing authority over the plan, the budget and the vendors, attends a standing meeting and answers for what happens next month. If you only need one question answered, hire the consultant. It will cost less.
Yes. Distance matters less than having written specifications, a repository you own, a place where you can see the working software, and invoices tied to finished items. Those same controls apply to the developer down the street. Casey Kinnison can review the code, run the meetings and tell you honestly whether the arrangement is working.
Keep reading
- Technology audit checklistFractional CTO First 90 Days: A Technology Audit Checklist and RoadmapWhat a fractional CTO should do in the first 90 days: inventory, access, a backup restore test, the NIST functions, first vendor decisions and AI rules.
- CTO vs IT companyFractional CTO vs MSP or Dev Shop: Who Fixes It, Who Builds It, Who DecidesFractional CTO vs MSP vs dev shop: what each is paid to do, what none of them owns, and why the party writing the code should not be the one grading it.
- CTO as a service pricingFractional CTO Cost: What the Published Rates Say and What They Leave OutFractional CTO rates: one vendor's published range, the hours math, the bills that arrive later and our own price, from $5,500 for 15 hours a month.
- Do I need a CTOFractional CTO vs Full-Time CTO: The Math, the Exceptions and the HandoffFractional CTO vs full time: federal pay data and the benefits math, when a full-time hire clearly wins, and how to hire a first engineering lead.
- CTO for startup foundersFractional CTO for Non-Technical Founders: How to Check Work You Cannot ReadHow non-technical founders can check developers' work, who should own the code and accounts, what tech debt means, and what investors will ask you.
- Everything in Fractional CTOSee the section
Find out which of these five documents you already lack
Tell us what you have and what you pay for. A person at DataCram reads it, replies with what looks missing, and says whether a part-time seat would fix it.
Which of these sounds like you? (pick any)
Rather talk now? Call (210) 346-0848.