Technical direction
What should we do next?
Connect the business problem to a technical decision. Compare the options, make the constraints explicit and decide what is worth building.
Todd Watts / Shell Command, LLC
Through Shell Command, LLC, I help service businesses in finance, quant and tax set technical direction, shape system architecture and build the software.
01Fit
A fractional CTO brings technical leadership to a business without a full-time executive appointment. My work connects that leadership to system architecture and hands-on software development.
That can be useful when the business knows something needs to change, but the technical direction is still unsettled:
These are starting points for a conversation. The right scope depends on your business, your existing team and the decision in front of you.
A fractional CTO fits when technical decisions keep coming up across projects, someone has to connect them to business priorities, and the work does not yet need a full-time executive. If something else is missing, a different arrangement may fit better.
The titles overlap, so ask about the actual responsibilities and capacity. We can start by deciding which arrangement fits.
For the full comparison and a fictional decision memo, read When does a service business need a fractional CTO?
02Responsibility
What should we do next?
Connect the business problem to a technical decision. Compare the options, make the constraints explicit and decide what is worth building.
How should it fit together?
Work through how the parts connect, where data and responsibilities live, and what needs to happen when a dependency fails.
How do we make it work?
Build the software, interfaces and integrations. Bring implementation detail back into the architectural decisions as the work takes shape.
To compare your options before replacing tools, work through a fictional build, buy or integrate decision. To size a first step you can reverse, see how to plan a roadmap before a rewrite.
Considering coding agents for your team? Read about the process, review checks and execution boundaries behind agentic coding.
03Evidence
Public code, original demonstrations and colleagues’ recommendations give you different ways to evaluate my work.
Public source code
A Pi package for shell policy, checkpoints and inspectable status. Read the implementation and its documented boundaries.
Explore MAINFRAMEOriginal engineering demo
Try duplicate requests and failed notifications in a fictional telescope lending desk. All data and scenarios are synthetic.
Try the experimentPublic professional context
Read attributable recommendations about technical skill, communication and working together, with links to LinkedIn.
Read the recommendationsFor professional context, I developed software at Engineered Tax Services from 2018 to 2025, and I work with Jamie Pope as marketing and technology partner for JPOPE Tax Consultancy. Read the career record, or see the public client associations and independent projects. Client entries record the association only.
The code and demonstrations are independent work. They show engineering choices you can inspect, not client systems or claims about client results.
04First conversation
Tell me about
A high-level description is enough to start.
We can discuss the technical responsibilities, the scope of the work and whether fractional leadership or a focused build makes sense.
Book a free 20-minute ops teardownHiring a software engineer for your team? Read my résumé or get in touch about a role.