JasonFlatford

Available now

When nobody can make the call

If you are responsible for something and there is nobody who can own its technology, I take that seat.

I come in as the technical owner. I make the calls, I do the work, and I am accountable for whether it ships.

What that usually looks like

A stalled project.
It has not moved in months. Everyone has a reason and nobody has a plan.
A decision that is yours to make and impossible to make.
You have the authority. You do not have the basis. The people advising you disagree and you cannot referee it.
A CTO-shaped hole.
Someone left, or there was never anyone, and the work does not stop to wait for a hire.

How it works

Remote. I scale to the problem: some of these need two days a week, some need all of them. It runs for as long as the problem takes, not for a fixed number of weeks, because nobody knows at the start how long it takes.

What this costs

It depends on how much of the week the problem takes, and nobody knows that at the start.

Tell me what is stuck and I will give you a number before you commit to anything.

What you have when I leave

  • The thing actually shipped.
  • A written record of what was decided and why, so nobody re-litigates it in six months.
  • Someone on your side who can carry it forward.
  • A straight account of what is still broken and what it will cost.

That last one is not a formality. You will get an honest list of what I did not fix.

Who this is for

Mostly people running mission-driven work with more mandate than technical support. Civic projects, nonprofits, founders without a technical co-founder, people who own a project outright. It is not defined by the size of your organization. Some of the people I have done this for do not have one.

Tell me what is stuck

Describe it in a paragraph. I will tell you honestly whether I can help, and if I cannot I will say who might.

Describe what is stuck
Press Esc to close • ⌘K / Ctrl K to open