Start with the workflow
What task would you like to make easier?
Describe the work in your own words. You do not need requirements, wireframes, or technical terminology — a clear account of the task that keeps getting in the way is enough to start from.
Most useful projects begin the same way: someone can describe a recurring frustration precisely, but cannot describe the software that would fix it. That is the normal starting condition, and it is a good one. Figuring out what to build is part of the work.
What happens after you write in
- 1
A focused first conversation. We talk through the task as it exists today — who does it, how often, what the current workaround is, and what breaks when it goes wrong.
- 2
Honest scope and feasibility feedback. You get a direct read on whether custom software is the right answer, roughly what it would take, and what the risks are.
- 3
A practical smallest-next-step recommendation. Sometimes that is a prototype. Sometimes a full build. Sometimes it is a change to an existing tool, or a recommendation to build nothing at all.
Useful things to include
- The task or workflow you want to improve
- How you handle it today — spreadsheets, forms, email, group chats, or an existing tool that almost fits
- Roughly how many people are involved and how often it happens
- Anything that has already been tried and did not work
None of this is required. A single paragraph is fine.
Direct contact
Based in Hamilton, Ontario. Working with clients and collaborators wherever the right problem lives.
Not sure which kind of engagement fits?
See the engagement options or read a case study before describing the workflow.