Bring a problem.
Let’s work through it.

Bring the prototype, the results and the parts you’re struggling with. In our weekly working session, I’ll help you examine the approach, work through technical decisions and decide what to test next.

Teaching follows the project. One week we might map how information moves between departments. Another might involve comparing models, reviewing code or finding out why a seemingly good answer is wrong.

Between sessions, your team carries the work forward. We agree who will do that work and how much time they can realistically give it before we start.

You need someone who understands and owns the business problem, plus someone able to build and test. They can be the same person. You’ll also need access to approved examples of the work.

For a dealer group, that might be an operations lead working with a developer. For an automotive software company, it could be a product manager and an engineer testing a new customer feature.

Our first conversation covers the project, your team and the help you need. If it looks like a good fit, I’ll set out the scope, schedule and fee. We also agree confidentiality, ownership, access and which tools we’ll use.

Investment is discussed on that call. Any tool subscriptions, specialist development or production integrations are identified separately in the proposal.

Want to understand the approach first? Read about Intent-to-System Engineering or look through the example automotive projects.

I’m exploring a pathway for local university students and interns to join supervised dealer-group projects. They would learn by doing, while your team gets to know their work.