Submit your problem
You know the frustration. Start there.
What is happening, what is it costing you, and what have you already tried? You do not need to know which software or technology would solve it.
Before we begin
Practical questions.
Straight answers.
Do I need to know what software I need?
No. Describe what happens, where work gets stuck, and what you have already tried. Understanding the problem comes before selecting a tool or writing a technical specification.
How does an engagement begin?
Start by submitting your problem. Andrew reviews the context and determines whether a focused discussion makes sense. Any paid scope, deliverables, responsibilities, and commercial terms are agreed before that work starts.
How do you control project risk?
Define a bounded first scope, test assumptions early, and agree on decision points. We consider disruption, data migration, user adoption, maintenance, and the cost of doing nothing. Expansion should follow a demonstrated business case.
What happens after a system is launched?
Ownership, documentation, support, and future changes should be agreed as part of the engagement. We consider maintainability during design, not just at launch. The specific support arrangement depends on the system and the agreed scope.