Define the result
Describe who will use the website or feature and what they need to accomplish. Explain the current process and where it gets difficult.
Planning your project
Whether you have a working site, an idea for a new feature, or a problem to solve, a few practical details help us plan the next step.
Describe who will use the website or feature and what they need to accomplish. Explain the current process and where it gets difficult.
Send the site address, platform, and version if you know them. Mention important add-ons, customizations, hosting changes, and connected services.
For an integration, name both systems and describe the data that should move between them. API documentation is useful when available.
For new pages or a rebuild, gather your service descriptions, contact details, logo, and any images or testimonials you have permission to use.
Separate the essential requirements from later improvements. Mention deadlines, other people involved, and anything the work depends on.
We’ll discuss the scope and pricing, any investigation required, how changes will be reviewed, and the plan for updating the live site.
Common starting questions
The domain is your website’s address. Hosting provides the server resources that deliver your pages and run any application code. Keep ownership and access details for both.
It depends on how the content will be managed. Regular editing may suit a content management system; a site that changes infrequently may work well as static pages.
Not necessarily. We can review whether a targeted change, a new feature, or a page redesign will address your needs.
Start by describing the work. We can then identify the access required, an appropriate way to share it, and the backup or development copy needed before live changes.
A direct conversation.
Tell me what you want to build, connect, or improve. You’ll work directly with Jeff.
Tell me about your project