Some things are best made clear before starting.

Audacher is a creative and strategic web development agency for medical device companies. The work is organized into four areas: strategy, content, web design and development, and impact and evolution, with AI across all processes. A project can be an audit, a market analysis, a new site, or all of those together.

Audacher grew out of more than ten years of work in the industry and works across the Spanish-speaking market in Spain and Latin America.

It depends on factors that can't be estimated until we see them: how many products, languages, or markets are in scope, the state of the content, and how much of what already exists can be reused.

A corporate site with the copy already written and a catalog of hundreds of products without product pages are different projects, even if both come in as the same request. That's why we prepare the quote after understanding the situation, separating what we can commit to from what depends on internal decisions. We discuss it in a meeting.

Less than people usually think, and nothing that has to be written from scratch:

• who decides and who validates in each area: Product, Quality, Marketing, technical director;
• the actual product list, even if it's in a messy spreadsheet;
• whatever documentation exists, in whatever state it's in;
• someone who can unblock things when something depends on an internal decision.

What's missing is identified during discovery. Waiting until everything is in order before starting is the most common way to never get started.

By exploring what already exists. The self-assessment gives a first reading; when a deeper look is needed, a digital audit reviews the site, content, channels, and priorities.

It depends on the scope and, above all, on internal approvals. Product, Quality, and Medical Affairs review different things, and their availability usually sets the pace of the project. That's why we don't give a timeline before seeing the material. The schedule distinguishes between what depends on us and what depends on company decisions, and makes that clear from the start.

If there's a fixed date, like a congress or a launch, we plan backward from it and decide what is included and what moves to a second phase.

Yes. Most of the work is asynchronous anyway: gathering information from each team, writing, reviewing, and uploading. What matters is a regular cadence, with a short weekly meeting and a living document where decisions are written down. That way, validation happens as we go instead of discovering misalignment at the end.

Yes. Often there's no need to replace anyone. Audacher can work alongside an agency, a developer, the IT team, or outside specialists when the project needs to connect strategy, content, and digital structure. If responsibilities overlap, that's settled at the start.

It takes time to gather information, decide, and validate. How much depends on the project, and it's included in the scope from the start. Part of the work is precisely making sure those decisions don't have to be repeated every time something new is published.

The company. The site, content, and access credentials all belong to the company. The team is also able to run it: in a real project, the publishing workflow we set up is still running today without us.

To speed up work that would have to be done anyway: organizing scattered material, preparing drafts from the company's sources, checking consistency across hundreds of product pages, and analyzing what people search for on the site. AI is used across every service.

Judgment and validation are human. AI doesn't decide what is true or what can be claimed about a medical device, and anything involving clinical content goes through the appropriate person at the company. AI speeds things up; judgment decides.

No. We handle how information is shown, found, and maintained. What must be published, what can be said about a product, and whether a claim is substantiated are decided by the company's regulatory team.

In practice: we decide where an IFU lives, how it links to its product, and how it displays on a phone, while the client decides whether that IFU can be provided only in electronic form. The product page includes the fields the company needs to show, such as the registration number; which fields are mandatory in each country is defined by its regulatory team. More than ten years in the industry matter in a concrete way: they help us avoid proposing things that can't be implemented later and recognize when a decision needs to go back to the technical team.

No. What happens with a sales opportunity depends on many people besides us, and no one outside Google controls its ranking criteria.

What we do show, with dates and sources, are changes in structure, use, and operations. In a real project, clicks on product pages went from 1,308 to 3,227 and clicks on catalog PDFs dropped from 1,391 to 324, in two equal 39-day windows around the launch. These are organic search figures: paid campaigns were handled by someone else.

It depends on what's falling short. If it's speed, a group of product pages, or measurement, we work with what already exists, using web performance and accessibility or ongoing maintenance and optimization. If the structure can no longer support the catalog, the languages, or the audiences, it makes sense to rebuild it, and sometimes keep the design. The digital audit determines that based on the data.

In a defined sequence. Before anything is moved, an inventory is prepared: every URL with traffic or external links, every PDF Google has indexed, and every language version. Then the redirect map is built. After launch, each redirect is checked all the way to its final destination, and progress is tracked in Search Console.

Catalog PDFs that still get visits are redirected to their product page or linked from it. If there are IFUs with a URL printed on labels or encoded in QR codes, the new site keeps those URLs; which version of the document each one points to is defined by the company's regulatory team.

In a real project, 511 redirects were audited before going live, with none broken. No one outside Google controls what happens in the following weeks; we can make sure no important URL is left without a destination.