Have a pursuit, a dataset, or a deadline?
Thirty minutes is enough to tell you whether I'm the right fit and roughly what it would take. No pitch.
Or send a note
A couple of lines on the problem and the data you have is plenty.
Questions people usually ask first
How do you price work?
Fixed-scope projects get a fixed price after a short scoping call. Fractional and embedded work is billed weekly or hourly. I'll tell you on the first call roughly what your problem would take — no proposal theater.
Do you work through consulting firms, and under NDA?
Yes. I regularly subcontract to firms on their paper, under their brand, with their PM cadence — including client-facing workstream lead roles. NDAs are standard; send yours or I'll send mine.
Remote or on-site?
Remote by default, based in Northern Virginia on Eastern time. I travel for kickoffs, steering-committee readouts and anything where being in the room changes the outcome.
What do I need to have ready?
Less than you'd think. A clear business question and a sense of what data exists is enough to scope. If the data is messy or scattered, that's usually part of the work, not a reason to wait.
What does a typical engagement look like?
Scope (one to two weeks), build with weekly readouts, and a documented handoff to your team or the client's — with an optional retainer for iteration. Most first engagements are a focused four-to-eight-week project; many turn into a fractional relationship.
Do you lead, or build?
Both, on the same engagement. I'll run the stakeholder side — scoping, cadence, executive readouts — and write the code myself. If you already have a lead, I'm comfortable slotting in purely as the senior modeler.