In short: send 5–10 lines about your idea and its context. This page tells you exactly what to include and what happens after you send it.
Start a project
You do not need a polished specification to start. A short, honest brief is enough for a first conversation — often 5–10 lines. The clearer the brief, the faster we can tell whether and how a first working version makes sense.
A good brief answers these questions:
- What are you trying to build?
- Who is the user?
- What should the first working version do?
- What systems must it integrate with?
- What data is involved?
- What is sensitive or regulated?
- What does success look like after 2–6 weeks?
Download the project-brief template (Markdown) ↓
What happens after you send it
- I read the brief and reply with an honest first read — including whether I am the right fit.
- If it fits, we schedule a short call to clarify scope and open questions.
- You get a first orientation on scope, risks, and a sensible first working version — before any larger commitment.
Send a project brief→