Skip to main content

Are you a designer or an agency looking for a developer to collaborate with on a custom website project?

How I Work

Step 1: Discuss Project Details

When you have a project in mind, email the details of the client and project scope. We'll assess the development needs while we look at our schedules to see if the project is a good fit.

Step 2: Scope, Contract, Invoicing

I'll send a customized proposal with the full development scope, a contract, and an invoice.

Step 3: Development

When the final design files are ready, send them with any notes on functionality. We'll then set an official development start date and timeline with the client.

Step 4: Revision and Testing

Once I'm finished with the build and have tested things per the scope document, I'll send you a link to the staging server. You'll get a chance to look things over before the client gets eyes on it. This stage allows you to test functionality, provide feedback, and ask questions.

Frequently Asked Questions

I don’t have one. All projects are fixed price, fixed scope. This ensures you know what you’re paying before a project begins.

Expect development costs to start around $3,000. Things could be more depending on functional requirements and the complexity of your design files.

4-6 weeks is enough for a typical project. Depending on functional requirements and the complexity of your design files, things could take longer. And there are other factors like:
— Lack of communication and/or feedback.
— Change in project scope (such as adding more pages or making major design changes after coding has started).
— Failure to pay an invoice on time.

That’s up to you. If you don’t supply anything, I’ll use my best judgment for responsive views. If you have loose opinions about how things should look on mobile, we can just discuss them over the phone. If you have strong opinions, it’s better to include design files at those screen widths.

We can discuss what this will look like, but having direct communication with the client is best for everyone involved. It’s especially beneficial for long-term communication with the client when they need future maintenance and/or support after their site launches.

I build Jekyll sites hosted on CloudCannon.