Skip to main content
Client Portal

Submitting Feedback & Revisions

Best practices for providing feedback on designs and development work.

Last updated: November 15, 2024

Clear, constructive feedback helps us deliver exactly what you're looking for. Here's how to provide effective feedback.

When to Provide Feedback

We'll request feedback at key milestones:

  • Design mockups: Before we start coding
  • Staging site: When development is complete
  • Pre-launch: Final review before going live

How to Give Great Feedback

Be Specific

Instead of "I don't like this," try:

  • "The headline font feels too casual for our brand"
  • "Can we make the CTA button more prominent?"
  • "The image on the About page doesn't reflect our team's energy"

Reference Locations

Tell us exactly where to look:

  • Page name or URL
  • Section of the page (header, hero, footer, etc.)
  • Screenshots with annotations are incredibly helpful

Explain the Why

Understanding your reasoning helps us propose better solutions:

  • "Our customers are mostly 50+, so we need larger text"
  • "This conflicts with our brand guidelines because..."
  • "Our sales team said customers often ask about X, so we should highlight it"

Revision Process

Each project phase includes revision rounds:

  • Design: 2 rounds of revisions included
  • Development: Ongoing refinements during the build
  • Pre-launch: Final adjustments before go-live

Consolidating Feedback

To keep things efficient:

  • Gather feedback from all stakeholders before submitting
  • Submit all feedback at once rather than piecemeal
  • Prioritize must-haves vs. nice-to-haves

Remember: we're on the same team! We want your website to succeed as much as you do.

Was this helpful?

If you have questions or need clarification, we're here to help.

Contact Support

Explore More Resources

Browse all documentation or check our FAQ for quick answers.