<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Mexant blog</title>
    <link>https://www.mexant.com/blog/</link>
    <atom:link href="https://www.mexant.com/blog/rss.xml" rel="self" type="application/rss+xml" />
    <description>Notes from building software for small businesses: what it costs, how it works, and what we shipped. By Itai Rotem, Mexant.</description>
    <language>en-us</language>
    <lastBuildDate>Sun, 15 Nov 2026 12:00:00 GMT</lastBuildDate>
    <item>
      <title>From a parked domain to a shop taking orders: Besamim Perfumes</title>
      <link>https://www.mexant.com/blog/besamim-perfumes-shop-and-back-office/</link>
      <guid isPermaLink="true">https://www.mexant.com/blog/besamim-perfumes-shop-and-back-office/</guid>
      <pubDate>Sun, 15 Nov 2026 12:00:00 GMT</pubDate>
      <dc:creator>Itai Rotem</dc:creator>
      <description>A perfume retailer had 110 bottles, stock in Shopify nobody could buy, and a domain pointing at nothing. What we built for them, the shop and the back office, and why each piece works the way it does.</description>
      <content:encoded><![CDATA[<p>Besamim Perfumes is a perfume retailer. When we started, they had 110 bottles, a Shopify account full of stock that nobody could buy, and a domain pointing at nothing.</p>
<p>That combination is more common than it sounds. The inventory was real and already in a proper system. What was missing was the part a customer touches. So the first job was a shop, and the second was the screen the owner looks at every morning.</p>
<p>Both are running today. The shop is at <a href="https://www.besamimperfumes.com/">besamimperfumes.com</a>, and photographs of both are on <a href="/work/">our work page</a>.</p>
<h2>The shop</h2>
<p>The storefront is built on Next.js and talks to Shopify through Shopify&#39;s own Storefront API. The design decision that matters most is the one you cannot see: <strong>stock and prices are read from Shopify at the moment someone loads the page.</strong></p>
<p>The cheaper way to build a shop is to copy the product list into the website and update it now and then. That works until a bottle sells out, the copy still shows it, and a customer pays for something that is not on the shelf. Reading live means the shop shows what Shopify says, and Shopify is where the owner already keeps stock and prices. Nobody has to remember to update the website as well.</p>
<p>On top of that are the parts every shop needs: a product page per bottle with live stock, price and the notes it is built from, a basket, and a real checkout.</p>
<h2>The trade portal</h2>
<p>Besamim sells to other businesses as well as to the public, and wholesale buyers do not shop the way a retail customer does. They are not picking one bottle for themselves. They are building a case list.</p>
<p>So the shop has a separate trade portal where a wholesale buyer builds that list. A retail customer and a trade buyer want different screens, so they get different screens, on the same shop.</p>
<h2>The picker</h2>
<p>Most people do not shop for perfume by name. They shop for a moment. So the shop has a picker that reads what a shopper types in plain words, something like &quot;something for a date night, under $80&quot;, and suggests three bottles.</p>
<p>The important part is who makes the final choice. <strong>The three bottles are chosen by our own code, from the bottles Besamim actually has, at the prices they actually set.</strong> So the picker cannot offer a fragrance that is not on the shelf, or a price nobody set. A shop assistant that invents a product is a support ticket at best and a refund at worst. This one can only point at the shelf.</p>
<h2>The back office</h2>
<p>The second build is for the owner, not the customer: an ops console that reads their Shopify and their QuickBooks at the same time.</p>
<p>The daily screen answers three questions: what is out of stock, what needs a decision, and what the shop is worth at cost. The console reads both systems to answer them, so nobody has to open two tabs and compare by hand.</p>
<p>The money screen puts the takings from the shop next to income and shrinkage from the accounts. It sits side by side on purpose. A shop&#39;s sales and its books should agree, and where they do not, that gap is where the money questions live. Seeing both on one screen is how you find it, instead of finding it at tax time.</p>
<p>Two rules the console is built around:</p>
<ol>
<li><strong>Nothing changes without a person approving that exact change.</strong> Before the console changes anything in the shop or the books, a person sees exactly what will change and approves it, or it does not happen.</li>
<li><strong>Every change it makes is written to an append-only log.</strong> Entries are added, never edited or deleted. If a number looks wrong six months from now, there is a record of what changed it and who approved it.</li>
</ol>
<p>That is also why you see the console blurred on our work page. It holds one business&#39;s accounts. Every figure on those screenshots is blurred before the picture is taken: their takings, their margin, the value of their own stock. We blurred them rather than swapping in made-up numbers, because a blurred figure is visibly one we chose not to publish, and an invented one would be a lie on a page whose whole point is that the screens are real.</p>
<h2>What a small shop can take from this</h2>
<p>You may not need a custom storefront or a console. But the rules behind them apply to any business selling online:</p>
<ul>
<li><strong>One source of truth for stock and prices.</strong> If your website has its own copy of your products, it will drift. Find out where your site reads its stock from.</li>
<li><strong>Keep AI on a short leash.</strong> If you add an AI assistant to your shop, let it read what customers say, but do not let it make up the answer. Anything it suggests should come from your real catalog, at your real prices.</li>
<li><strong>Put your sales and your books side by side.</strong> If the shop says one figure and the accounts say another, you want to know this month, not next April.</li>
<li><strong>Approve changes, and log them.</strong> Any tool that can change your shop or your books should show you the change first and keep a record after.</li>
</ul>
<p>The shop is built on Next.js, TypeScript, Shopify&#39;s Storefront API and Supabase. The console uses TypeScript, the Shopify Admin API, the QuickBooks API and Supabase. Both run on Railway. The full set of screens is on <a href="/work/">our work page</a>.</p>
<p>If your stock lives in one system, your books in another, and your website in neither, <a href="/#start">tell us about it</a>.</p>
]]></content:encoded>
    </item>
    <item>
      <title>How we made mexant.com readable to Google and AI</title>
      <link>https://www.mexant.com/blog/making-mexant-readable-to-google-and-ai/</link>
      <guid isPermaLink="true">https://www.mexant.com/blog/making-mexant-readable-to-google-and-ai/</guid>
      <pubDate>Sun, 15 Nov 2026 12:00:00 GMT</pubDate>
      <dc:creator>Itai Rotem</dc:creator>
      <description>Our own home page sent search engines zero words. What was wrong, what prerendering is, the numbers before and after, and six checks to run on your own site.</description>
      <content:encoded><![CDATA[<p>Until this month, our own website had a problem we fix for clients: a search engine asking for the home page got an empty box.</p>
<p>Open mexant.com in a browser and you see a full page: the hero, the services with their prices, the work. But that page was built in the browser, by JavaScript, after it arrived. What the server actually sent was a short HTML file with an empty <code>&lt;div id=&quot;root&quot;&gt;</code> and a script tag. We counted the words a program sees when it downloads the page and runs no JavaScript:</p>
<table>
<thead>
<tr>
<th>Page</th>
<th>Words before</th>
<th>Words after</th>
</tr>
</thead>
<tbody><tr>
<td>Home page</td>
<td>0</td>
<td>970</td>
</tr>
<tr>
<td>The work</td>
<td>0</td>
<td>427</td>
</tr>
</tbody></table>
<p>Google can run JavaScript, but it does that later, in a second pass, when it has the capacity. Bing does less of it. Most AI crawlers, the ones that feed ChatGPT search, Perplexity and the rest, do not run it at all. To them, our home page was blank.</p>
<h2>What prerendering is</h2>
<p>A site like ours is made of components: a header, a hero, a price card. Normally the browser downloads those components as code and assembles the page itself. That is fast to build and pleasant to use, and it is invisible to anything that only reads HTML.</p>
<p>Prerendering means we assemble the page once, when we build the site, and save the result as an ordinary HTML file. A visitor, a search engine or an AI crawler asking for the page gets the finished words straight away. The browser then picks up that same HTML and makes it interactive, which is called hydration. Nothing looks different to a person. The difference is that the page now exists before any script runs.</p>
<p>We did it with the tools the site already had. React, the library the site is written in, ships a function that renders a page to a string of HTML. Our build now runs three steps: build the site for the browser, build it again for the server, then run a short script that writes every page&#39;s HTML to disk. No new dependency, no new hosting, no monthly fee.</p>
<h2>The rest of the list</h2>
<p>Words on the page were the biggest fix, not the only one. While we were in there:</p>
<ul>
<li><strong>One table of pages.</strong> Every page now has one entry in one file: its address, its title, its description. Everything below is generated from that table, so a new page cannot be added without them.</li>
<li><strong>A title and description per page, checked.</strong> Ours were typed by hand into each page&#39;s HTML, where one forgotten page goes unnoticed. Now the build writes them from the table, with the tags that decide how a link looks when someone shares it, and adds whatever a page was missing.</li>
<li><strong>A sitemap that lists the site.</strong> Ours listed 1 address. It now lists every page, and it is rebuilt from the table on every build, so it cannot go stale.</li>
<li><strong>Structured data.</strong> A small block of JSON on each page that tells a search engine, in its own format, who we are and where we are. The home page also lists every service with its real price range, the same figures the service cards show, read from the same file.</li>
<li><strong><code>llms.txt</code>.</strong> A plain-text summary of the company, every service and every page, for AI tools that look for one. Before, that address returned &quot;not found&quot;.</li>
<li><strong>Smaller pictures.</strong> The screenshots of our work were loading at full size, about 5 MB on the home page. Phones now get 640 and 1024 pixel WebP copies.</li>
</ul>
<h2>Before and after, measured</h2>
<p>We measure with Lighthouse, Google&#39;s free page audit, on its mobile setting, which simulates a mid-range phone on a slow 4G connection. Scores are out of 100.</p>
<table>
<thead>
<tr>
<th>Page</th>
<th>Performance</th>
<th>SEO</th>
<th>Main content shown after</th>
</tr>
</thead>
<tbody><tr>
<td>Home page before</td>
<td>65</td>
<td>85</td>
<td>17.3 s</td>
</tr>
<tr>
<td>Home page after</td>
<td>98</td>
<td>100</td>
<td>2.2 s</td>
</tr>
<tr>
<td>The work before</td>
<td>71</td>
<td>92</td>
<td>11.7 s</td>
</tr>
<tr>
<td>The work after</td>
<td>99</td>
<td>100</td>
<td>1.9 s</td>
</tr>
</tbody></table>
<p>Performance moves between runs, so we ran the home page three times: 98, 90 and 98. The SEO points we were missing came from five links in a mock-up of a bad website on our home page. They had no address, which a crawler reads as broken links. They are plain text now.</p>
<h2>Six checks to run on your own site</h2>
<p>You do not need to be technical for any of these.</p>
<ol>
<li><strong>Look at what a crawler gets.</strong> In a desktop browser, right-click your home page and choose &quot;View page source&quot;. Search the source (Ctrl+F, or Cmd+F on a Mac) for a sentence you can see on the page. If it is not there, a search engine has to run your scripts to read it, and many AI tools never will.</li>
<li><strong>Ask Google what it has.</strong> Search <code>site:yourdomain.com</code>. Every page you care about should be listed, with its own title and a description that makes sense.</li>
<li><strong>Open your sitemap.</strong> Go to <code>yourdomain.com/sitemap.xml</code>. It should list every page you want found. If it is missing, or lists two pages on a site of twenty, that is worth fixing.</li>
<li><strong>Check each page&#39;s title.</strong> The text on the browser tab is the blue headline in search results. If every page says the same thing, they compete with each other.</li>
<li><strong>Run Lighthouse on mobile.</strong> Open your site in Chrome, open the developer tools (F12), pick the Lighthouse tab, choose Mobile and run it. Below 90 on Performance or SEO, the report tells you why in fairly plain terms.</li>
<li><strong>Ask who your firewall blocks.</strong> Hosting and security services such as Cloudflare can block AI crawlers, and some do it by default. That can be the right call. Just make it on purpose: blocking the crawlers that train AI models is a different decision from blocking the ones that let ChatGPT or Perplexity find you and link to you when someone asks.</li>
</ol>
<p>If the first check fails, the others matter less. A page with no words in its HTML is a page most of the internet cannot read, however good it looks.</p>
]]></content:encoded>
    </item>
    <item>
      <title>What a small-business website costs in 2026, and what drives the price</title>
      <link>https://www.mexant.com/blog/small-business-website-cost-2026/</link>
      <guid isPermaLink="true">https://www.mexant.com/blog/small-business-website-cost-2026/</guid>
      <pubDate>Sun, 15 Nov 2026 12:00:00 GMT</pubDate>
      <dc:creator>Itai Rotem</dc:creator>
      <description>Our real price tiers, from $500 to $3,500 to build and $50 to $200 a month, what each one includes, and the five decisions that move a quote up or down.</description>
      <content:encoded><![CDATA[<p>The question we get first is &quot;how much is a website?&quot;, and the honest answer is a range. This post gives you our ranges, the actual figures we quote, and then the part that matters more: what moves a price within a range, and what pushes a project out of the &quot;website&quot; box altogether.</p>
<h2>Our three tiers</h2>
<p>Every website we build has two prices: a one-time setup fee to build it, and a monthly fee to keep it running.</p>
<table>
<thead>
<tr>
<th>Tier</th>
<th>What it is</th>
<th>Setup</th>
<th>Monthly</th>
</tr>
</thead>
<tbody><tr>
<td>Basic</td>
<td>1 to 5 pages, made for phones, a contact form, the basic SEO set up</td>
<td>$500 – $1,000</td>
<td>$50 – $100</td>
</tr>
<tr>
<td>Standard</td>
<td>5 to 15 pages: a page per service, a blog, image galleries, testimonials, email signup</td>
<td>$1,000 – $2,000</td>
<td>$75 – $150</td>
</tr>
<tr>
<td>Premium</td>
<td>15+ pages or a simple online shop, custom design, booking and payments, a members area</td>
<td>$2,000 – $3,500</td>
<td>$100 – $200</td>
</tr>
</tbody></table>
<p><strong>Basic</strong> is for a business that has no site yet, or one it is embarrassed by: the few pages a customer needs to find you, trust you and get in touch. <strong>Standard</strong> is for an established business with several services, where each service deserves its own page and you want to post news or work. <strong>Premium</strong> is for a business that wants customers to do the whole job on the site: book, pay, buy, log in.</p>
<h2>What the monthly fee is for</h2>
<p>People are often surprised there is a monthly fee at all. A website is not a brochure you print once. It sits on a server, it needs security updates, its forms send email that has to keep arriving, and the business it describes keeps changing.</p>
<p>The monthly fee covers hosting, security, updates and support, and it scales with the tier. On Basic, that means hosting, security updates and small edits each month. On Standard, the monthly updates and content changes are handled for you. On Premium, it is weekly updates, priority support and analytics.</p>
<p>If you would rather host and maintain a site yourself, say so. But price in your own hours, and the cost of finding out your contact form broke three weeks ago.</p>
<h2>The five decisions that move the price</h2>
<p>Two businesses can ask for &quot;a five-page site&quot; and get quotes at opposite ends of a range. Almost always the difference is one of these.</p>
<p><strong>1. How many pages, really.</strong> A page per service is good for customers and for search: someone searching for &quot;emergency plumber&quot; should land on the emergency page, not a list of twelve services. It is also the clearest driver of cost, which is why our tiers are drawn around page counts.</p>
<p><strong>2. Whether the site does work, or only describes it.</strong> A page that says &quot;call us to book&quot; is cheap. A page where the customer picks a time, pays a deposit and gets a reminder the day before is a different build. Booking, payments, a shop and members-only pages are what separate Premium from the rest.</p>
<p><strong>3. Custom design or a proven layout.</strong> A clean, proven layout, set in your colors with your photos, is fast and works. A design drawn from scratch around your brand costs more, and is worth it when looking different is part of what you sell.</p>
<p><strong>4. Who writes the words.</strong> Nothing slows a website down like waiting for the copy. If you have the words and photos ready, the build moves quickly. If you need them written, that is a separate job: our content and SEO rewrite is $800 to $2,500, depending on how many pages and how much needs saying.</p>
<p><strong>5. What it has to connect to.</strong> A site that stands on its own is a website. A site that reads live stock from your inventory system, or writes orders into your accounting, is software. That is the next section.</p>
<h2>When it is not a website any more</h2>
<p>Our website tiers stop at $3,500, on purpose. Past that line a project is usually custom software, and pricing it off a website table would be wrong in both directions.</p>
<p>Examples of where the line falls:</p>
<ul>
<li>A shop selling a few dozen products through a standard checkout: Premium website.</li>
<li>A shop where stock and prices are read live from the inventory system the business already runs, with a separate ordering portal for wholesale buyers: custom software. That is close to what we built for <a href="/blog/besamim-perfumes-shop-and-back-office/">Besamim Perfumes</a>.</li>
<li>A booking page: a website feature.</li>
<li>A back office that reads your shop and your books at once and shows where they disagree: custom software.</li>
</ul>
<p>Custom software starts at $2,000, and we quote it after we understand the scope, not before. Anyone who quotes you a fixed price for custom work in the first five minutes of a call is guessing.</p>
<h2>Add-ons that come up a lot</h2>
<p>These are separate services with their own prices, often added to a site later:</p>
<table>
<thead>
<tr>
<th>Add-on</th>
<th>Setup</th>
</tr>
</thead>
<tbody><tr>
<td>FAQ page</td>
<td>$400 – $1,200</td>
</tr>
<tr>
<td>Testimonial collection</td>
<td>$600 – $1,500</td>
</tr>
<tr>
<td>Instant quote calculator</td>
<td>$800 – $2,000</td>
</tr>
<tr>
<td>Website content and SEO rewrite</td>
<td>$800 – $2,500</td>
</tr>
<tr>
<td>Online booking and reminders</td>
<td>$1,000 – $2,500</td>
</tr>
</tbody></table>
<p>We also run Google Ads for clients, but only on top of a site we built, because sending paid clicks to a page we did not build means buying the blame for it. We price that after a call, and you pay Google for the clicks directly. We never handle ad spend.</p>
<h2>How to compare quotes</h2>
<p>When you have quotes in front of you, ask each company the same four questions:</p>
<ol>
<li>What is the monthly fee, and what exactly does it cover?</li>
<li>Who owns the domain and the site if we stop working together?</li>
<li>Who writes the words, and is that in the price?</li>
<li>Can I see a site you built that is running today, not a mock-up?</li>
</ol>
<p>The last one is the most useful. Every screen on <a href="/work/">our work page</a> is software that is running, photographed, not designed for the photo. If someone cannot show you the same, the price is not the thing to worry about.</p>
<p>If you want a number for your own business, <a href="/#start">tell us what it does</a>. The service explorer on the home page shows the matching options and their prices before you ever talk to us.</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
