Send me the messy version.
You do not need to write a specification.
- A voice note.
- A screenshot.
- An email thread.
- A spreadsheet.
- A half-formed idea.
- A website that is not working.
- A process everyone hates.
- A problem nobody internally owns.
Start with the outcome
Tell me what you want to be different, who is affected, and what happens if nothing changes. If there is a real deadline, say why it matters. An imperfect description is enough to begin.
Keep the first contact safe
You can describe the material before sending it. Remove personal information from screenshots and examples. The Discuss form is for an initial description, not confidential file upload. We can agree an appropriate channel for a voice note or documents afterward.
What happens next
The first step is to clarify the outcome, constraints, and whether a bounded build, a larger business system, or embedded support is appropriate. A conversation is not a commitment to a project or a promise that every problem needs custom software.
Explore example problems · See engagement modes
Have something you need built, fixed, or figured out?
You do not need a specification. Just tell me what you are trying to make happen.
Using “NEWPHYSICIAN:” in the subject helps me recognize that you found me through the site. The message is editable.
Please describe the outcome first. Do not send patient information, passwords, confidential client records, or private legal documents through an initial inquiry. An appropriate channel can be agreed if documents are needed.