How we work
How we work. No surprises.
Every MoonRise project follows the same six-phase process — refined across dozens of projects. You'll always know what phase you're in, what's next, and what we need from you.
Discovery
Week 1–2We start with a deep-dive discovery call to understand your business, your audience, and what success looks like. We review your current site, your competitors, and your goals. Output: a project brief that both sides sign off on before any design begins.
Discovery
Week 1–2
We start with a deep-dive discovery call to understand your business, your audience, and what success looks like. We review your current site, your competitors, and your goals. Output: a project brief that both sides sign off on before any design begins.
Strategy
Week 2–3Before we open Figma, we build the strategic foundation: information architecture, sitemap, content hierarchy, and keyword strategy. This is where we decide what pages you need and what each page needs to accomplish.
Strategy
Week 2–3
Before we open Figma, we build the strategic foundation: information architecture, sitemap, content hierarchy, and keyword strategy. This is where we decide what pages you need and what each page needs to accomplish.
Design
Weeks 3–6Full visual design in Figma — desktop and mobile breakpoints for every page. We present designs in a structured review, collect feedback, and iterate. Two rounds of revisions are included in every project.
Design
Weeks 3–6
Full visual design in Figma — desktop and mobile breakpoints for every page. We present designs in a structured review, collect feedback, and iterate. Two rounds of revisions are included in every project.
Build
Weeks 6–10We translate approved designs into production-quality code — Next.js, Tailwind CSS, deployed on Vercel. This is where performance optimization, accessibility compliance, and CMS integration happen.
Build
Weeks 6–10
We translate approved designs into production-quality code — Next.js, Tailwind CSS, deployed on Vercel. This is where performance optimization, accessibility compliance, and CMS integration happen.
Launch
Week 10–11Pre-launch QA checklist: cross-browser testing, mobile review, Core Web Vitals check, content proofread, 301 redirects if needed. We handle DNS migration and go-live. You're not touching a terminal.
Launch
Week 10–11
Pre-launch QA checklist: cross-browser testing, mobile review, Core Web Vitals check, content proofread, 301 redirects if needed. We handle DNS migration and go-live. You're not touching a terminal.
Support
OngoingAfter launch, you're not on your own. Our Care Plans keep your site fast, secure, and up to date. Or we hand off clean documentation if you're taking it in-house.
Support
Ongoing
After launch, you're not on your own. Our Care Plans keep your site fast, secure, and up to date. Or we hand off clean documentation if you're taking it in-house.
Common questions
How do you communicate during a project?
Primarily async via email and Loom videos for design reviews. We do scheduled calls at key milestones — discovery, design review, and pre-launch.
What if I need changes after launch?
We offer Care Plans for ongoing support, or we can scope individual change requests. Nothing gets lost in a black hole.
Do I need to provide copy and images?
Ideally yes — you know your business best. We can recommend copywriters and photographers if needed, and we'll guide you on exactly what we need.
Ready to start?
Book a free 30-minute discovery call. We'll talk through your project, answer your questions, and figure out if we're a good fit.
Book a Discovery Call