A few questions before we talk.

Take the space you need — the form isn't timed and there's no minimum length. The questions are the same ones we'd ask in the first ten minutes of a fit call. Working through them now means the call itself can move faster.

After you submit, we read every form ourselves. We'll write back within a few days with one of three answers: yes let's book a fit call, not right now and here's why, or here's a question or two before we decide.

The work

What are you trying to build?A few sentences is plenty. The clearer you can be about what the thing is, the better. “An app that does X for Y people” is more useful than “a platform.”

What steps toward building have you already taken?No wrong answer. We're trying to understand what kind of help would actually help.

What does done look like?Not the long-term vision — the first version that's worth using. The thing you'd point at and say “that's it, that ships.”

Who is it for?Specific is better than broad. “The three engineers on our checkout team” beats “engineering teams.”

The shape

Where does the work sit right now?Pick the one that fits best.

Idea, no code yet

Prototype, not in production

In production, working but the next move is unclear

In production, working but parts of it need rebuilding

Other (briefly explain)

Have you tried building this with AI tools already?Either answer is fine. We're trying to understand what you've already learned about the gap.

Yes

What's the timeline?Realistic, not aspirational. If “by end of quarter” is real, say so. If “no rush” is real, say so.

The fit

Why Thrivant?A real question, not a flattery prompt. If the answer is “you came up in a search,” that's fine to say.

Anything else we should know?Optional. Constraints, context, things you don't want to find out about ten minutes into a fit call.

Your emailRequired. We'll write back to this address. We don't share it, and we don't add it to a list.

We keep what you tell us — see what we do with it.