The requests arrived through one Notion form. A password reset. A laptop that needed setting up before a new hire's first day. A partner asking for a report nobody had built yet. One person handled all of it on the side of another job, and for a while that held. Then the queue got long enough to read. The helpdesk volume was steady and predictable, the reporting requests kept coming from the same corner of the firm, and no one person could cover both.
That queue is what the firm's ten-person technology team was eventually built out of, one role at a time, in the order the tickets justified.
Start with a system
When the work piles up, the instinct is to hire. Build the system first. A system shows you what to hire for.
A ticketing system tells you what to hire for before you write the job description.
We started in Notion with one place where anyone in the firm could submit a request, with templates, defined service levels, and a clear lifecycle so nothing got lost and requesters always knew where things stood. Two things came out of that. Support got reliable instead of ad hoc, and every request started leaving a trail. Once all the requests lived in one place, the patterns were hard to miss: what kind of work came in, how often it came in, and where the demand concentrated. That evidence is what justified every hire after the first one.
Grow the team around the work
From one person the team grew to ten, and each role answered a demand we could point at in the ticket queue.
The scope a modern firm requires is broad. In any given week the team handles break/fix support and password resets at one end, and at the other, data analytics and dashboard building, API and system configuration, equipment procurement and endpoint security, identity management, infrastructure and technology capital planning, vendor contract negotiation, data governance, AI process and system implementation, data migration and hygiene, employee onboarding and offboarding, and even HRIS management and bonus payroll processing. The ticketing data is what made all of that legible. You could watch the helpdesk load justify a support hire, and watch the reporting requests justify a data analyst.
The fractional-leadership lesson
You don't need a full-time CTO and a built-out department to start. You need someone who can stand up the system and then keep growing the function as the business grows, using what the system tells them.
That is what fractional technology leadership is for. Build the lightweight structure first, a ticketing system with clear process around it and some way to see demand, then scale the team against evidence rather than budget guesses. It keeps technology spend honest, because every role has to earn its place. And the firm's technology capability grows alongside the firm instead of lurching to catch up after something breaks.
How do you start building a technology team at a firm?
Start with the system. A ticketing system with templates and service levels makes support reliable, and it generates the data that shows you which roles you need, so you scale against evidence instead of guesses.
What does a firm's technology team cover?
At maturity, a lot more than helpdesk. Data analytics and dashboards, security and identity, infrastructure and procurement, vendor and contract management, data governance, AI implementation, onboarding and offboarding, and sometimes HRIS and payroll support.
Do we need a full-time CTO?
Not to start. Fractional technology leadership can stand up the structure and then grow the function in step with the business, reading the demand signals as they show up. Technology spend stays disciplined while capability scales.