Start a project

Share a concise picture of what you're trying to accomplish, what constraints matter, and how we'll know it worked. The more context you give here, the faster we can respond with something useful — usually without another round of basic questions.

About you

Basic context and how we should follow up.

Name, company, and role *

Website / LinkedIn (optional)

How did you hear about us? *

Email for follow-up *

Phone *

The project

Problem framing helps us propose the right solution—not just features.

In one or two sentences, what are you trying to build or automate? *

What business problem does this solve? *

What happens if you don't build it? (optional)

Who are the end users? *

Existing software, systems, or data this needs to work with (optional)

Reference products, competitors, or “something like this” (optional)

Scope & features

Separating must-haves from later wish lists keeps timelines realistic.

Must-have features for v1 *

Out of scope or nice-to-have for later (optional)

AI / automation: input, desired output, and roughly how often it runs (optional — skip if N/A)

Constraints

Budget bands and timeline context reduce back-and-forth.

Budget range *

When do you need this live? What drives that date? *

Is that date flexible or hard? *

Tech stack preferences, hosting, compliance (HIPAA, SOC 2, etc.) (optional)

Success & logistics

Clarity on success and decision-makers prevents stalls later.

How will you know this project was a success? *

Main point of contact on your side, and who has final sign-off? *

Have you worked with external developers or agencies before? How did it go? (optional)

Anything else we should know? (optional)

Fields marked * are required.