How website development works at Manáry: the 4 approvals
The biggest risk in a website project isn’t technical: it’s finding out, in launch week, that the structure wasn’t what the client pictured. Changing a wireframe takes minutes; changing a finished site takes weeks. That’s why we organize development into successive approvals, with the client deciding at every turning point.
Before starting: briefing and access
We gather into a single document the project’s goals, audience, references, visual identity and the access we need — domain, hosting, platforms and tools. It looks like red tape; in practice, it stops the team from working on assumptions.
The four approvals
Approval 1 — Wireframe, timeline and process
We draw the structure of each page: what goes in, in what order and with what goal. Alongside the wireframe, we agree the development timeline and process, with the date of each delivery. You approve the structure and the timeline.
Approval 2 — Layout and structural content
The wireframe takes on the brand’s visual identity. You see the pages designed, with copy and calls to action in place, before development starts. It’s the moment to adjust tone, hierarchy and images.
Approval 3 — Content, products and automations
With the structure built, in go the final content, product setup and the agreed automations: forms, CRM and email tool integration, payment methods and shipping. You validate everything working.
Approval 4 — Final approval and full testing
We test the full journey on mobile and desktop: speed, forms, checkout, tracking events and behavior across browsers. With your sign-off, the project is ready to go live.
After the last sign-off: launch
On launch day, we point the domain, set up redirects from old URLs so rankings aren’t lost on Google, and check Search Console and GA4. In the first weeks live, the team closely follows real visitor behavior.
What you need to have on hand
Briefing checklist
The more items ready at the start, the faster the project moves.
0 of 10 items
Brand and content
Access
For e-commerce
Can I ask for changes after approving a stage?
Yes. The difference is the cost: adjustments within the current stage are natural; changes to stages already approved count as scope changes, with an impact on the agreed timeline.
Who takes care of the content?
It depends on the scope contracted. Manáry can write the copy from the briefing or organize and review the material your team sends.
What happens to the old site?
We map the existing URLs and create the necessary redirects to preserve what has already been earned on Google.
What a wireframe is and why it comes before the layout
The wireframe is the structural drawing of each page, with no colors, photos or visual identity: it shows which blocks exist, in what order they appear and what each one is for. Approving the structure before the visuals separates two conversations that tend to get mixed up — “what needs to be on the page” and “how the page should look” — and stops a debate about color from hiding a missing key section.
How to give feedback at each approval
| Approval | What to assess | What to avoid at this stage |
|---|---|---|
| 1. Wireframe and timeline | Pages, section order, goals and deadlines | Discussing colors, fonts and photos |
| 2. Layout and content | Visual identity, hierarchy, copy and calls to action | Changing the approved structure |
| 3. Content, products and automations | Final information, catalog, forms and integrations | Asking for new pages or features |
| 4. Full testing | Behavior on mobile and desktop, speed and purchase paths | Revisiting layout decisions |
Consolidated feedback — a single list per approval, bringing together comments from everyone involved — speeds up the project more than any other factor.
What happens after launch
Monitoring in the first weeks
Tracking errors, forms, speed and real visitor behavior.
Indexing check
Search Console following the indexing of new pages and the redirects of old ones.
Adjustments with real data
Targeted improvements based on what GA4 and click maps show.
Ongoing evolution
New pages, conversion tests and integration with media and SEO campaigns.
That’s the complete process of Manáry Web Dev & Infrastructure, with the four approvals described on the page.
Frequently asked questions
How long does it take to develop a website?
It depends on the scope, the number of pages and how quickly approvals come. A corporate site usually takes one to three months; each project’s timeline is set at the first approval.
Do I need the copy ready to start?
Not necessarily. The copy can be written by the agency from the briefing or organized from the company’s material; the important thing is to decide that at the start.
Will my team be able to edit the site?
At Manáry, yes. Sites are built so the team can publish pages and content without relying on a developer, with critical areas protected.
What happens to the old site’s SEO?
Old URLs are mapped and redirected to the new ones, preserving what has already been earned in search engines.
Have a website, platform or e-commerce project?
Start with the briefing: we understand the goal and come back with the project’s structure and timeline.
Want to apply this to your business?
Manáry looks at your real numbers — media, website and CRM — and hands back the priorities in order of impact.
Get the next pieces by email
Calculators, checklists and practical guides. No spam, one-click unsubscribe.