VolaVolaMost agencies describe their process in broad, reassuring strokes — "discovery, design, development, launch." Here is what actually happens at each stage in a real project, the honest version with the parts agencies usually skip over.
Discovery is the part clients sometimes want to skip because it does not produce anything visible. It produces something more valuable: a shared understanding of what we are building and why.
In discovery, we ask questions most clients have not been asked before. Who specifically is visiting your site? What do they already believe when they arrive? What objection do they have that prevents them from contacting you? What do your best customers have in common? What do your worst clients have in common?
We also audit what exists: analytics from the old site if there is one, competitor positioning, any research the client has done on their customers. Discovery ends with a brief document that both sides sign off on. It becomes our reference throughout the project when disagreements arise about direction.
Before anyone touches visual design, we map out the structure. What pages exist, what content lives on each page, how users move between pages, where the conversion points are. Wireframes at this stage are deliberately rough — boxes and labels, not design. This is where we catch structural problems cheaply, before they are expensive to fix.
Clients often want to skip this and go straight to "what it looks like." We push back. Fixing information architecture after visual design is built is 5-10x more expensive than fixing it in wireframes. This is where most of the real strategic thinking happens.
Design happens in Figma. We share view access with the client from day one so they can follow along, not just see finished deliverables. The first design round shows one direction at high fidelity for the homepage and one core interior page. We are not presenting three options hoping one sticks. We are presenting our recommendation, backed by the reasoning from discovery.
Revision rounds happen in real-time on video calls where possible. Reviewing design asynchronously through email produces slower, more frustrating feedback than reviewing it together and making decisions in the room.
Development starts from the approved Figma files. We build on a staging environment with a live URL the client can visit and test throughout. We do not show a finished product at the end — the client watches it get built.
Content goes in during development, not after. Waiting until development is complete to think about real copy and images is one of the most common causes of launch delays. We start asking for content at the beginning of the project and use real content wherever possible in design mockups rather than placeholder text.
Before going live, we run through a comprehensive checklist: every page on mobile and desktop, all forms tested and sending correctly, load speed checked, SEO elements confirmed (meta titles, descriptions, canonicals, sitemap), analytics verified, and a full link check for broken URLs.
We also send the staging link to the client for a final review with a clear list of what to check and a deadline for any changes. Open-ended "let me know if anything needs changing" creates drift. A specific review with a specific deadline keeps projects moving.
DNS changes. SSL confirmation. Redirect setup if existing URLs are changing. First 30 minutes after launch are spent confirming everything is working in production. We stay on call for 2 hours after any launch.
The project is not finished at launch. We monitor for broken links that only appear in production, form delivery issues, and any unexpected traffic behavior. Minor fixes in this window are included. The post-launch period is also when we set up or verify analytics and review the first real user session recordings if tools are in place.
The honest part: Even well-run projects have surprises. Content arrives late. A stakeholder has feedback in week 7 that contradicts what was approved in week 3. A third-party integration breaks during testing. What separates good agencies from bad ones is not the absence of problems. It is how problems are handled when they happen.
We work this way with every client. Talk to us and we will walk you through what it looks like for your specific project.
Talk to Vola