Two doors. Same principal practitioner behind both.
Companies engage directly. Consulting firms bring Steven in on pursuits and client delivery. Either way, the person who scopes the work with your stakeholders is the person who builds it.
Same principal practitioner behind both.
A principal data scientist you can put in front of your CMO
For marketing, growth, product and analytics teams that need consulting-grade insight without the consulting-firm overhead — and someone who will still be there to build it.
- Fractional analytics lead — a retainer for ongoing insight, modeling and team direction
- Fixed-scope project — a segmentation, MMM, churn model or dashboard with a clear handoff
- Embedded practitioner — hourly or weekly inside your team while you hire or scale
Practice-lead-level capacity for pursuits and delivery
I've sat on your side of the table at BCG and Accenture. I know what a proposal needs, what a deliverable has to look like, and how to run a client workstream under your brand.
- Pursuit support — approach, demo assets and proof-of-value builds that win the work
- Client-facing workstream lead — run the data-science track and the stakeholder relationship
- Principal modeler — hands-on delivery alongside your team, on your paper, under NDA
Sized to the question, not the other way around.
Every model below is available to companies and to consulting firms. Pricing is settled on the first call: a fixed price for defined scope, a weekly or daily rate for embedded work.
Fixed-scope project
A defined deliverable — a segmentation, a marketing mix model, a churn model, a dashboard — scoped in a short discovery, priced once, delivered with a documented handoff. The most common first engagement.
Fractional analytics lead
A standing retainer for ongoing insight, modeling and direction of an in-house analytics or marketing team — senior judgment on tap without a senior hire.
Embedded practitioner
Weekly or daily inside your team while you hire, scale or clear a backlog — hands-on data science with the stakeholder fluency to work unsupervised.
Pursuit support
For firms: the analytical approach, capability demos and proof-of-value builds that make a proposal credible — under your brand, on your timeline.
Client-facing workstream lead
For firms: run the data-science track of a live engagement and own the client relationship for it — scoping, cadence, readouts and delivery, on your paper and under NDA.
Advisory and outcome-based
Short advisory engagements to frame, scope and prioritize analytics investments; and, for the right problem, performance-based pricing tied to a measurable result.
Scoped like a consultant. Delivered like an engineer.
Scope
A short discovery with your stakeholders to pin the business question, the data that exists, and what "done" looks like. You get a one-page plan with a fixed price or a weekly rate.
Build
Data engineering, features, modeling and a working interface — with weekly readouts so executives see decisions forming, not status reports.
Hand off
Documented code, monitoring in place, and a walkthrough for whoever owns it next — your team or the client's. Optional retainer for iteration.
What people ask before they engage
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 principal modeler.
Have a customer question, a dataset, or a proposal due?
Thirty minutes is enough to tell you whether I'm the right fit and roughly what it would take. No pitch.