Granado is one of Brazil's oldest beauty and personal care brands, founded in 1870 as a pharmacy in Rio de Janeiro. The company sells skincare, perfumery, baby care, and home fragrance across two flagship brands, Granado and Phebo, and ships internationally. Today the group runs more than ten storefronts: Granado, Phebo, Kerenton, the wholesale B2B store, and five international sites. A single internal IT team supports all of them, alongside marketplace integrations and back-office projects.
That team has more important work to do than change the font weight of a submenu. When Camila Marinho joined as e-commerce analyst three months ago, every small request, banner sizes, color tweaks, a missing field on a product card, went into the same backlog. Most of them sat there.
“We have a team that handles at least ten sites, plus marketplace integrations and other projects. It is a small group of POs for a lot of work. When I arrived, I pushed a lot of improvement requests their way, and most of them ended up at the back of the line.”
The setup at Granado was familiar. The e-commerce team would describe what they wanted, the request would join the development queue, and weeks or months later, the change would ship. The process worked, but it was tuned for big projects, not for the steady stream of small content and CRO improvements that an e-commerce operation needs every week.
Two months after joining, Camila opened Decopilot, the AI development agent built into deco.cx Admin, and started doing the small things herself. She calls the agent "the dev." "He is a dev to me," she says.
“Today, any adjustment to the site, content, new component, I do straight from here. The first thing I did was the menu. That was a request that always ended up at the end of the line.”
The clearest moment came during a routine CRO review. Granado's CRO partner joined a meeting with the team and walked through suggestions for the product page. One of them was simple: show the "interest-free installment from R$100" message next to the price, a standard pattern in Brazilian e-commerce that Granado did not have yet.
André, Granado's executive manager, opened Decopilot during the same meeting. Ten minutes later, he came back with a screenshot. The change was already implemented on a preview environment, with the product card showing the new installment line. The CRO partner moved on to the next item.
“If we had put that in the IT queue, it would have taken more than a month to go live. He went in, asked the agent, came back, and said: done.”
André's thread is one of many we see from Granado team members. Camila and her colleague Andressa, who runs content updates, account for most of the rest. The site they own is shared with marketing, executives, and CRO partners who can all step in when something small needs to ship.
The list of small wins is long. Most of them would individually look minor in a press release. Together, they describe how a site is actually maintained.
Reducing the mega-menu hero image so it stops overlapping with submenus. Adjusting the spacing between submenu items. Wrapping long submenu titles like "eau de toilette" onto two lines. Changing the menu font to SOFIA PRO in uppercase.
Setting the home carousel interval to eight seconds. Making the mobile video banner play automatically instead of requiring a tap. Testing different banner sizes and locking in the ideal dimensions for desktop and mobile.
Removing the large "ITAÚ PERSONNALITÉ" title above the filters on a single campaign landing page, without affecting any other category page. The pattern is now reusable for future LPs.
A grid banner with every form field the team needed, plus a few the agent suggested. A category banner adapted from an existing component, ready to use across the catalog.
Andressa handling redirects, fixing a blog post URL that pointed to a 404, debugging a GIF that would not render in a banner slot, checking why a benefits ruler icon was missing on the live site.
“I described a grid banner I wanted, gave a few hints about positioning, and he came back with a component that had every field I needed, including a few I had not thought to ask for.”
The agent reads Portuguese, English, and screenshots. Camila writes the way she would speak to a developer sitting next to her.
Granado's IT team kept their weekly review with Camila. Most weeks she now opens the call by closing tickets she had already filed, then resolved herself through the agent.
“Our demand to IT has dropped by more than half. In the last review, I told Roberto, our PO: don't worry about this one, I will publish it myself on deco.”
Granado is preparing a full redesign of the site. The first phase is internal: their UX designer is rebuilding the layout in Figma, with weekly CRO sessions feeding back into the design. Visual updates are something Camila plans to handle herself through the agent. Structural changes will likely stay with their development partners for now.
The team is also moving to deco's new Studio, where the agent accepts screenshots and Figma context as input. Camila has already tested it by uploading a screenshot of a fragrance family component (floral, woody, citrus) and asking the agent to build it. The component was generated, but did not yet surface in the CMS, a frontier issue the deco team is fixing. Once the path is solid, the team will be able to take a Figma frame and ship it as a section.
Another agent on the roadmap standardizes product photo backgrounds across the catalog. Granado was considering re-shooting thousands of catalog images from scratch. They plan to test the agent first to see if the re-shoot is still needed.
“When I started, I figured I would just use the CMS. After one call with Leandro showing me what the agent could do, we have not stopped using it.”
Granado's story is about a quieter kind of change. The kind of work that piles up between roadmap items, that nobody owns, that holds up a site every day, has stopped piling up. The team that owns the site finally owns the site.
Granado didn't change vendors or shrink scope. They put more capacity to act in the hands of the people closest to the brand, and the small improvements stopped waiting in line. If your CMS is the bottleneck for the work your team wants to ship, we'd like to talk.
Subscribe to our newsletter and get the latest updates, tips, and exclusive content delivered straight to your inbox.
