# Working with Scott *by: [Scott Booher](https://www.linkedin.com/in/scottbooher/)* My work with growth-stage firms over the years has taken many forms - from complex platform development efforts across many stakeholders, to un-structured retainers covering multiple domains. Here are a few topics that are typically discussed in our intro call: ### Engagement Scope My scope within an organization could be a structured project, such as standing up and managing a large development program internally and with a partner, to an assessment with specific deliverables such as a [[Technical Due Diligence|diligence effort]], to providing a 2nd opinion on an aspect of the current technology team/IP, to simply 'keeping the lights on' between permanent leaders. Regardless of the scope of work, clients can count on my sharing any concerns or risks found that they should be aware of during my partnership with technology staff - a differentiation from typical consulting engagements and a benefit of hiring someone who has been in the CTO seat for many years and can quickly identify material risks. ### Hours Many engagements start with a limited set of hours, and the partnership often expands from there as I am asked to take on additional scope, staffing challenges, vendor management, filling key hires, etc. We therefore have a great deal of flexibility as to initial hours for an engagement, and the try-before-you-scale approach is one of the key benefits of the fractional CTO model. I do ask that we match the engagement hours to the scope and complexity of the work, to ensure a successful outcome. For example, it would not be reasonable to expect to get an organization prepared for its first HITRUST assessment with only a few hours investment by a fractional CTO. When these mis-matches occur I gently share what I believe to be a more realistic estimate for hours/investment to match the hoped-for outcome, and in most cases clients will welcome that feedback. If we are starting out with <40 hours per week, I generally ask that we set expected availability hours early on, so that they can be shared with all company stakeholders and it will be clear when I'll be available for calls, responding to questions and chats, etc. This approach ensures that I am fully engaged and present for each client, rather than context-switching across clients. ### Rates A benefit of not having the overhead of a large firm is that I can price my work with a great deal of flexibility. Short-term engagements of a few hours/week carry the highest hourly rate. That initial rate will drop with extensions to our partnership and longer-term commitments. I am always open to rate discussions should there be a desire to discuss a longer-term arrangement. For those longer engagements with a high personal [Ikigai](https://medium.com/@marenkate/ikigai-and-the-four-ps-how-to-get-paid-enjoy-your-work-solve-problems-and-find-purpose-8c9dc615648f) factor, I'll discount quite aggressively. Examples include engagements with some focus on team mentorship and coaching, maturing processes, vendor/partner evaluation, selection and nurturing, etc... ### Retainers I've completed several retainer agreements and those are often attractive for clients, as we aren't forced to pre-determine every item of scope, and can simply set availability and start working on key issues, strategic planning or whatever is a current challenge - up to the established hours. ### Agreement Template Clients usually like to start with their own [[Master Service Agreements for Fractional CTOs|MSA]] template and I've found that only minor adjustments are needed - where we will work together to define the initial [[Statements of Work for Fractional CTOs|Statement of Work]] content under that MSA. ### Reporting, Invoicing & Terms I typically provide a status email to sponsors each week with key efforts, milestones reached, roadblocks and what's ahead for the following week. I like to invoice every (2) weeks with 30-day terms. > [!tip] Contact Scott Booher > > [email](mailto:[email protected]) > >[linkedin](https://www.linkedin.com/in/scottbooher/)