START A CONVERSATION
Send me a scope and a deadline. You will get an honest answer about whether I am the right fit, a fixed price, and a realistic timeline, usually within a day.
WHAT TO INCLUDE
You do not need a technical specification. A few lines covering these gets us most of the way.
What you are building: A paragraph is fine.
The deadline: Real or approximate.
Existing code: Is there a repo already, or is this from scratch?
Who it is for: Your own product, or a client project?
Anything fixed: A platform, a stack, or a constraint I should know about.
WHAT HAPPENS NEXT
A reply, including if I think I am the wrong fit.
A short call if the project looks like a match.
A written scope with a fixed price, before any commitment.
There is no proposal process, no pitch deck, and no follow-up sequence if you decide not to proceed.
COMMON QUESTIONS
If the brief is still rough, that is fine. The first conversation is where we make it concrete.
Usually within a day or two of scope agreement and repo access.
Yes, if the scope is clear. A two-week build is a real project.
Describe the problem rather than the solution. Working out what should be built is part of the conversation.
Yes, as standard, and I will sign yours rather than insisting on mine.
Send the scope and deadline directly.
