A website project without a process turns into a string of opinions: someone suggests a color, someone else wants to change the copy, the deadline slips and nobody remembers what was agreed. Process isn't bureaucracy. It's what makes the work predictable for both sides.

Mine is asynchronous and written, in five stages: brief, proposal, build, launch and evolve. I explain each one here, with what you send, what you receive and what gets decided.

Why in writing

I work remotely, with clients in Portuguese, English and Spanish, sometimes across time zones. Writing solves three things at once: every decision is on record, you reply in your own time, and the project doesn't have to wait for a meeting to fit everyone's calendar before it can move.

That doesn't mean refusing to talk. When a call genuinely helps — a decision with many variables, a topic that would take ten messages in writing — I do one. It just isn't mandatory. Brief, proposal, contract, approvals and deliveries go by email, WhatsApp or whatever platform you already use.

1. Brief

You tell me, in writing, what exists today, what should happen and any reference that helps: sites you like, brand materials, copy you already have, the timeline you have in mind. It can be an email, a message or the contact form.

I read it, research your market and reply with the questions that are missing. Sometimes there are two; sometimes fifteen. That exchange ends when both sides can describe the project the same way: goal, audience, pages, what's in and what's out.

2. Proposal

With the brief closed, I send a written proposal with scope item by item, timeline per stage and price. It's a fixed proposal: you know exactly what's included before deciding anything.

For reference, typical timelines are:

  • landing page: 5 to 10 business days;
  • company website: 2 to 4 weeks;
  • site with a blog or content area: 4 to 6 weeks.

The exact timeline for each project goes in the proposal. Payment is in stages: a deposit to start and the balance on delivery, by Pix, boleto or card in Brazil; for clients abroad, by bank transfer, card or PayPal. Once the proposal is approved, the contract goes by email with a digital signature, and work starts with the first payment.

3. Build

Here design and code move together. Instead of approving dozens of static screens and only seeing the working site at the end, I start with a page map and a first designed screen to validate the visual direction. From there, each page is born working, published on a preview link.

You open the link on your phone or computer whenever you can and comment by message: "this headline is too long", "the address is missing here", "I prefer the other photo". Each adjustment shows up in the next version, with a record of what changed. Seeing the real site on your own phone tends to produce more useful feedback than any static image.

The copy is also built at this stage. I write with you: you bring the business knowledge, I organize, edit and make it ready for people and search engines. I go into that work in copy for service websites.

4. Launch

Before going live, I review four fronts: domain, performance, SEO and the layer for AI agents. That includes a title and description per page, structured data, sitemap, speed on mobile, a basic accessibility check and files like llms.txt. The full list is in the checklist for an agent-ready site.

Domain, hosting, repository and credentials stay in your name, with the access documented. If one day you want to continue with someone else, you don't need to ask me for anything.

5. Evolve

Launch isn't the end. An adjustment period is included after delivery, to fix what only shows up with real use. I also show you how to edit the content — in a simple CMS or in files, depending on the project — so day-to-day changes don't depend on me.

After that, the path varies: maintenance, new pages or the next layer of the business, such as an automation, a system or an AI agent. When it makes sense, I suggest the next step in writing. When it doesn't, the site simply keeps working.

What depends on you

The proposal's timeline assumes two things on your side: materials sent at the start (logo, existing copy, domain access if there is one) and feedback on the previews within a reasonable time. It also helps to name one person to approve. When several people comment and nobody decides, the project goes in circles.

None of this takes much time. It only takes answers arriving, even short ones.

If you'd like to start with the first stage, send me your brief in whatever way is easiest for you.

References