Have a project in mind? Fill out the form below or email [email protected].
The fastest way to get a useful reply is to share a little context. If this is for a managed website, include the business name, what you do, where you operate, and any existing website URL. If this is custom software, include the problem you’re trying to solve, who will use it, and what “success” looks like.
After you send a message, I’ll confirm whether I’m a good fit and ask any follow-up questions needed to scope the work. For managed websites, that usually means clarifying services offered, service areas, and the pages you need (home, services, pricing, contact). For custom software, it usually means clarifying data sources, integrations, and constraints like timeline, budget range, and security requirements.
If you’re reaching out about a managed website, it helps to mention what you want the site to accomplish. Examples: “more calls from Google”, “a clean place to send referrals”, “a site that doesn’t break”, or “new pages for new services”. From there we can confirm what pages you need and what content assets (photos, logos, service area list) will make onboarding fast.
If you’re reaching out about custom software, a short description of your current process is ideal. What tool are you using today? Where does the data live? What step is slow, error-prone, or manual? When we understand the workflow, it becomes easier to recommend the simplest approach—automation, integration, or a small app—rather than overbuilding.
If it’s a match, the next step is a short call or email thread to lock down scope and expectations. The goal is to avoid surprises: clear deliverables, clear ownership, and a clear path from “idea” to “working.” If it’s not a fit, I’ll tell you quickly so you can move on without losing time.
You don’t need perfect requirements. A messy first message is fine. The key is enough detail to understand the problem. If you have screenshots, examples of competitors, or a short list of must-haves vs nice-to-haves, include them—those are often more useful than long descriptions.
To keep things simple, I typically communicate in plain language: what’s happening, what I’m doing, what I need from you, and what the next checkpoint is. The goal is the opposite of “black box” work. You should always know where things stand.