Tell me what you’re working on and what you’d like to make easier. You’ll work directly with me.
Back to articleYou do not need a technical specification to start a useful conversation. Tell me what your business does, who will use the website or application and what problem you want to solve. A good first message describes the current process and the change you want to see. For example, a store may need a clearer stock record, a service business may want faster customer follow-up, or a founder may need a first version of a SaaS product.
Describe the people who will use the system and the actions they must complete. Mention whether customers need to book, buy, request a quote or sign in. If you already have a website, say which pages work well and which steps are confusing. A practical example is more helpful than a long list of technologies.
Tell me if the project needs payments, Google sign-in, dashboards, email notifications or connections with existing business tools. You can include a preferred budget range, target launch period and any devices you need to support. If you are unsure, say so; we can discuss alternatives before deciding what belongs in the initial scope.
We can identify the most important pages and workflows first, then agree on the expected result and how to test it. I will distinguish finished functionality from concepts and planned features. Do not submit passwords, API secrets, private customer databases or financial account credentials through this form. Those require a separate, appropriately secured handover if a project proceeds.
After submitting the form, you will see whether your brief was saved. If email delivery is unavailable, the page also provides a direct email option. Submitting a message is an enquiry, not a contract or a subscription to marketing emails.