Tell me where work or information breaks in your business.

What should you tell me in the first message?

The first message needs three things: where the problem shows up, who it affects and what it costs you today. Most people open with the solution they have already chosen, such as "we need a dashboard" or "we need to automate this". A chosen solution hides the problem behind it, and the same request can describe very different situations. What would the dashboard show, and who would act on it? A plain description of what goes wrong lets me look at the work itself instead of the tool.

• Where it shows up: the report, handoff or process where work slows down or numbers disagree.
• Who it affects: the people who spend time working around the problem.
• What it costs: hours, errors, delays or decisions made on figures nobody trusts, even as a rough estimate.
• What you have tried: tools, people or changes that did not hold.

You do not need to know which service you need. Describing the symptom is enough.

What happens after you send it?

After you send the form, I reply with questions about how the work and the information move through your business. The steps are the same each time:

• I read your message: I ask what I need to understand before suggesting anything.
• We talk through the problem: a conversation about where work is copied, retyped or waiting on one person.
• I trace the system: I follow the work and the data from where they start to where they end.
• You get an honest recommendation: what I would change first, what I would leave alone, and whether the problem needs new software at all.

Who do I work with?

I work with growing, data-heavy businesses whose tools, spreadsheets and manual steps no longer fit together. The work usually falls under information systems, automation, infrastructure, knowledge graphs, data liquidity or predictive analytics. You can read about how I work or look at all the services before you write.