Project-based consulting, when advisory isn't the right shape.
Most of the time, the right shape of engagement is advisory: ongoing, open-ended, with someone senior who stays long enough to see changes land. But occasionally a company has a specific, scoped problem. Snowflake bills are out of control. The dbt project has accumulated a year of shortcuts that nobody fully understands. Airflow keeps falling over and nobody has time to properly diagnose it.
This page is for those cases. Not an ongoing relationship. A focused engagement with a clear problem, a clear deliverable, and a defined end.
What I'll actually do
Audit, recommend, and where the engagement allows, implement. The specific things I do most often: Snowflake cost and architecture reviews, dbt project health checks, Airflow stability and design assessments, data infrastructure audits for teams that have outgrown their original setup. Every engagement produces written output, shared with the team, so the value stays after the work is done.
What I won't do
Long-term maintenance. Production code ownership. Anything that looks like a contract development role. If the problem requires someone embedded on the team for months, that's either advisory or a full-time hire.
How to inquire
Email me with the problem, the rough size of the system, and what you've already tried. That's enough to tell whether it's a good fit.
If the problem is bigger than a single project, or you're not sure where to start, advisory is probably the better fit.