<?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/">
  <channel>
    <title>The alstro blog</title>
    <link>https://alstro.co/blog/</link>
    <description>Straight answers about websites, apps, AI agents and automation, for business owners.</description>
    <language>en</language>
    <lastBuildDate>Thu, 05 Nov 2026 12:00:00 GMT</lastBuildDate>
    <atom:link href="https://alstro.co/blog/feed.xml" rel="self" type="application/rss+xml" />
    <atom:link href="https://pubsubhubbub.appspot.com/" rel="hub" />
    <item>
      <title>Do you need an app, or is a website enough?</title>
      <link>https://alstro.co/blog/app-or-website/</link>
      <guid isPermaLink="true">https://alstro.co/blog/app-or-website/</guid>
      <pubDate>Thu, 05 Nov 2026 12:00:00 GMT</pubDate>
      <category>Mobile apps</category>
      <description>Most businesses need a website first. An app earns its place when customers come back often, need to sign in, or need what only a phone does well: notifications, the camera or their location.</description>
      <content:encoded><![CDATA[<p><img src="https://alstro.co/blog/covers/app-or-website-661dc0d7.jpg" alt="" /></p>
<p>It’s one of the first questions a business owner asks once customers start wanting more: do we need an app? For most businesses, the honest answer is to start with the website. For some, the app comes later. It depends on how your customers use you, not on what your competitors have.</p>
<h2 id="when-a-website-is-enough">When a website is enough</h2>
<p>A website works on every phone and computer without anyone installing anything. Someone searches, taps a link and they’re in. If people mostly find you, read about you and get in touch, a fast <a href="https://alstro.co/web-design/">website</a> does the whole job.</p>
<p>It can also do more than most owners expect. A website can take bookings, payments and forms. It can hold a customer’s account and send email reminders. For most businesses, that covers what customers came for.</p>
<p>Think about how often someone really needs you. A customer who hires a roofer once in ten years won’t install an app for it. A patient who sees a dentist twice a year probably won’t either. They want to find you, trust you and book, and a website does that in a few taps.</p>
<h2 id="when-an-app-earns-its-cost">When an app earns its cost</h2>
<p>An app makes sense when at least one of these is true:</p>
<ul>
<li>Customers come back often, like ordering weekly or checking in daily.</li>
<li>They sign in to see their own things: orders, appointments, points or progress.</li>
<li>You need what only a phone does well: notifications, the camera or their location.</li>
</ul>
<p>A coffee shop with regulars is a good example. People who come in most mornings will keep an app for ordering ahead and collecting points. A gym is another, where members book classes and check in. An app can also be for your staff instead of your customers, like a field crew that needs today’s jobs, site photos and sign-offs in one place.</p>
<p>What these have in common is habit. The app stays on someone’s home screen because they use it all the time. If none of that fits, an app adds cost and one more thing to keep up to date, without bringing in more customers.</p>
<h2 id="what-an-app-costs-beyond-the-build">What an app costs beyond the build</h2>
<p>The build is only the start, and this is the part that surprises people.</p>
<p>An app lives in two stores. Apple and Google both review it before it goes out, and they can ask for changes. New versions of iPhone and Android software arrive every year, so an app needs regular updates to keep working well. Customers also have to download it, so you need to give them a reason and tell them about it: a link on your website, a sign at the counter, a line on your receipts.</p>
<p>A website has none of those steps. You change it, and everyone sees the new version right away.</p>
<p>None of that makes an app a bad idea. It just means the app has to earn its keep.</p>
<h2 id="mistakes-to-avoid">Mistakes to avoid</h2>
<ul>
<li><strong>Building an app because a competitor has one.</strong> Ask how many of their customers actually use it. An app nobody opens does nothing for you.</li>
<li><strong>Building the app before the website works.</strong> New customers still find you through search. If your website is slow or unclear, they’ll never reach the app.</li>
<li><strong>Copying your website into an app.</strong> If it does the same things as your site, people have no reason to install it. Apple can also turn down apps that are little more than a website.</li>
<li><strong>Expecting downloads on their own.</strong> Apps don’t get found the way websites do. Most people who install yours will be customers you already have.</li>
</ul>
<h2 id="three-questions-to-ask-yourself">Three questions to ask yourself</h2>
<ol>
<li>How often does a typical customer need you? Once a year points to a website. A few times a month starts to point to an app.</li>
<li>Would they sign in to see something of their own? If yes, an app gets more useful.</li>
<li>Is there something you can’t do without the phone itself? Alerts the moment something changes, scanning with the camera and knowing where someone is all count.</li>
</ol>
<p>If you answered no to all three, you have your answer, and it saves you money. If you said yes to one or more, an app is worth a real conversation.</p>
<h2 id="questions-owners-ask">Questions owners ask</h2>
<h3 id="cant-you-just-turn-my-website-into-an-app">Can’t you just turn my website into an app?</h3>
<p>You can wrap a website so it looks like an app, but it rarely feels like one, and the stores may refuse it. If you want an app, it should do something your website can’t.</p>
<h3 id="do-i-need-iphone-and-android">Do I need iPhone and Android?</h3>
<p>Usually yes, because your customers use both. We build one app that runs on both, so you aren’t paying for two separate projects.</p>
<h3 id="does-an-app-cost-more-than-a-website">Does an app cost more than a website?</h3>
<p>Yes, because there’s more to build and more to keep up. How much depends on what it needs to do. We give you one price in the plan, in writing, before any work starts.</p>
<h3 id="will-an-app-help-me-show-up-on-google">Will an app help me show up on Google?</h3>
<p>Not really. Google mostly sends people to websites. You’ll want a good website either way, which is another reason it comes first.</p>
<h2 id="the-usual-path">The usual path</h2>
<p>Most businesses grow into it. The website comes first. When customers keep coming back and asking for an easier way, that’s the sign.</p>
<p>There’s also a cheap way to test the idea. A website can be saved to a phone’s home screen, where it opens much like an app. It won’t replace a real app, but if your customers use it, that tells you something.</p>
<p>We build <a href="https://alstro.co/apps/">mobile apps</a> for that moment, and we’ll tell you plainly if a website still covers it. If you’re not sure who should own what once it’s built, <a href="https://alstro.co/blog/what-should-be-in-your-name/">start with this</a>.</p>]]></content:encoded>
    </item>
    <item>
      <title>What an AI agent can and can’t do for your business</title>
      <link>https://alstro.co/blog/what-an-ai-agent-can-do/</link>
      <guid isPermaLink="true">https://alstro.co/blog/what-an-ai-agent-can-do/</guid>
      <pubDate>Thu, 05 Nov 2026 12:00:00 GMT</pubDate>
      <category>AI agents</category>
      <description>An AI agent can answer the same questions all day, book appointments and follow up, at any hour. It should hand the conversation to a person when money, a complaint or a judgment call comes up.</description>
      <content:encoded><![CDATA[<p><img src="https://alstro.co/blog/covers/what-an-ai-agent-can-do-150b7840.jpg" alt="" /></p>
<p>An AI agent is software that answers your customers in plain language, by chat, text, email or phone, and can take simple actions for them, like booking an appointment. Done well, it covers the hours when nobody is at the desk. Done badly, it annoys the customers you worked hard to win. The difference comes down to what you give it and what you keep for your people.</p>
<h2 id="how-its-different-from-an-old-chatbot">How it’s different from an old chatbot</h2>
<p>You’ve probably used the old kind: a chat box with a few buttons, none of which is what you need. Those follow a fixed script. An AI agent reads what the person actually wrote, answers from what you’ve given it, and can do the next step instead of pointing to a page.</p>
<p>Picture a customer texting at 9 at night to ask if you can fit them in on Thursday. The agent checks your calendar, offers two open times and books the one they pick. It sends a confirmation, then a reminder the day before. When your team comes in the next morning, the booking is on the calendar with the whole conversation attached.</p>
<h2 id="what-it-does-well">What it does well</h2>
<ul>
<li>Answers the questions you hear all the time: your hours, what you offer, where to park.</li>
<li>Books, moves and cancels appointments in your calendar.</li>
<li>Follows up with people who asked for a quote and went quiet.</li>
<li>Takes a message with the details your team needs, so nobody calls back blind.</li>
</ul>
<p>Notice what those have in common. They repeat, the right answer is already known, and waiting costs you. Someone who messages after hours and hears nothing may just try the next business on the list.</p>
<h2 id="what-it-shouldnt-do-alone">What it shouldn’t do alone</h2>
<p>Some moments need a person. A good agent knows them and hands over:</p>
<ul>
<li>Anything about money that isn’t already decided, like discounts or refunds.</li>
<li>Complaints, and anyone who sounds upset.</li>
<li>Judgment calls, like whether a job is safe or a problem is urgent.</li>
</ul>
<p>When it hands over, it passes along the whole conversation, so the customer never has to repeat themselves.</p>
<h2 id="how-a-good-handover-works">How a good handover works</h2>
<p>The handover is the moment most worth planning, because it’s where a customer decides how you treat them. It should go like this:</p>
<ol>
<li>The agent says plainly that a person will take it from here, and when.</li>
<li>Your team hears about it right away, with the whole conversation and a short summary.</li>
<li>After hours, the agent takes the details and says when someone will reply, instead of guessing.</li>
<li>Whoever picks it up can see everything that was said.</li>
</ol>
<p>The customer should feel they reached the right person. They shouldn’t feel they hit a wall.</p>
<h2 id="when-its-worth-it">When it’s worth it</h2>
<p>An agent tends to pay off when these sound familiar:</p>
<ul>
<li>Calls and messages go unanswered, because your team is busy or the doors are closed.</li>
<li>Your team answers the same few questions all day.</li>
<li>Bookings or quotes are a big part of how you make money.</li>
</ul>
<p>If you get a handful of messages a week and answer them all yourself, you probably don’t need one yet.</p>
<h2 id="what-it-needs-from-you">What it needs from you</h2>
<p>An agent only knows what you give it. Before it talks to a single customer, it needs:</p>
<ul>
<li>Your hours, your services and the answers to your most common questions.</li>
<li>Access to your calendar, so it books real openings.</li>
<li>Your rules: what it can do alone, and what always goes to a person.</li>
<li>A sense of how you talk to customers, so it sounds like your business.</li>
</ul>
<p>Most of that is writing down what your team already knows.</p>
<h2 id="mistakes-to-avoid">Mistakes to avoid</h2>
<ul>
<li><strong>Letting it guess.</strong> When it doesn’t know something, it should say so and pass it on.</li>
<li><strong>Hiding the way out.</strong> Anyone who asks for a person should reach one, without a fight.</li>
<li><strong>Pretending it’s human.</strong> Tell people they’re talking to an AI assistant. It’s honest, and in some places the law asks for it.</li>
<li><strong>Starting with everything.</strong> Ten jobs at once means ten things to fix at once.</li>
<li><strong>Setting it up and walking away.</strong> Read the conversations, especially in the first few weeks. That’s how you find what it’s missing.</li>
</ul>
<h2 id="questions-owners-ask">Questions owners ask</h2>
<h3 id="will-it-say-something-wrong">Will it say something wrong?</h3>
<p>It can, if it’s set up loosely. That’s why it should answer only from what you give it and hand anything else to a person. You can read every conversation and change what it knows at any time.</p>
<h3 id="does-it-replace-my-front-desk">Does it replace my front desk?</h3>
<p>No. It takes the calls and messages nobody could answer, at 2 AM and at lunch, and hands the rest to your people. It also takes the same questions off their plate, so they have more time for the customers in front of them.</p>
<h3 id="which-channels-does-it-work-on">Which channels does it work on?</h3>
<p>Text, website chat, email and phone. It can run on one of them or all of them, and most businesses start with the one customers use most.</p>
<h3 id="what-does-it-cost-to-run">What does it cost to run?</h3>
<p>It depends on how much it handles. Our plan tells you the monthly cost before we start. It stays in your accounts, so you see every bill.</p>
<h3 id="will-customers-hate-it">Will customers hate it?</h3>
<p>People hate being stuck. They don’t mind a fast answer. If it replies right away and gets them to a person when they need one, it helps more than a voicemail does.</p>
<h2 id="where-to-start">Where to start</h2>
<p>Pick the one question your team answers most, and let the agent take that first. Once it handles it well, add the next one. That’s how we set up <a href="https://alstro.co/ai-agents/">AI agents</a>: one job at a time, with you able to read every conversation. If you’re still deciding what to build first, <a href="https://alstro.co/blog/app-or-website/">start here</a>.</p>]]></content:encoded>
    </item>
    <item>
      <title>What should be in your name when someone builds your website</title>
      <link>https://alstro.co/blog/what-should-be-in-your-name/</link>
      <guid isPermaLink="true">https://alstro.co/blog/what-should-be-in-your-name/</guid>
      <pubDate>Thu, 05 Nov 2026 12:00:00 GMT</pubDate>
      <category>Websites</category>
      <description>Everything your website runs on should be in your name from day one: the domain, the hosting, the code, the email and your Google profile. Whoever builds it should be a guest on your accounts, never their owner.</description>
      <content:encoded><![CDATA[<p><img src="https://alstro.co/blog/covers/what-should-be-in-your-name-fa67154b.jpg" alt="" /></p>
<p>Most owners find out who really owns their website on the worst possible day. The person who built it stops answering, the bill for the address goes unpaid, or a new designer asks for a login nobody has. By then, getting it back can take weeks.</p>
<p>It doesn’t have to go that way. A website runs on a handful of accounts, and each one can be in your name from the start.</p>
<h2 id="why-it-matters">Why it matters</h2>
<p>When the accounts are yours, you can change who works on your site the same afternoon. You add the new person, remove the old one, and nothing goes down. When the accounts belong to someone else, they hold your website, your email and sometimes your place in search with them.</p>
<p>This isn’t about distrust. Good builders move on, retire or get busy. Owning the accounts simply means your business never depends on one person staying around.</p>
<h2 id="the-six-things-to-own">The six things to own</h2>
<ol>
<li><strong>The domain.</strong> Your address, like yourbusiness.com. It should be registered to you, with your email on it, and set to renew on your card.</li>
<li><strong>The hosting account.</strong> Where the site lives. You own the account and invite the builder in.</li>
<li><strong>The code and the content.</strong> The files, the words and the pictures. Ask for a copy you can keep, or keep them in an account you own. If your site is on a website builder, ask what you can take with you if you leave.</li>
<li><strong>Your email.</strong> If your email runs on your domain, the account behind it should be yours too, so nobody can switch it off.</li>
<li><strong>Your Google profile.</strong> The listing people see on Maps and in search. You should be its owner, with the builder added as a manager if they help.</li>
<li><strong>Your analytics.</strong> The numbers on who visits. They belong to the business, not to whoever set them up.</li>
</ol>
<h2 id="how-to-check-what-you-own-today">How to check what you own today</h2>
<p>You can check most of this in an afternoon. The test is simple: can you log in yourself?</p>
<ul>
<li><strong>Domain.</strong> Search your inbox for a renewal notice. If you’ve never seen one, it’s probably going to someone else. Public lookups often hide the owner now, so logging in is the surest test.</li>
<li><strong>Hosting.</strong> Find out who gets the bill and whether you have your own login.</li>
<li><strong>Email.</strong> Find out who the main admin is. If it’s a past employee or your builder, change that first.</li>
<li><strong>Google profile.</strong> Open your profile and look at who has access. You should be listed as the primary owner.</li>
<li><strong>Analytics.</strong> Log in and check that you’re an administrator.</li>
</ul>
<p>If you can’t get into something, treat it as not yours yet, and put it on the list.</p>
<h2 id="what-to-ask-before-any-work-starts">What to ask before any work starts</h2>
<p>Three questions settle most of it:</p>
<ul>
<li>Whose name will the domain and the hosting be in?</li>
<li>Will I get the logins, and can I remove your access myself?</li>
<li>If we stop working together, what do I get, and how?</li>
</ul>
<p>A builder who means well answers all three in one reply. If the answers are vague, ask again before you pay anything.</p>
<blockquote>
<p>The simple rule: they work inside your accounts. You never work inside theirs.</p>
</blockquote>
<h2 id="mistakes-to-avoid">Mistakes to avoid</h2>
<ul>
<li><strong>Using the builder’s email on an account.</strong> Password resets and renewal notices go to them instead of you.</li>
<li><strong>Using one employee’s personal email.</strong> When they leave, the account can leave with them. Use an address the business controls.</li>
<li><strong>Sharing one password.</strong> Give each person their own login, so you can remove one without changing everything.</li>
<li><strong>Leaving login codes on someone else’s phone.</strong> If the two-step code goes to their number, they still hold the key.</li>
<li><strong>Letting a card expire.</strong> Domains can lapse quietly. Turn on auto-renew and keep the card on the account current.</li>
<li><strong>Assuming that paying means owning.</strong> Custom work doesn’t always belong to the person who paid for it. Get it in writing.</li>
</ul>
<h2 id="if-its-already-in-someone-elses-name">If it’s already in someone else’s name</h2>
<p>Start with the domain, since everything else points to it. Ask the person who registered it to move it to an account in your name. Most registrars have a simple transfer, and the site keeps running while it happens. Then do the same for the hosting and your Google profile, one at a time.</p>
<p>If they won’t answer, Google has a way to ask for access to your profile, and registrars have their own dispute steps. It takes longer, and it depends on whose name is on the record, so start as soon as you can.</p>
<h2 id="questions-owners-ask">Questions owners ask</h2>
<h3 id="is-it-rude-to-ask-for-all-this">Is it rude to ask for all this?</h3>
<p>No. It’s a normal question, and a good builder expects it. You’re not accusing anyone of anything. You’re making sure your business can keep running no matter what happens.</p>
<h3 id="what-if-my-builder-says-its-easier-on-their-account">What if my builder says it’s easier on their account?</h3>
<p>It may be easier for them, but it isn’t better for you. Opening an account in your name takes minutes, and you can invite them in right after.</p>
<h3 id="can-my-builder-pay-the-bills-for-me">Can my builder pay the bills for me?</h3>
<p>Yes, as long as the account stays in your name and you can see it. Paying a bill is fine. Holding the account is the problem.</p>
<h2 id="how-we-handle-it">How we handle it</h2>
<p>When we build a website, every account is opened in the client’s name from day one, and we work as a guest on it. That’s how all our <a href="https://alstro.co/web-design/">websites</a> are set up. If you want to see what that looks like for your business, <a href="https://alstro.co/start/">tell us what you’re building</a>. If you’re still deciding what you need, <a href="https://alstro.co/blog/app-or-website/">start here</a>.</p>]]></content:encoded>
    </item>
  </channel>
</rss>
