DEV Community: Emma Bogmann

How I Rebuilt My Business Website With Revamp

Emma Bogmann — Sun, 18 Oct 2026 13:08:13 +0000

I wanted our website to look like it belonged to the business we were actually running.

We sell specialist services. People need to understand what we do, see that we take our work seriously, and find a straightforward way to contact us. That puts a lot of responsibility on a website, even before anyone sends an inquiry.

I already had a website and a clear idea of the standard I wanted. The useful content needed to carry forward. The presentation needed attention. I also wanted a practical way to make changes after the initial work was finished.

I started with Revamp by bringing in our existing website address. Its AI created a starting design I could review, and I could ask for changes in the same conversation.

That became the most useful part of the experience. I could make decisions about my own business and see those decisions take shape on the page. As the work progressed, I paid attention to the details that would matter to a prospective customer: the images, the readability, the contact process, and how the website behaved on a phone.

Starting with the business I already had

An existing website contains decisions you do not necessarily want to throw away.

There is the way you describe your services, the images you have chosen, and the identity people already associate with you. Starting again should give you a chance to improve those things while keeping what still works.

My early requests were quite specific about preservation. I wanted the existing website brought into the workspace, and I wanted to understand how closely the result could match what was already live.

I learned to treat the first design as something to review carefully. A redesign can use an existing website as its starting point, but the details still deserve attention. I checked what had carried across and pointed out what needed changing.

That gave the project a useful focus. We already had a business to represent. I could spend my attention on making that representation clearer and more professional.

Making the design feel credible

I cared about how the website would feel to someone considering our services.

The typography needed to be consistent. The images needed to fit the work we do. The page needed enough structure for a visitor to understand it without having to work through a wall of information.

Some of my requests were about fairly small details. A logo looked too small. An image needed a different treatment. A heading needed better proportions. I wanted spacing and alignment to feel deliberate across the page.

Those details affect the impression a business makes. An authentic image can explain something about the company. A clear heading can help someone find the service they need. Consistent typography makes the whole website easier to read.

I also wanted to use the real brand assets I supplied. If an image or logo belonged on the website, it needed to appear correctly.

The written claims mattered just as much. I asked for statements about credentials and performance to be checked against what the business could actually support. I wanted a website I could confidently stand behind when a prospective customer looked through it.

Explaining changes and seeing what came back

I could give a simple request when that was enough.

I asked for changes to background colors, supplied a replacement company logo, and asked for it to be made larger. For more involved sections, I shared reference images and more detailed instructions.

I liked being able to work at both levels. Sometimes I knew exactly what needed changing. At other times, I had a reference and wanted help turning it into something appropriate for our website.

There was also a useful distinction between changing one part of a page and changing the whole design. I often wanted to preserve the layout or wording while refining a particular image, section, or visual detail.

Being able to say what should stay helped me keep control of the result.

The work became a sequence of decisions I could review. I would look at a section, explain what felt wrong, and decide whether the next version was closer to what I wanted.

I still needed to be involved. It was our business and our presentation. What made the process approachable was having a direct way to express those decisions and continue refining them.

Giving visitors a clearer way to get in touch

A professional appearance matters, but the website also needs to help someone take the next step.

I spent time on the contact experience because a visitor should be able to understand how to approach us. I wanted the contact area to feel tidy and the form to appear when someone chose to open it.

I also looked at how the service sections connected to that contact process. Someone who has just read about a service should have an obvious way to ask about it.

That changed how I judged the website. I started looking at each section through the decisions a prospective customer would need to make.

Could they find the relevant information? Was the next action clear? Were we asking for more information than we needed at the beginning?

Those were practical questions I could bring into the same conversation as the design changes.

The mobile experience needed its own attention too. I asked for it to be reviewed, along with the navigation and frequently asked questions. Looking good on a desktop did not remove the need to check how a visitor would use the website on a smaller screen.

Working through the details

There were things I asked to change more than once.

Some images needed further adjustment. Logos needed more attention to their size and appearance. I raised questions about navigation and how the mobile layout looked.

I think that is worth saying because an owner needs a realistic picture of what a website project involves.

Seeing a first version is helpful. Reviewing it is where you make sure it suits your business. I looked at the result, gave feedback, and kept asking for the details that mattered to me.

My advice would be to bring your actual images, know which content you want to keep, and check the important parts as you go. If something looks wrong, point to it as precisely as you can.

For me, the value was having a way to keep working through those decisions within the project. I could ask for help, clarify what I meant, and continue shaping the website.

Having a website I can keep improving

I use Revamp on the Grow plan.

For me, the appeal goes beyond getting a design onto a screen. I want to be able to keep working on the website as the business changes.

A service description may need to be clearer. A new image may represent our work better. A contact section may need another adjustment after we have used it for a while.

Those are ordinary business needs. I want a manageable way to deal with them.

