MURAGE™
How it worksFeaturesSolutionsUse casesComparePricingLearn
DownloadDownload
MURAGE™

An AI Chief of Staff and a team that does the work. Open source, from Ferrox Labs.

Product

  • Features
  • How it works
  • Engines and apps
  • Privacy and security
  • Pricing
  • Murage Cloud
  • Download
  • Changelog
  • FAQ

Solutions

  • Solopreneurs
  • Founders and startups
  • Agencies
  • Ecommerce
  • Small business
  • Creators and educators
  • Developers
  • SaaS
  • Nonprofits
  • Consultants and freelancers
  • Customer success teams
  • Legal and professional services
  • Small teams
  • Sales teams
  • Operations managers
  • OpenClaw and Hermes
  • Industries
  • Use cases
  • Build your team

Compare

  • vs Claude Code
  • vs Codex (ChatGPT Work)
  • vs Claude (Cowork)
  • vs Paperclip
  • vs OpenClaw
  • vs Hermes Agent
  • vs Manus
  • vs Genspark
  • vs n8n
  • vs Zapier
  • vs Grok Bot
  • vs Meta Muse
  • vs Claude Duet
  • vs OpenAI Dots
  • vs Cue by Manus
  • vs Instinct
  • vs Viktor
  • vs Lindy
  • vs Tasklet

Resources

  • Learn
  • Docs
  • Team library
  • Team gallery
  • Skill library
  • AI Chief of Staff
  • How we test
  • Limits
  • Switching to Murage
  • Open source
  • Blog
  • Community on Discord
  • Release notes

Company

  • About
  • Why trust Murage
  • Press
  • Partners
  • Enterprise
  • Contact
  • Privacy
  • Terms
  • Cookies

© 2026 Ferrox Labs, LLC. Murage is open source under AGPL-3.0. Murage™ is a trademark of Ferrox Labs, LLC.

Getting started · Episode 15 of 17

Rebuild your website

7:25

Chapters

A small florist’s website is stuck in 2019: old prices, clip art and one blurry photo. Put the old site, this year’s price list and her story in one project folder, approve a plan, a design and a mockup, and Murage builds a new site full of her work, with every photo waiting on her OK. Then give it weekly routines that keep it fresh, with nothing going online without her yes.

What you'll learn

  • Put the old site, your current prices and your story in one project folder
  • Ask it to think first, and say what you don’t know
  • Approve the plan, the design and a mockup before the build
  • Every photo made one at a time, each one waiting on your OK
  • A finished site: your products and prices, weddings, a map and hours, a phone layout
  • Check one fact against your own list yourself
  • Make it easy for search engines and AI assistants to understand
  • Weekly routines that keep it fresh, all waiting on your yes
Read the transcript

If your website still shows old prices and an old look, customers notice, and so do search engines. A florist's website, stuck in 2019. Rebuilt into a site that sells her flowers, by an AI team, with her yes at every step. Is your website stuck in another decade? Old prices, an old look, and hard to find. Today, Murage rebuilds it from the files you already have, with today's prices. Then it makes the site easy for search engines and AI assistants to find, and gives it a team that keeps it fresh. And nothing goes online until you say so. Let's do it. Step one: start with what you have. Wren and Willow is a small florist in Hudson, New York. Here's her website today. Scrolling text, clip-art roses, and copyright 2019. The prices page still shows 2019 prices. And the only photo of the shop is blurry, with a van parked in front. Maya sets it up for Rosa, the owner: a new project for the website. Ember leads, and Canvas, the design bot, joins the team. Then point it at the folder with her old site, this year's price list and her story. Everything for the website now lives in one place. Step two: ask it to think first. Rosa knows nothing about websites, and she says so. It's a flower shop, so show the flowers: big photos, prices, weddings, and a map. Before you build anything, really think about what a florist like us needs. Come back with a plan, a design and a mockup. Ember thinks it through, and makes a photo of one of her bouquets for the top, right inside Murage. Then the plan: the pages, the look, the colors and the fonts. A mockup first, to agree the look. The photos come next. Step three: approve, then build. She says yes: build the four pages, flowers first on every page, and keep it all on this computer. Ember builds it one change at a time, each with her Allow once. Four pages, one shared style, and a small preview server, saved in her folder. Step four: the photos. Rosa asks for them one at a time, in one style: soft daylight, the same backdrop, the bouquet big in the frame. Murage makes each photo, and each one waits for her OK. Allow once. The first bouquet. One at a time: every bouquet on her price list, the weddings, the inside of the shop, and Mei's hands at work. When too many came out pink, she asked for new colors, so each bouquet has its own. Step five: the finished site. This season's bouquet up top: the Autumn Harvest, seventy-five dollars, with an Order button. Shop by occasion, each with its own photo. Her bouquets, each in its own colors, with this year's prices. What's in season now. Her weddings. What her customers say. And where to find her: a real map of Columbia Street, her hours, and the inside of the shop. Her flower photos, and a full footer on every page. The Shop page has every bouquet and arrangement from her price list. Each one in its own colors, with its price and an Order button. The Weddings page. A gallery of her wedding flowers, and a booking form that saves each inquiry on her computer. Our Story and Visit: her story, with Mei at work, the map and hours, and answers to common questions. And on a phone, it all fits. Big photos and the same prices, sized for a phone. Try an order. Her own order form: a delivery date, delivery or pickup, and a card message. Place order. And there it is: her order, added to her orders file and saved on her computer. Nothing is sent anywhere. Step six: don't take its word for it. Her 2026 price list: the Autumn Harvest bouquet, seventy-five dollars. And on the site: seventy-five dollars. Step seven: easy to find, so search engines and AI assistants can understand her site. Plain answers to what customers really ask. And a clear title and description for every page, in the page code. Step eight: a team that keeps it fresh. Two weekly routines. Byline drafts a short post about what's in season, and saves it for her to check. Ember checks the prices, hours, links and forms, and changes nothing until she says yes. Nothing goes online without her. The site you're watching this on, murage.ai, was built by Murage, and its team keeps it growing: over three thousand pages and counting. Even these tutorials were made with Murage. Now try it on your own site. Put your old pages, your prices and your story in one folder. Ask it to think first, and say what you don't know. Approve the plan, then the build, one step at a time. Check one fact yourself. Then give it a team that keeps it fresh. So that's your website, rebuilt. One folder, a plain ask, and Allow once at every step. Check a price yourself. Then make it easy to find, and give it a team that keeps it fresh, with every new post waiting on your yes. Next time: finding new clients. See you there. Whatever your business is, a shop, a studio or a salon, you get a modern site that keeps working for you, and you're the one who says yes. Real work, finished. By an AI team you never had to hire. Let Murage handle it. Get started at murage.ai.

Previous, episode 14Work with your spreadsheetsNext, episode 16Find new clients
Download it at murage.ai