Your business & audience
Describe what you do, who your customers or users are, and what you want them to understand or accomplish.
Tell us about your next project. We'd love to hear what you're building.
Whether you need a website, software solution, or a fresh visual identity, we're ready to discuss your ideas.
Fill in your details below to prepare an email inquiry.
Describe what you do, who your customers or users are, and what you want them to understand or accomplish.
List the pages, features, design assets, or workflows you need. Include your existing website or platform and examples you like.
Share the target launch date, budget range, available content, and any constraints. Identify who will review and approve the work.
Once your inquiry reaches us, the next step is to clarify your requirements. We may ask for examples, existing assets, or a short discussion before outlining an approach.
The proposed deliverables, assumptions, client inputs, estimated schedule, pricing, review rounds, and any separately priced items.
No. Tell us what you have and what is still missing. Content and approval dependencies will be considered when agreeing on a timeline.
Yes. Describe your expected updates or support needs so they can be included in the proposal or scoped separately.
Use the meeting page when you want to discuss your requirements together. Email is useful when you already have a brief, existing website, reference links, or a list of deliverables to share.
Book a Meeting ↗Suggested subject: your business name + the service you need.
Include links to relevant assets and explain your top priorities. Please avoid sending passwords or confidential access details in an initial inquiry.
You can begin with a plain-language description of what your business does and what you want to improve. If your website is not generating the right inquiries, explain what visitors currently see and what you want them to understand. If a manual process takes too much effort, describe its steps and who is involved.
A useful brief separates essential requirements from preferences. List the pages, functions, or assets you must have, then identify optional ideas. Include any existing platform, brand guidelines, reference examples, or target date that could influence the approach.
If your deadline relates to an event, campaign, or business launch, mention the reason and whether the date is fixed. If content or internal approvals are still in progress, describe their status. This helps identify dependencies before a schedule is proposed.
Share the existing website or tool, the platform it uses, and the content or brand assets available. Links are useful when they can be viewed without confidential credentials.
Explain the current problem and the result you want. A concrete example, such as a visitor being unable to find service details, is more useful than a general request to make everything better.
Identify who will provide feedback and make the final decision. Mention any other stakeholders, procurement steps, or internal reviews that affect the process.
Your inquiry is the start of a requirements conversation. Depending on the project, the next step may be a few clarification questions, a discovery meeting, or a review of the material you have shared. A discussion does not by itself confirm a delivery date or a final price.
Once the requirements are sufficiently clear, the proposed scope can identify deliverables, exclusions, assumptions, milestones, and commercial terms. You can review these details before deciding whether to proceed. Work and change requests are managed against the agreed scope.
The inquiry form prepares an email in your email application. Review the prepared message and send it there to complete the inquiry. Alternatively, email Shaunadams010@gmail.com directly or use the Book a Meeting page.
Start with a non-confidential summary and public links where possible. If sensitive materials are needed later, agree on the appropriate sharing arrangements first. Do not include passwords in the initial inquiry.
Yes. Explain what you need people to do, what is difficult today, and which outcome matters. Examples of the current process are often more helpful than technical labels.
No. The requirements and commercial scope need to be agreed before a project begins. The initial inquiry helps establish whether the requested work and approach are a suitable fit.