Article
We Built Our Own Website with AMOS. Here's What We Learned.
How we built softalika.com with AMOS through plain-language requests: real before-and-after examples, what we rejected, and what we'd tell an owner.
Most small business owners know their website could be better. The hard part is knowing what to change, finding the time to change it, and deciding whether the result is good enough to publish.
We build AMOS for businesses without a marketing team, so we used it to build our own sales website, softalika.com. Between 16 and 19 October 2026 we started with the AMOS setup wizard and then improved the site through plain-language requests to the Site Assistant. Each request became a small draft that we previewed on desktop and phone, then approved or turned down. Nothing went live until we approved it.
Here is what changed, what we rejected, and what we would tell another business owner.
What changed on the site?
The setup wizard gave us a working site with every page in place: home, product, about, contact, privacy and cookies. Its words were a starting point. These are real sentences from our site, before and after:
| Where | Before | After |
|---|---|---|
| Home page headline | Marketing work for your website, planned from evidence and published only with your approval. | Your website's marketing team, without hiring one. |
| Line above the headline | AI marketing software | For service businesses without a marketing team |
| Main button | Order now | Request a pilot |
| Contact section | Get in touch for your order | Talk to us about a pilot |
| Reply promise | We will get back to you soon. | We reply within one working day. |
We also added what the first version did not have:
- a three-step "How it works" section, from seeing the evidence to watching what changes;
- five questions owners ask before a pilot, answered on the home page;
- a comparison of AMOS with an agency, a freelancer and do-it-yourself tools on the product page;
- a contact form at the end of the home page, so a reader who gets that far can ask for a pilot without looking for it.
And we took things away. The home page went from eight long feature cards to four short ones; the full list now lives on the product page.
How does a request become a draft?
A request is one sentence in ordinary language, for example "Give the home page a clearer opening" or "Move the AMOS column first in the comparison table, so phone visitors see it". Each request becomes one draft that changes one thing. The panel shows what will change, before and after, with a preview on desktop and phone.
It took us more than 30 small drafts. That number sounds like work; it was the opposite. Each draft took a minute to judge, and a draft we did not like cost nothing: we turned it down and asked again.
What did we reject, and why?
We rejected one draft outright: the first rewrite of our About page. The words were close, but in the preview the bold heading and the list showed up as raw symbols instead of formatted text. We asked for the same section again as formatted text and approved the next version. The preview caught it; no visitor ever saw it.
What did the flagged sentences catch?
When a draft contains a statement that is not in our own words or on our site, AMOS lists it under the draft and asks us to confirm it before we can approve. One example: a draft that renamed our product page also added the sentence "Feel free to get in touch about your order and your questions." We do not take orders. That sentence never reached the live site; a later draft replaced the paragraph.
This matters to us more than any other feature. An assistant that quietly adds claims about your business is a risk; one that shows you every addition is a colleague.
What would we tell another business owner?
- Start with one clear request, not ten. Ask for your home page headline before anything else.
- Read the phone preview. Our comparison table looked fine on a laptop and hid the most important column on a phone.
- Treat flagged sentences as a checklist. If a sentence describes something you do not offer or cannot measure, remove it.
- Expect a few rounds. Small changes you can check add up faster than one big rewrite you cannot.
Want to see what AMOS could improve on your website?
You don't need a marketing team to start improving your website, and you don't need to hand control of it to AI.
A pilot starts with a short conversation about your website, your team and the markets you serve. We then set AMOS up for you, so you can see what it would change, page by page, understand why each change is suggested, and decide what to approve. Each customer runs on their own isolated cloud resources.
Request a pilot and we reply within one working day, or see everything AMOS does.