Contact
Tell us what you’re trying to build.
A short note about your team, your data, and the decision you’re stuck on is the best way to start. Reach out on GitHub — you’ll hear from the principal, not a sales team.
Austin, Texas
The first note
What to include in the first note
Four short things. No deck, no RFP, no procurement theater — just enough to tell whether there’s a fit.
01
Your team
Who would own the outcome — size, roles, and how technical the room is. This decides whether the work is a prototype, an evaluation, or a read on what to do first.
02
Your data
What you have, roughly where it lives, and who can grant access. You don't need it perfectly organized — knowing the shape of it is enough to start.
03
The decision you're stuck on
The one sentence version. If the answer is “should we build this,” say so; if it's “will this work,” say that. The first conversation works best when the question is sharp.
04
Your timeline
When a decision has to be made. Engagements run in weeks, not quarters — knowing the real deadline keeps the scope honest.
What happens next
A reply from the principal, usually within a couple of days. If there’s a fit, the next step is a conversation about the decision — then a fixed-scope proposal you can read in ten minutes. If there’s no fit, you’ll hear that too, with a pointer to what would actually help.