James Hobbs Discuss an engagement

Founders and CEOs

A trusted partner for founders

In short

Founders carry decisions that shape the whole company: what to build, who to hire, what to spend and when to bring in a technology leader. I have built and exited a business of my own, so these are founder-to-founder conversations, and I help you build engineering leadership of your own rather than depend on me.

You might recognise this

  • You are making consequential technology decisions without a senior technical voice you trust.
  • You need to hire your first technology leader, or your next one, and want to get it right.
  • An agency or freelancers built the product, and you need to bring it in-house.
  • Investors or enterprise customers are asking technical questions you cannot yet answer.
  • A board meeting, a raise or due diligence is coming, and technology will be under scrutiny.

How we might work together

Examples, not packages. They often overlap within one relationship, and we shape the work together.

See the examples
Founder-to-founder conversations
A regular, candid conversation about the decisions in front of you, before they become expensive.
Hiring your technology leader
Defining the role, assessing candidates and supporting them once they start.
Board and investor conversations
Preparing for board meetings, investor questions and due diligence, and joining them where it helps.
Leading for a while
Fractional or interim CTO leadership while your permanent team takes shape.

Relevant experience

Festicket homepage in 2017
festicket.com in 2017, from the Internet Archive
  • Founded, scaled and sold Fill My Weekend, a profitable events and event-promotion technology business with more than 30,000 members
  • Took over technical leadership at Festicket from the founding CTO, then scaled the team from 3 to 17 Read the case study
  • Technical roadmaps and hiring advice for early-stage SaaS, EdTech and data science startups

He combines very deep technical expertise with something I think is much rarer: a constant focus on the commercial outcome. He is very good at stepping out of the developer mindset and asking, “Does this actually matter to the end user?” That has had a real impact on how we prioritise, build and make technical decisions.

Ivan Finn Founder at AdsDroid and Adigy.ai · James’s client

Read the recommendation in context

He is someone that I would hire and work with again in a heartbeat.

Hoyin Cheung Co-founder and CEO, Remo

Read the recommendation in context

How we start

We start with a focused look at what you’re trying to achieve, what’s getting in the way, and how I could help. From there, we agree whether there’s a useful role for me and what it should involve.

  • Understanding the business and what you are trying to achieve
  • Meeting the people who matter to the work
  • Looking at enough evidence to see where I could be useful
  • Deciding together whether an ongoing role makes sense, and what it should be

Questions

We are pre-product. Is it too early to talk?

Often, yes, for ongoing leadership. You probably need a strong engineer or a product studio first. A conversation can still help you hire well or choose a partner, and I will say plainly if that is all you need.

Will you become our CTO?

Sometimes for a period, as a fractional or interim CTO. The aim is always a leadership team of your own that does not depend on me.

Further reading

How do I know whether my engineering team is performing well?

Look at whether engineering helps customers and the business achieve their goals, delivers changes predictably and keeps the product dependable. Combine outcome measures with delivery and operational evidence, then discuss the constraints with the team. Commit counts, hours worked and a busy roadmap cannot establish performance on their own. Read the full answer

Should we rewrite our software or improve what we have?

Rewrite only when you can explain which business constraint the existing system cannot reasonably overcome and how you will manage the transition. Compare a replacement with targeted improvements and gradual migration. Include the cost of maintaining both systems, rediscovering existing behaviour and delaying other work, not just the appeal of a newer stack. Read the full answer

How should a CEO and CTO resolve disagreements about technology priorities?

Start by identifying the shared business objective and the assumptions behind each position. Separate facts, risks and preferences, then compare realistic options and agree who owns the decision. A useful conversation makes the tradeoff explicit; it does not require either person to pretend the cost or uncertainty has disappeared. Read the full answer