Software architecture and technical advice
Five ways to work with me, from a one-off review to a seat at the table. All of them start with a conversation, all of them end with decisions you can act on, and none of them come with a price list on a website. Scope and pricing follow from the first call.
Investors, before a seed or Series A deal
Technical due diligence
You getA risk assessment of the technology in plain language, in days.
Typical momentThe deck is convincing and nobody on your side has looked at the code.
Teams with a product in production
Architecture and code review
You getA prioritised list of what to change and what to leave.
Typical momentReleases take longer every month, or a rewrite is on the table.
Founders deciding what to build next
Product and technology strategy
You getA roadmap in order, the architecture and stack to carry it, and a written set of decisions.
Typical momentThe roadmap is a wish list, or a decision that is hard to undo is coming up.
Startups without a technical lead
Fractional CTO
You getSomeone accountable for architecture, team and technical decisions, a few days a month.
Typical momentYou have developers but nobody who owns the direction, or an investor is asking who does.
Teams where advice alone will not move things
Hands-on engineering
You getThe critical parts built, or a team unblocked, with product decisions made along the way.
Typical momentA plan exists and the people to execute it do not, yet.
Not sure which one?
Most engagements start with a review or a strategy session, because both produce a written result within days and show how we work together. Fractional CTO arrangements usually grow out of one of them. If you are investing rather than building, the due diligence is the only one you need.
If none of this fits, write me anyway. Half an hour on a call usually settles what the right format is, and sometimes the answer is that you do not need me.