Ongoing consulting
A senior engineer on your team, a few hours a week.
Not every problem needs a project or a new hire. Sometimes you just need someone experienced around regularly, to steer the developers you already have, keep an important system healthy, or make the calls nobody else on the team is placed to make.
What it usually looks like
- Managing or mentoring your developers
- Weekly check-ins, planning, code review, and unblocking, for an in-house or contracted team that has no senior technical person steering the work.
- Maintaining a system you depend on
- Updates, security patches, monitoring, and fixes for software your business runs on, especially when the person who built it has moved on.
- Architecture and code review
- A second opinion before the big decisions, and regular review so small problems get caught before they compound.
- Someone to ask
- Vendor proposals, technical hires, estimates that don't add up. An experienced engineer who isn't selling you anything.
How it works
- We agree on a weekly or monthly block of hours and what matters most right now.
- I work in your tools: your chat, your repositories, your standups. Your team doesn't change how it works for me.
- The hours move with the work. No minimums and no long-term contract, and if the work outgrows the block, we talk about a project or a fractional CTO role instead.
The rate depends on the hours and the system involved. I'll give you a number on the first call.
Consulting or CTO?
Consulting is help with specific work. A fractional CTO owns the company's technology: roadmap, hiring, budget, and the technical questions investors ask. If you're not sure which you need, say so when you get in touch. It's a common question, and the answer is usually obvious within a few minutes.
Get in touch
Tell me about your team or your system and roughly how much help you think you need. Your first 30 minutes is complimentary.