Working through this project gave me a process I could return to: review the page, decide what needs attention, and explain the change. I could use our own materials and keep directing how the business was presented.

That sense of control has been a large part of the positive experience for me.

It also changes how I think about the website. It can continue developing alongside the business. I do not have to treat every decision made during the initial redesign as permanent.

I still care about reviewing the result. The difference is that making another improvement feels like a practical next step.

A stronger presence and more customers

Since moving to the new website, I have seen greater visibility for the business and more customers coming to us.

The website has been part of that progress, alongside the work we do and the relationships we build. It gives people somewhere to learn about us and decide whether to start a conversation.

I am more comfortable sharing it because I have been able to shape the details myself. The presentation, the information, and the way someone gets in touch all deserve that attention.

For a specialist service business, I think that confidence matters. Prospective customers may visit the website before speaking to us. I want what they see to support the impression we would give them in a direct conversation.

The improvement I value most is having more control over that first introduction.

I can look at the website from a customer’s point of view and keep asking whether it explains the business well. When I see something that should change, I have a way to act on it.

That has made the website feel more useful in the everyday work of running the business.

What I would tell another business owner

If you already have a website, start by deciding what you want to carry forward.

Gather your real images and logo. Identify the information people need before contacting you. Think about what should be clear on the first page and what deserves more explanation elsewhere.

Then review the design against those needs. Check it on a phone. Follow the navigation. Look at the contact experience as though you were a prospective customer visiting for the first time.

My experience with Revamp has been very positive because I could stay involved in the decisions without having to handle every part of building the website myself.

I could bring an existing website, describe what I wanted, provide references, and keep refining the result. That made a substantial project easier to approach and gave me more confidence in what we were putting in front of customers.

If you are considering a similar move, you can start with your existing website on Revamp. Bring the parts that represent your business well, and take the time to improve the parts that need attention.

How to review a website template before you customize it

Emma Bogmann — Sat, 17 Oct 2026 13:21:54 +0000

A website template can look finished while still containing sample content and demonstration links. Before customizing it, separate what the design shows from what a real visitor will need to do.

This walkthrough uses the public Revamp med spa website template as a worked example. Its demo brand is FORMA. This is a review of the public example, not a report about a real clinic or a completed customer launch.

1. Map the page before judging the design

The example has a hero introduction, an approach section, a treatment menu, a skin-care philosophy section, first-visit information, and footer navigation.

That sequence gives a reviewer something concrete to evaluate: can someone understand the offer, explore the relevant service, and find a next step?

For another business, write the same sequence in ordinary language. A restaurant might need a menu, location, opening hours, and a reservation route. A consultant might need services, evidence, and an enquiry route. Decide what the visitor needs before adding more sections.

2. Inspect the destination behind the action

In the FORMA preview, the main navigation links point to sections on the same page. The hero's starting-point link points to the treatment section, and several consultation links point to the first-visit section.

Those are navigation steps. They do not establish that an appointment has been requested or confirmed.

The final contact link in this public demo uses an illustrative email address, hello@example.com. That is sample content to replace before a real launch. A visual review should catch it before a visitor does.

For each important link, record three things:

The label the visitor sees.
The destination it opens.
The business outcome that should happen afterward.

For example, 'Request a consultation' could open an enquiry form, an email draft, or a scheduling service. Choose the behavior deliberately and make the label match it.

3. Keep design and business setup as separate decisions

The template's catalog page describes appointment tools as possible additions. That wording should not be treated as evidence that a booking account is already connected.

When reviewing any starter design, keep a short list of what is visible, what is sample content, and what needs configuration. This prevents a useful design from being mistaken for a completed business workflow.

Replace the demo business name, service descriptions, imagery, contact details, and any other sample information with content the real business has approved. For a regulated business, the relevant professional should review its public claims.

4. Write acceptance checks for the finished website

These are proposed checks for a customized website, not claims that this demo has passed them:

Area	Check before launch
Navigation	Open every important destination directly and through the page's links
Contact	Send a clearly identified test enquiry and confirm it arrives at the intended destination
Scheduling	If scheduling is added, check the available service, time, and confirmation
Mobile	Review the menu, long text, buttons, and forms on a narrow screen
Keyboard	Reach the important links and controls without a pointer
Content	Search for sample names, contact details, and descriptions that still need replacement

If a check fails, describe the observed behavior and the expected result. 'The contact link opens the sample email address; replace it with the approved enquiry route' is more actionable than 'make the site work.'

What this review establishes

A public preview can show the design, section structure, and link destinations. It cannot establish the results of a customer's launch, the reliability of an untested integration, or whether a website will attract enquiries.

Review the example, customize it for the actual business, then test the completed visitor journey on the published site.

Disclosure: This educational walkthrough was prepared with AI assistance and input from Revamp. It is not an independent customer testimonial. Observations concern the public demo; the launch checklist describes checks to perform, not completed tests.