Contact
Let's talk about what your system actually needs.
I take on a small number of projects at a time, so I read every message myself. Tell me what the system needs to do, who has to rely on it, and I'll give you a straight answer on whether it's a fit.
matt@matthurley.dev
GitHub
@theantipopau
Matt Hurley
What to include
The faster I understand the real shape of the problem, the faster you get a useful answer.
What the system needs to do
The actual job, not the feature list — what breaks today, or what doesn't exist yet.
Who has to rely on it
Staff, customers, or the public — and what happens if it's unavailable for a day.
Any hard constraints
Governance, budget, timeline, or existing systems it has to work alongside.
What "done" looks like
Even a rough version helps — it's easier to scope a project against a real outcome.