Write to us

Write a few lines about the situation. A program that has slipped and nobody is sure by how much. An acquisition closing with a technology integration behind it. A regulatory commitment with a date attached. A process your team keeps running by hand. There is no need to prepare a formal request; a plain description is more useful.

Isaac replies personally, usually within two business days, and proposes a call. The first conversation is typically forty-five minutes to an hour. Its purpose is to understand where things stand and whether independent help would make a difference. It is held in confidence, whether or not anything follows, and a non-disclosure agreement can be signed first if your organisation requires one.

If the fit is right, the next step is a short written proposal: what the firm would do, who would do it, how long it would take, and what it would cost. For consulting work that is usually a time-boxed assessment first, so that both sides can judge the situation before committing to a longer engagement. For software, it is a discovery phase with a defined output.

If the fit is wrong, we say so and, where we can, suggest who might be better placed. Nobody is added to a mailing list, because there is not one.

What helps, if you have it

• The current plan or roadmap, in whatever state it is in
• The most recent status report the executive received
• Any findings or commitments from a regulator or auditor that the work has to address
• A sense of who the sponsor is and who else needs to be involved

None of this is required for a first conversation. It simply makes the conversation more concrete.