Your message is in. I will review your project context, tools, and goals, then reply with either a short proposal or a few clarifying questions so we can scope a realistic prototype sprint together.
What happens after you hit send
Review your context
I first read your message in full, note your engine, team size, and timelines, then restate your main design risks in my own words to confirm I understood what you want to test.
Draft a possible loop
Next I sketch a simple experiment loop that could fit your roadmap, including a draft question, scope, and rough sprint length, and I highlight any assumptions or gaps I see.
Share next steps
I then reply with that outline, propose a call or async follow up, and we refine scope together so any eventual engagement stays honest about constraints and expected learning.
Confirm fit and timing
If we both agree the fit is right, we confirm a start window, communication rhythm, and deliverables, then plug the experiment sprint into your existing planning tools.
Usually within two working days
How you can prepare
While you wait, you can gather past prototypes, short videos, or notes that show where your team got stuck. Those artifacts help us skip guesswork and move faster toward a small, honest test. Results may vary, but clear inputs always improve the loop.