How We Approach New Projects

One of the most common questions we get is "what's it like to work with you?" People want to know what they're signing up for before they commit. Fair enough.

So here's our process, start to finish. This is how every project goes, with some variations based on scope and complexity.

Phase 1: Discovery

Before we write a single line of code, we need to understand what we're building and why. This starts with a conversation, usually a video call that runs 30-60 minutes.

We'll ask you things like:

• What does your business do?
• Who are your customers?
• What problem are we solving with this project?
• What does success look like?
• What's your timeline and budget?
• Do you have existing brand guidelines, content, or designs?

We also want to see websites you like (and don't like). Not to copy them, but to understand your aesthetic preferences and expectations.

At this stage, we're also evaluating whether we're a good fit for each other. If your project needs something outside our expertise, we'll tell you. We'd rather turn down work than take on something we can't do well.

Phase 2: Proposal and Scope

After discovery, we put together a proposal. This isn't a vague estimate - it's a detailed document that covers:

Scope of work - Exactly what we'll build, broken down by feature. If it's not in this list, it's not included. This prevents the dreaded "I thought that was part of it" conversations later.

Timeline - When each phase will be complete, with specific milestones. We're conservative here - we'd rather under-promise and over-deliver.

Investment - The total cost, payment schedule, and what's included. No hidden fees, no surprise charges at the end.

What we need from you - Content, images, feedback at specific points. Projects stall when clients don't provide materials. We're upfront about when we'll need things from you.

You'll have time to review this and ask questions. We revise until we're both clear on what we're doing.

Phase 3: Design

With the scope locked, design begins. For most projects, this means creating mockups in Figma that show exactly how the final site will look.

We typically start with the homepage and one or two key interior pages. Once you approve these, we extrapolate the design system to the rest of the site.

Feedback happens in rounds:

• Round 1 - Initial concepts. We might show multiple directions if we're not sure which way to go.
• Round 2 - Revisions based on your feedback. Usually the biggest changes happen here.
• Round 3 - Polish and final adjustments. Minor tweaks only.

After three rounds, the design should be locked. Additional revision rounds are possible but may affect the timeline and budget.

For some projects, we skip the Figma mockups and design directly in code. This is faster and means what you see is exactly what you'll get. We'll recommend this approach when it makes sense.

Phase 4: Development

This is where we write the code. Depending on the project, development takes anywhere from a few days to several weeks.

You won't be in the dark during this time. We set up a staging URL where you can see progress in real-time. Every few days, we'll share updates on what's done and what's next.

We build in logical chunks:

• Core layout and navigation
• Homepage and key pages
• Remaining pages
• Interactive features and forms
• CMS integration if needed
• Final polish and optimization

Throughout development, you can test things on the staging site and flag issues. Small bugs or adjustments are expected and don't cost extra. Scope changes - new features or pages we didn't plan for - need to be discussed.

Phase 5: Content Integration

Design and development work best with real content, not placeholder text. Ideally, you provide the final copy before development starts. In reality, content often comes in stages.

We can work with drafts initially and swap in final content later. But the site can't launch until all content is final. This is often the bottleneck, so the earlier you start on content, the better.

If you need help with content, we can recommend copywriters or help with basic content strategy. We're not a copywriting agency, but we can point you in the right direction.

Phase 6: Testing and QA

Before launch, we test everything:

• Cross-browser testing (Chrome, Firefox, Safari, Edge)
• Mobile testing on real devices
• Form submissions and any interactive features
• Performance testing (load times, Core Web Vitals)
• Accessibility review
• SEO checklist (titles, meta descriptions, sitemap)
• Security review

We'll share a list of items for you to review and approve. This is your chance to catch anything we missed before it goes live.

Phase 7: Launch

Launch day isn't as dramatic as it sounds. Because we've been testing on staging throughout, going live is mostly just flipping a switch.

We handle:

• DNS configuration
• SSL certificate setup
• Analytics installation
• Search Console submission
• Final production checks

We typically launch during business hours so we're available if anything goes wrong. 99% of the time, it's uneventful.

Phase 8: Support and Maintenance

The project doesn't end at launch. Websites need ongoing care - security updates, bug fixes, content changes, small improvements.

We offer maintenance packages for clients who want ongoing support. This includes regular updates, monitoring, and a bank of hours for changes. The specifics depend on the site's complexity.

Even without a maintenance package, we're here if something breaks. We stand behind our work.

How Long Does All This Take?

For a typical marketing website with 5-10 pages, expect 4-8 weeks from kickoff to launch. More complex projects with custom functionality can take 2-3 months or more.

The biggest variable is usually feedback turnaround. Fast feedback keeps things moving. Slow feedback extends the timeline.

Ready to Start?

If this process sounds good to you, let's talk. The discovery call is free, no commitment. We'll learn about your project and tell you honestly whether we're the right fit.