01
So we can reach you. Phone and company are optional but help for quick clarifications.
Used only for your request and follow‑ups.
Helpful for short questions. Digits and common symbols only (+, spaces, brackets).
02
Multiple selections are fine, they highlight relevant platforms and skills early.
If several apply, select all that are relevant.
03
Where the solution should run, and whether you prefer a stack or want a recommendation.
Target platform
Where should the solution run or be used?
Technical direction
Optional, choose “Open, recommend” if you want a proposal.
04
In your own words: what should be better in the end. Bullet points are perfectly fine.
One sentence can be enough, direction matters more than polish.
A real‑world example helps: “Right now it takes …”
Fill at least one of “Goal” or “Problem” with a bit of substance (about 30+ characters), enough for an initial assessment.
Priorities over completeness: what must v1 definitely do?
Is there existing material, tool, file, example or sketch?
05
Indicative ranges, not fixed pricing. They help propose realistic options even as details evolve.
Timeline:
If there is no fixed date, leave empty and pick a timeline above.
Estimated scope:
Budget (indicative):
06
How and when we may reach you, including an optional callback window.
So we don’t call at the wrong moment: please indicate whether a phone callback is useful.
Callback requested:
Preferred channel:
If you don’t select an option, we’ll default to email, change this if you prefer phone or video.
07
Finally: consent to process your request and a clear submit action.
Without this consent we cannot process your request, hence it is required.
Submit requirements
Submitting starts a factual review, non‑binding and without automatic obligation.