<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Joey Stout on Medium]]></title>
        <description><![CDATA[Stories by Joey Stout on Medium]]></description>
        <link>https://medium.com/@apollorion?source=rss-549929542dd7------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*YM9q4GNpyjNLzd_DSOfGYA.jpeg</url>
            <title>Stories by Joey Stout on Medium</title>
            <link>https://medium.com/@apollorion?source=rss-549929542dd7------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 20 Nov 2026 16:11:38 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@apollorion/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to Plan a Small Business Software Project Without Building Everything at Once]]></title>
            <link>https://medium.com/@apollorion/how-to-plan-a-small-business-software-project-without-building-everything-at-once-15dcf1bdd7f7?source=rss-549929542dd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/15dcf1bdd7f7</guid>
            <dc:creator><![CDATA[Joey Stout]]></dc:creator>
            <pubDate>Thu, 19 Nov 2026 02:27:56 GMT</pubDate>
            <atom:updated>2026-11-19T02:27:56.722Z</atom:updated>
            <content:encoded><![CDATA[<p>A software project can start with one useful idea and quickly become a long wish list. Customers need an easier way to send a request. Then someone suggests accounts, a dashboard, reminders, and reporting.</p><p>Those ideas might be useful. They don&#39;t all need to be built together.</p><p>For a small business, a good starting plan has <strong>one clear outcome, a short list of essentials, and a place to save later ideas</strong>. You&#39;re not trying to build as little as possible. You&#39;re trying to create something useful without committing your whole budget before you&#39;ve learned what customers need.</p><h3>1. Start with one outcome</h3><p>Before listing features, write down what you want people to accomplish.</p><p>“Customers need a dashboard” names something you could build. “Customers need to understand what happens after sending a request” describes a problem you can solve. The second statement leaves more room for a simple answer.</p><p>Ask yourself:</p><p>• Who will use this?</p><p>• What are they trying to do?</p><p>• What should be easier when it works?</p><p>Imagine a hypothetical equipment rental business. Its first project statement might be:</p><blockquote>Help customers send a complete rental inquiry so our team has the information it needs to respond.</blockquote><p>That&#39;s a useful boundary. It doesn&#39;t include instant reservations, payments, or live availability. Those are separate possibilities, not automatic requirements.</p><p>If your statement contains several different goals, choose the most important one for the first version. Save the others for a later decision.</p><h3>2. Plan one complete customer journey</h3><p>A small first version should still let someone finish the main task. Write out the steps in everyday language.</p><p>For our hypothetical rental business, that could mean:</p><p>1. Choose the equipment of interest.</p><p>2. Enter preferred dates and contact details.</p><p>3. Review and send the inquiry.</p><p>4. See a confirmation explaining what happens next.</p><p>5. Let the business access the details and respond.</p><p>That&#39;s a complete inquiry process, even though it isn&#39;t a complete rental management system.</p><p>Now look for gaps. What if someone misses a required field? Will customers understand that an inquiry isn&#39;t a confirmed booking? Can staff find the information they need?</p><p><strong>Small should mean focused, not unfinished.</strong> Clear wording, useful error messages, accessibility, and appropriate privacy and security measures still matter. What those require will depend on the project and the information it handles.</p><h3>3. Make each feature earn its place</h3><p>For every proposed feature, ask:</p><p>• Can the customer finish the main task without it?</p><p>• Does the business need it to handle the request?</p><p>• Does it address an important risk or requirement?</p><p>• Is there evidence of a need, or are we guessing?</p><p>In the rental example, equipment details, dates, and contact information may be essential. Saved favorites and a personalized dashboard may be able to wait.</p><p>Be cautious when a suggestion starts with <em>“while we&#39;re at it.”</em> Something that looks small can bring extra decisions and testing. Accounts, for example, also need ways for people to regain access and understand what information is saved.</p><p>Instead of asking whether a feature would be nice, ask:</p><blockquote>What would stop working in the first version if we left this out?</blockquote><p>If the answer is “nothing essential,” keep the idea, but don&#39;t automatically include it.</p><h3>4. Give later ideas somewhere to go</h3><p>You don&#39;t have to reject a good idea just because it doesn&#39;t belong in the first build.</p><p>Keep three short lists:</p><p>• <strong>Now:</strong> Needed to deliver the chosen outcome.</p><p>• <strong>Next, perhaps:</strong> Worth considering after you&#39;ve learned more.</p><p>• <strong>Not part of this project:</strong> Outside the current goal.</p><p>For each later idea, note the problem it would solve and what would make it worth revisiting.</p><p>Instead of writing “add accounts,” try “consider accounts if returning customers struggle with entering the same details again.” That turns a feature request into a question you can investigate.</p><p>When someone suggests an addition during the build, make a clear choice. Can it wait? Should it replace something already planned? Is it important enough to reconsider the budget or timing?</p><p><strong>A new idea should prompt a decision, not become a commitment by default.</strong></p><h3>5. Test with people who would use it</h3><p>Before adding more, check whether the main task makes sense to real customers. You might start with a set of sample screens people can click through, then test a limited working version.</p><p>Give participants a realistic task. For the hypothetical rental project:</p><blockquote>You need equipment for an upcoming job. Show how you&#39;d send an inquiry and find out what happens next.</blockquote><p>Watch where they pause, miss information, or expect something different. Try not to explain every step. You want to find out what makes sense without your help.</p><p>Afterward, ask what was confusing and what they expected after submitting. Include staff, too. They need to be able to work with the incoming request.</p><p>A small test can reveal useful problems, but it doesn&#39;t tell you how every customer will behave. Address the obstacles you find and test again where needed.</p><h3>6. Set a spending boundary and decide what comes next</h3><p>Before building, agree on what the first version includes, what it leaves out, and when you&#39;ll review it before committing to more work. Leave room in the plan for testing and changes.</p><p>At that review, return to your original outcome. Could customers finish the task? Did staff receive useful information? Where did people need help?</p><p>Sort possible next steps into three groups:</p><p>• <strong>Fix:</strong> Something blocks or undermines the main task.</p><p>• <strong>Improve:</strong> The task works, but people encounter a recurring difficulty.</p><p>• <strong>Expand:</strong> A new capability would serve another need.</p><p>Fixes usually deserve attention before expansion. If customers mistake an inquiry for a confirmed booking, clarify that before adding favorites.</p><p>For each larger addition, weigh the customer need, the evidence, and the effort involved. Better wording or fewer fields might help more than another feature.</p><p>This approach doesn&#39;t guarantee lower costs. It gives you clearer points to decide whether more spending is worthwhile. Pausing is a valid choice when the current version meets the need.</p><p>Whether you&#39;re planning a simple website or a custom service, start with a useful boundary rather than a complete wish list.</p><p>When you&#39;re ready, visit <a href="https://nerdswhofish.com/">Nerds Who Fish</a> for a low-pressure conversation about your project.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15dcf1bdd7f7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Questions to Ask Before You Sign Up for New Business Software]]></title>
            <link>https://medium.com/@apollorion/questions-to-ask-before-you-sign-up-for-new-business-software-3a24f4a1751d?source=rss-549929542dd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a24f4a1751d</guid>
            <dc:creator><![CDATA[Joey Stout]]></dc:creator>
            <pubDate>Wed, 18 Nov 2026 14:12:12 GMT</pubDate>
            <atom:updated>2026-11-18T14:12:12.049Z</atom:updated>
            <content:encoded><![CDATA[<p>New software can be tempting when you are juggling bookings, chasing invoices, or searching for customer details. But before you add another subscription, it is worth asking whether it will make everyday work easier.</p><p>You do not need to be technical to choose thoughtfully. These questions will help you assess an <strong>off-the-shelf tool</strong>, meaning software already built for many businesses, against what your business actually needs.</p><h3>1. What problem must this tool solve?</h3><p>Start with the task that is causing trouble, rather than a list of appealing features. “We need to be more organized” is understandable, but hard to test.</p><p>A more useful problem statement might be:</p><blockquote>We need everyone handling bookings to see the same current schedule without checking three different places.</blockquote><p>Write down what is difficult now, what a better process would look like, and which features are essential.</p><p>Keep <em>must-haves</em> separate from nice extras. If your biggest headache is tracking unpaid invoices, do not let a collection of marketing features distract you from testing invoice tracking.</p><h3>2. Can something you already pay for do the job?</h3><p>Before adding another account, check your existing tools. There may be a booking feature, shared contact list, or reporting option you have not tried.</p><p>Ask whoever manages your accounts to check what is included. If something looks promising, ask the provider to show you how it handles your task.</p><p>An existing feature might be too awkward or limited. You do not have to settle for it. Still, it deserves a look before you add another bill and another place to keep information updated.</p><p><strong>The goal is a workable process, not a bigger software collection.</strong></p><h3>3. Who will use it every day?</h3><p>The person buying the software may not be the person using it all afternoon. Include the people who will enter bookings, send invoices, or update customer details.</p><p>Ask where their current process gets frustrating, then let them try those tasks themselves.</p><p>Consider the practical details:</p><p>• Will they work at a desk, on a phone, or both?</p><p>• Can they find common tasks without constant help?</p><p>• Does it meet their accessibility needs?</p><p>• Who will help new employees learn it?</p><p>You want something that fits an ordinary busy day, not just a guided demonstration.</p><h3>4. Does it work with your existing tools?</h3><p>Providers often advertise <strong>integrations</strong>. These are connections that let tools share information or trigger actions between them.</p><p>Do not stop at “Yes, it connects.” Ask what the connection actually does.</p><p>Will a new booking appear in your existing calendar? If someone changes it, will both places update? Does customer information move automatically, or will someone still copy it across?</p><p>Check whether the connection needs a separate service, a different subscription, or extra setup. Ask how you would notice if it stopped working and who would help.</p><p>List the tools you rely on now, then test the connections that matter most.</p><h3>5. Who owns your data, and can you take it with you?</h3><p>Your customer details, appointment history, invoices, and notes need to remain useful beyond one subscription.</p><p>Read the provider’s terms and privacy information. Ask who owns the information you enter, how the provider may use it, and whether other companies help store or process it. For sensitive information or industry-specific obligations, seek qualified advice about suitability.</p><p>Ask about <strong>exporting</strong>, too. This means downloading your information so you can keep a copy or move it elsewhere.</p><p>• Which records can you export?</p><p>• Are notes, attachments, and history included?</p><p>• Can another tool read the downloaded files?</p><p>• Can you export records yourself, or must support help?</p><p>• How long can you access your information after cancellation, and when is it deleted?</p><p><strong>Test an export before committing.</strong> Open the files and check that the information is understandable and usable.</p><h3>6. How will account access work?</h3><p>Not everyone needs access to everything. Decide who should view customer information, change settings, download records, or manage billing.</p><p>Look for individual accounts instead of one shared login. Ask about <strong>permissions</strong>, the settings that control what each person can see and do.</p><p>Check for <strong>two-step sign-in</strong>, which adds another check beyond a password, such as a code from an authentication app.</p><p>Think through what happens when an employee leaves:</p><p>• Can you remove their access promptly?</p><p>• Can you reassign their bookings or unfinished work?</p><p>• Will their business records remain available?</p><p>• Who can recover the main account if its usual manager is unavailable?</p><p>Keep the main account and recovery details under business control rather than tied to an employee’s personal email address.</p><h3>7. What support and updates are included?</h3><p>When something goes wrong, you need to know where to turn. Check how to contact support, its working hours, and what help your subscription includes.</p><p>During a trial, send a genuine question. Is the answer clear enough to help you move forward? Check whether everyday instructions and setup guidance are available, too.</p><p>Ask how the provider announces important updates, including changes to features you rely on. Find out whether there is a service-status page showing known outages.</p><p>Look for support that fits your working day, not just a “support included” label.</p><h3>8. Can you try one real task from start to finish?</h3><p>Choose a typical task and complete the whole process during a trial. For scheduling, try creating a booking, rescheduling it, sending a confirmation, and cancelling it.</p><p>Use realistic test information rather than sensitive customer details while you assess the provider’s arrangements. Check that test messages will not reach actual customers.</p><p>Let the daily user do the work. Note confusing steps, repeated typing, and workarounds. Test important connections and export your test records.</p><p>Then return to your original problem: does this tool solve it in a way your team can maintain?</p><h3>9. What are you committing to over time?</h3><p>Understand what affects ongoing costs, including extra users, usage limits, storage, support, connections, and access to essential features. Allow for the time needed to set up the tool and train your team.</p><p>Read the terms covering commitment length, automatic renewal, cancellation notice, and changing or ending the subscription. Check whether a trial turns into a paid subscription automatically.</p><p>These are general checks. If the commitment is significant or the terms are unclear, seek appropriate professional advice before agreeing.</p><h3>Choose for the work you actually do</h3><p>You do not need software that does everything. You need something that solves a clear problem, suits the people using it, and gives you understandable options if you decide to leave.</p><p>A short checklist and a hands-on trial are a sensible place to start.</p><p>If you would like a second pair of eyes on your software questions, visit <a href="https://nerdswhofish.com/">Nerds Who Fish</a> or get in touch.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a24f4a1751d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What Should Your Website’s Contact Form Ask Customers?]]></title>
            <link>https://medium.com/@apollorion/what-should-your-websites-contact-form-ask-customers-00bd17e0dce0?source=rss-549929542dd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/00bd17e0dce0</guid>
            <dc:creator><![CDATA[Joey Stout]]></dc:creator>
            <pubDate>Tue, 17 Nov 2026 14:14:42 GMT</pubDate>
            <atom:updated>2026-11-17T14:14:42.526Z</atom:updated>
            <content:encoded><![CDATA[<p>Your contact form should help customers start a conversation, not feel like homework. You need enough information to understand what they want and reply helpfully. You probably do not need every detail before you have said hello.</p><p>For most small businesses, a good starting point is a name, a way to reply, and a short description of the request. Add more questions only when the answers will help you handle that first inquiry.</p><h3>Start with the basics</h3><p>Before adding a field, ask yourself: <em>Do we need this now, or could we ask during the follow-up?</em></p><p>A focused form usually includes:</p><p>• <strong>Name:</strong> One name field is often enough.</p><p>• <strong>A way to reply:</strong> Ask for an email address or phone number, depending on how you handle inquiries. Do not require both unless you need both.</p><p>• <strong>What the customer needs:</strong> Leave room for a short explanation in their own words.</p><p>A few extra questions may be useful. A service category can help you understand the request, but include “Other” or “Not sure.” A city or postal code may establish whether someone is in your service area without asking for a full address.</p><p>Ask about preferred timing if it helps you plan. A budget range may be appropriate for some projects, but let customers say they are unsure. Mark optional fields clearly rather than making people invent an answer to continue.</p><h3>Make the message box easier to answer</h3><p>“Message” is a familiar label, but a little guidance can help someone get started. Suggested wording:</p><blockquote>What can we help with? Tell us a little about the service or project you have in mind and any timing preferences. Please do not include payment details or other sensitive information.</blockquote><p>Keep those instructions visible beside the field, not just inside it as text that disappears when someone starts typing.</p><p>Only request photos or documents if you need them to assess the initial inquiry. Otherwise, ask later through an appropriate channel. File uploads add another step for customers and more information for you to manage.</p><h3>Leave sensitive details out</h3><p>A general contact form should not request passwords, payment-card details, government identification numbers, or unnecessary medical, legal, or financial information.</p><p>Even a simple message box can invite oversharing, so a brief reminder is worthwhile. That reminder does not replace sensible security and information-handling practices.</p><p>Know where submissions are stored, who can see them, and when they should be deleted. Link to a privacy notice that reflects what you actually do. If your business handles information with special legal requirements, get qualified advice about the right way to collect it.</p><p><strong>Ask for what you need to start the conversation, not everything you might need later.</strong></p><h3>Tell customers what happens next</h3><p>Before someone presses the button, explain how you will respond and give a realistic reply timeframe. Only state a timeframe your team can support.</p><p>After submission, show a clear message explaining that the inquiry was received and what comes next. If you send an acknowledgment email, avoid unnecessarily copying sensitive message content into it.</p><p>Be especially clear about appointments. Selecting a preferred date does not mean that date has been reserved.</p><p>For an inquiry-only form, use a button such as <strong>“Send inquiry”</strong> or <strong>“Request an appointment.”</strong> Suggested supporting wording:</p><blockquote>Sending this form does not confirm an appointment. We will contact you to discuss your request and confirm availability.</blockquote><p>Keep that distinction consistent on the form, confirmation screen, and acknowledgment email. Do not say “You’re booked” unless an actual booking has been made.</p><h3>Offer another way to reach you</h3><p>Some customers prefer not to use a form. Others may have difficulty completing it or need to ask something that does not fit your questions.</p><p>Provide a visible business email address or phone number that someone monitors. Make phone numbers easy to tap on a mobile device, and include contact hours where helpful. Only offer text messaging if your team handles texts.</p><p>If the form is not monitored for urgent requests, say so and explain which contact method customers should use instead, if you offer one.</p><h3>Keep it comfortable to use on a phone</h3><p>A form should work for people using small screens, keyboards, or screen readers, which read on-screen content aloud.</p><p>Focus on a few practical basics:</p><p>• Use a simple, single-column layout with readable text and easy-to-tap controls.</p><p>• Give each field a visible label, and clearly identify required and optional questions.</p><p>• Make sure people can move through the form using a keyboard and see which field or button is selected.</p><p>• Explain errors in words, not just color, and keep existing answers when someone needs to correct a field.</p><p>• Make sure submission confirmations can be detected by screen readers.</p><p>Ask whoever builds the form to check these details, including any spam-prevention step. A tidy appearance alone does not tell you whether everyone can use it.</p><h3>Choose the simplest setup that fits</h3><p>A <strong>hosted form</strong>, a form run by an outside service and linked to or embedded in your website, may be enough when inquiries go to one person or a small team and manual follow-up is manageable.</p><p>Check that you can review stored submissions rather than relying only on email notifications. Also check mobile usability, accessibility, account access, storage controls, and whether you can export your information if you change tools.</p><p>You do not automatically need custom development for a contact form. Consider setup and ongoing maintenance, not just the feature list.</p><p>A <strong>backend workflow</strong>, the behind-the-scenes process for organizing and handling requests, becomes worth considering when your team struggles to see who is responsible for an inquiry or whether anyone has replied. A shared record with an owner and status may be more useful than another email notification.</p><p>The customer-facing form can still stay short. Decide what operational problem you need to solve before adding complexity.</p><h3>Test the whole conversation</h3><p>Before launch, submit test inquiries from a phone and a computer. Try keyboard navigation, missing required answers, and an invalid email address.</p><p>Then follow a successful submission through the process:</p><p>1. Does the customer receive an accurate confirmation?</p><p>2. Is the inquiry stored, and does the right person receive the notification?</p><p>3. Can that person reply easily, and can someone cover when they are away?</p><p>Check spam folders and repeat delivery tests after changes to your website, email settings, or connected tools.</p><p>Start small, then adjust based on the questions customers struggle with and the details you repeatedly need to request. The goal is a useful first conversation, not a perfect questionnaire.</p><p>Whether you are planning a simple website or considering how inquiries should connect to backend systems and services, visit <a href="https://nerdswhofish.com/">Nerds Who Fish</a> to get in touch about your project.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=00bd17e0dce0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is Your Website Bringing You Customers? 6 Signs It’s Not (and What to Fix)]]></title>
            <link>https://medium.com/@apollorion/is-your-website-bringing-you-customers-6-signs-its-not-and-what-to-fix-56f98286241b?source=rss-549929542dd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/56f98286241b</guid>
            <dc:creator><![CDATA[Joey Stout]]></dc:creator>
            <pubDate>Thu, 12 Nov 2026 16:14:06 GMT</pubDate>
            <atom:updated>2026-11-12T16:14:06.120Z</atom:updated>
            <content:encoded><![CDATA[<p>Your website looks fine. The logo is there, the photos are sharp, and you’ve got a contact page. But is it helping people become customers, or is it just sitting there?</p><p>When you’re busy running a business, that can be hard to tell. A quiet inbox doesn’t explain what’s wrong. People might not be finding you, understanding your offer, or getting through when they try to make contact.</p><p>I’d start with a few simple checks, not a whole new website. Let’s walk through six signs something needs attention and what you can do about each one.</p><h3>1. Visitors have to guess what you do</h3><p>“Helping You Achieve More” sounds positive, but it could describe almost any business. Your homepage needs to tell people whether they’re in the right place.</p><p>Look at the first screen without scrolling. Can someone tell what you offer, who you help, and where you work, if location matters?</p><p><strong>What to fix:</strong> Trade vague wording for a clear description. A gardening business, for example, might use “Garden maintenance for homeowners in [service area].” Follow it with a short sentence explaining the work you handle.</p><p>You can still sound like yourself. Just explain the service before asking a visitor to make sense of a clever slogan.</p><p><strong>Quick check:</strong> Show your homepage to someone unfamiliar with your business. Ask what they think you do, without giving them hints. Their uncertainty can point you toward what needs rewriting.</p><h3>2. The next step isn’t obvious</h3><p>Someone likes what they see. Now what?</p><p>If they have to search for a way to contact you, there’s work to do. It’s also confusing when booking, subscribing, downloading, and following your social accounts all compete for attention.</p><p><strong>What to fix:</strong> Give each important page one main next step. Depending on the page, that could be:</p><p>• Request an estimate</p><p>• Ask about availability</p><p>• Book an introductory call</p><p>• Browse products</p><p>Use those words on the button instead of “Click Here.” Put the action near the introduction and again after the details someone needs to decide.</p><p>Alternatives are fine. A phone number beside a form offers a choice without making everything equally prominent.</p><p><strong>Quick check:</strong> Open a service page. Can you spot the next step straight away? Does it explain what happens afterward? If submitting a form starts a conversation rather than confirms a booking, say so.</p><h3>3. Your site is awkward to use on a phone</h3><p>A page that looks tidy on your computer can be frustrating on a phone. Small text, cramped buttons, and pop-ups can make a simple task feel like a chore.</p><p><strong>What to fix:</strong> Try using your site on an actual phone, not just a desktop preview. Check that:</p><p>• Text is readable without zooming.</p><p>• Buttons are easy to tap separately.</p><p>• Menus open, close, and lead to the right pages.</p><p>• Forms ask only for information you need.</p><p>• Phone links dial the correct number.</p><p>• Banners don’t cover important information or controls.</p><p>Notice slow-loading pages, too. If photos or decorative features seem to cause delays, ask your website provider to review them.</p><p><strong>Quick check:</strong> Pick a task, such as finding a service and asking about availability. Complete it on your phone. Note anything that makes you pause, zoom, or try again.</p><h3>4. Basic customer questions go unanswered</h3><p>Before getting in touch, people may want to know whether you cover their area, handle their kind of project, or offer the service they need.</p><p>“We provide excellent service” doesn’t answer those questions. Neither does a long description full of words your customers wouldn’t use.</p><p><strong>What to fix:</strong> Start with the questions people ask before working with you. Add useful answers to the relevant service pages, including:</p><p>• What’s included and what isn’t</p><p>• Who the service is for</p><p>• Which areas you cover</p><p>• How the process starts</p><p>• What someone should have ready when contacting you</p><p>Check for outdated details. Where available, add genuine supporting material, such as accurate credentials, project photos you have permission to use, or customer feedback shared with permission. Skip claims you can’t back up.</p><p><strong>Quick check:</strong> Take three common customer questions. Can you find clear answers on your site without digging? If not, start there.</p><h3>5. People aren’t finding your important pages</h3><p>A clearer contact button won’t solve everything if the right people never reach your site. They need a way to discover what you offer.</p><p><strong>What to fix:</strong> Check that your business listings and social profiles link to the correct website. Then look at your page titles, headings, and service descriptions. Do they use everyday words your customers would recognize?</p><p>Include accurate service-area details where relevant. Give a service its own page when you have enough useful information to say about it, rather than creating pages that repeat the same words.</p><p>If website reports or search tools are already set up, look at how people arrive and which pages they find. Those details are clues, not the whole story. If you’re unsure whether search engines can access your main pages, ask your website provider to check.</p><p><strong>Quick check:</strong> Follow the website links from your business profiles. Do they work, and do they land somewhere useful?</p><h3>6. You don’t know whether inquiries get through</h3><p>A quiet inbox doesn’t always mean nobody tried. A form might send messages to an old address, a booking link might be broken, or an inquiry might land in spam.</p><p><strong>What to fix:</strong> Test the full contact process from a phone and a computer. Check that the message reaches you, the visitor sees a clear confirmation, and any automatic reply is accurate. Only state response times you can realistically meet.</p><p>Keep a simple record of inquiries, where people say they found you, and whether they’re a good fit for your business. Keep only the personal information you need and handle it appropriately.</p><p>If you use website tracking, remember that a button click isn’t the same as a real inquiry. Privacy and tracking requirements vary by location, so check what rules apply to you before changing your setup.</p><p><strong>Quick check:</strong> Send a test inquiry today and follow it all the way to your inbox.</p><h3>Start with one thing</h3><p>You don’t need to tackle everything at once. I’d fix broken contact routes first, then work on the biggest source of confusion. Review inquiries over time to help decide what deserves attention next.</p><p>If you’d like a fresh perspective on your website, visit <a href="https://nerdswhofish.com/">nerdswhofish.com</a> or get in touch. You don’t need to have all the answers before starting a conversation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=56f98286241b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Behind the Click: What Happens When a Customer Uses Your Website?]]></title>
            <link>https://medium.com/@apollorion/behind-the-click-what-happens-when-a-customer-uses-your-website-6190350e7067?source=rss-549929542dd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/6190350e7067</guid>
            <dc:creator><![CDATA[Joey Stout]]></dc:creator>
            <pubDate>Wed, 11 Nov 2026 15:49:48 GMT</pubDate>
            <atom:updated>2026-11-11T15:49:48.364Z</atom:updated>
            <content:encoded><![CDATA[<p>A customer clicks “Book,” submits an enquiry or places an order on your website. They see a confirmation and get on with their day.</p><p>Behind that interaction, something needs to happen with their request. An appointment may need reserving, a message needs reaching the right person, or an order needs recording so your team can fulfil it.</p><p>That is where your website’s backend comes in. It connects the actions customers take on screen with the information and processes your business uses to serve them.</p><p>For a small-business owner, understanding that connection helps answer a practical question: <strong>What does your website need behind the scenes, and how much complexity is actually worth paying for?</strong></p><h3>The visible website and the work behind it</h3><p>The <em>frontend</em> is the part customers see and use: pages, menus, forms, calendars and buttons.</p><p>The <em>backend</em> handles work beyond that interface. It receives requests, checks rules, reads or updates stored information, and communicates with other services.</p><p>On a booking website, the calendar is part of the frontend. The process that checks whether a slot is available and records a reservation is part of the backend.</p><p>You do not necessarily need a bespoke backend to do this. A simple website can use existing hosted forms, booking tools or other services to receive enquiries and handle routine interactions. Your website platform may already include what you need.</p><p>The useful starting point is the customer’s journey, not a technology shopping list.</p><h3>Follow one customer interaction</h3><p>Imagine a customer booking an appointment through your website. The exact process will depend on your tools, but the work behind the screen might look like this.</p><h3>1. The website sends the request</h3><p>The customer chooses a service and an appointment time, enters their details and clicks “Book.” Their browser sends that information to the system responsible for handling bookings.</p><p>The backend needs to check what it receives. Are the required details present? Is the selected service valid? If there is a fee, does it match the business’s current pricing rules?</p><p>Checks on the visible page can help customers complete a form, but the backend should also validate the request. It should not assume that everything sent by a browser is correct.</p><h3>2. The system checks whether the booking can happen</h3><p>A time slot appearing on screen is not enough to guarantee that it is still available when the customer submits their request. Someone else may have selected it in the meantime.</p><p>The booking process needs a way to handle that situation without confirming two customers for the same appointment. It may also need to account for staff availability, preparation time or limits on how far ahead people can book.</p><p>These are business rules expressed in software. Defining them clearly is part of planning the website, even if an existing booking service will do the technical work.</p><h3>3. Connected services do their part</h3><p>If the appointment requires a deposit, the system may contact a payment provider. It might also connect to a calendar or customer management tool.</p><p>These connections often use an API: an agreed way for software systems to exchange requests and information. In ordinary terms, it allows one service to ask another to do something without a staff member moving the details manually.</p><p>Each connection needs a clear purpose. If your existing booking tool already manages appointments and sends reminders, adding a second system to do the same work may create unnecessary cost and confusion.</p><h3>4. The booking becomes a business record</h3><p>The system records the appointment and its status. Your team needs to know who booked, what they requested, when they are expected and whether any payment still needs attention.</p><p><strong>A success message on a page is not a substitute for a usable record.</strong> The information needs to reach the place where your team actually manages the work.</p><p>That might be a hosted booking dashboard rather than custom software. What matters is that staff can find the request and understand what to do next.</p><h3>5. The customer receives a clear outcome</h3><p>The website tells the customer whether the booking succeeded. A confirmation email may follow with the appointment details and instructions for changing or cancelling it.</p><p>Some work can happen in the background. For example, the booking might be saved before a notification email is sent. If that email fails, the appointment should still be visible to staff, with a way to identify and address the missing notification.</p><p>The customer should also know where to get help if the outcome is unclear.</p><h3>What happens when something goes wrong?</h3><p>The straightforward path is only part of the process. A useful backend also accounts for interruptions and uncertainty.</p><p>Consider a customer who clicks twice because the page seems slow. The system needs a way to prevent a repeated submission from creating duplicate bookings or charges.</p><p>Or suppose a payment request times out. That does not necessarily mean the payment failed. Before trying again, the process needs a way to check what happened.</p><p>You do not need to specify the technical solution yourself, but you should ask whoever builds or configures the website:</p><p>• What will the customer see if a service is unavailable?</p><p>• How will staff find incomplete or failed requests?</p><p>• Can a customer safely retry an action?</p><p>• Who is responsible for investigating a problem?</p><p>• Can the team recover the request without asking the customer to start over?</p><p>These questions help keep the discussion grounded in customer service rather than a list of features.</p><h3>When better backend services can support growth</h3><p>Backend services can help a business handle more activity by making the steps after a customer interaction easier to manage.</p><p>The strongest reason to improve them is usually a specific problem. Perhaps staff retype every enquiry into another tool. Perhaps customers keep calling because they cannot check a request’s status. Perhaps your website accepts bookings that someone must then reconcile against a separate calendar.</p><p>A suitable connection or service could reduce those handoffs, give customers useful self-service, or make outstanding work easier to see. The benefit depends on the process being clear in the first place, including which system holds the authoritative information and who handles exceptions.</p><p>Start with one outcome you can assess, such as removing duplicate entry or making unconfirmed bookings visible. Growth alone is not a reason to commission a larger system.</p><h3>Choose the simplest setup that serves the customer</h3><p>A business that needs a few informative pages and an enquiry form may be well served by a simple website connected to a hosted form service. It does not need a bespoke backend just because customers submit information online.</p><p>More involved requirements may justify additional service-building work. Examples include a customer portal with access to private records, a booking process with unusual rules, or a website that must exchange information with several business systems.</p><p>Before committing, consider the whole responsibility:</p><p>• <strong>Ongoing cost:</strong> Include subscriptions, maintenance, support and staff training alongside the initial build.</p><p>• <strong>Reliability:</strong> Decide what happens when a connected service is unavailable and how work will be recovered.</p><p>• <strong>Security and privacy:</strong> Identify what information is needed and who should have access. Legal requirements depend on jurisdiction and the data involved, so applicable obligations need verification.</p><p>• <strong>Flexibility:</strong> Check whether you can export the records you need if you change providers.</p><p>A useful proposal should explain why each part is necessary, what existing services can cover and what someone will need to maintain.</p><h3>Start with the journey you want to improve</h3><p>Nerds Who Fish’s backend and service-building focus is relevant to the work behind these interactions: how a request is handled, where information goes and how connected services support the next step.</p><p>Before discussing a project, write down one customer journey from start to finish. Include what the customer sees, what your team does afterward and where the process becomes difficult. Note the tools you already use and the budget constraints the solution needs to respect.</p><p>If you are a small-business owner considering hiring the team, visit <a href="https://nerdswhofish.com/">Nerds Who Fish</a> to start a conversation about what your website needs. That includes owners who simply need a clear, useful website with an existing hosted form or service. Bring the problem you want to solve, whether it calls for a straightforward site or more involved backend work, and ask what approach fits your business and budget.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6190350e7067" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Five Everyday Tasks a Custom App Can Take Off Your Plate]]></title>
            <link>https://medium.com/@apollorion/five-everyday-tasks-a-custom-app-can-take-off-your-plate-124bbd730493?source=rss-549929542dd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/124bbd730493</guid>
            <dc:creator><![CDATA[Joey Stout]]></dc:creator>
            <pubDate>Wed, 11 Nov 2026 09:58:47 GMT</pubDate>
            <atom:updated>2026-11-11T09:58:47.330Z</atom:updated>
            <content:encoded><![CDATA[<p>A customer sends a request without the job address. An approved order needs to be entered into another system. Someone calls to ask whether their job is finished, and you have to track down the person doing it.</p><p>These are useful places to look for software improvements because the work is specific. You can identify what information is missing, where someone has to copy it, and which decisions still belong with a person.</p><p>Before commissioning anything custom, check what your current tools can already handle. A better form, a scheduling feature, or an existing integration may be enough. Custom software is worth considering when an important gap remains and the cost of building and maintaining it fits a sustainable budget.</p><p>Nor does “app” have to mean something customers download. A browser-based tool or a behind-the-scenes service connecting your existing systems may do the job.</p><p>Here are five everyday tasks to examine, with hypothetical examples of how each could work.</p><h3>1. Collecting complete customer requests</h3><p>Imagine a small repair business receiving inquiries by email, phone, and a general contact form. One customer describes the problem but leaves out the equipment model. Another sends photos without a location. Before anyone can assess the work, someone has to ask follow-up questions.</p><p><strong>What automation could do:</strong> A guided request form could ask for the details needed for that type of job. It might request a service address, equipment information, photos, and preferred contact method. Required fields and basic checks could catch missing information before submission, then place the request in a shared queue.</p><p>A browser-based form could also show different questions depending on the service selected, so customers do not have to work through irrelevant fields.</p><p><strong>What still needs a person:</strong> A complete form does not necessarily contain an accurate diagnosis. Staff still need to assess unclear descriptions, decide whether the work is suitable, and handle customers who cannot supply every detail. The form should offer a way to say “I’m not sure” rather than encourage guessing.</p><p><strong>Check existing tools first:</strong> Your website builder, form service, or customer-management system may already support conditional questions, attachments, and notifications. Custom work becomes more useful when the request needs to feed a particular workflow that those tools cannot reasonably support.</p><h3>2. Coordinating appointments and job assignments</h3><p>Consider a cleaning business coordinating recurring visits and one-off bookings. A calendar shows when people are available, but the owner also has to consider travel, job length, equipment, and which team can handle each assignment.</p><p><strong>What automation could do:</strong> A shared scheduling tool could bring those details together, flag overlapping assignments, and suggest available slots based on agreed rules. Once a dispatcher approves an assignment, it could notify the team and send the customer a confirmation.</p><p>The first useful version might simply show unassigned jobs beside team availability. Automatic scheduling does not have to be the starting point.</p><p><strong>What still needs a person:</strong> An urgent request, an unexpectedly difficult job, or a team member calling in sick can require judgment. Staff should be able to override a suggestion and record the reason. Software also needs accurate availability and job information to make useful recommendations.</p><p><strong>Check existing tools first:</strong> Booking and field-service tools may already cover the scheduling needs of the business. Before building a custom scheduler, test whether configuration, shared calendars, or a better booking process resolves the difficulty. A custom addition may only need to handle one missing assignment rule.</p><h3>3. Moving approved orders between existing systems</h3><p>Picture a small wholesaler approving an order in a sales tool, then retyping customer details, item codes, and quantities into a fulfillment system. The second entry consumes attention and creates another opportunity for a mismatch.</p><p><strong>What automation could do:</strong> A backend service could detect an approved order, check that required information is present, and send the relevant details to the destination system. It could record the destination’s reference number and show whether the transfer succeeded or needs attention.</p><p>This work may need no customer-facing app at all. Staff might only need a small screen listing transferred orders and exceptions.</p><p><strong>What still needs a person:</strong> Someone must decide what counts as approval and how to handle missing item codes, changed quantities, cancellations, or conflicting customer records. A failed transfer should enter a visible exception queue rather than disappear. Retrying a transfer also needs safeguards against creating duplicate orders.</p><p><strong>Check existing tools first:</strong> Look for supported connectors or import features in the systems you already use. Any integration depends on the interfaces and access those systems provide, including permissions and subscription restrictions. Custom software cannot assume access that a provider does not support.</p><p>This is a strong reason to discuss backend and service-building work with Nerds Who Fish: the visible screen may be a small part of the project. Connecting the tools, keeping records consistent, and handling failed transfers deserve as much attention as the interface.</p><h3>4. Sharing useful job-status updates</h3><p>Imagine a workshop where the front desk regularly walks into the work area to ask whether a job is waiting for parts, underway, or ready for collection. Customers call for the same information, and staff have to repeat the search.</p><p><strong>What automation could do:</strong> A simple internal tool could let staff move a job through a few clearly defined stages. An agreed status change could trigger a customer message or update a private browser-based status page.</p><p>The important step is defining what each stage means. “Ready for collection,” for example, should only be selected after the necessary checks are complete. Customer-facing messages should exclude internal notes.</p><p><strong>What still needs a person:</strong> Staff still have to keep the status current. Delays, complaints, and changes to the agreed work may need a conversation rather than an automated message. A status label should not quietly become a promise about completion time.</p><p><strong>Check existing tools first:</strong> Your job-management or customer-service software may already offer status notifications or a customer portal. If it does, improving how staff use it may be more valuable than adding another place to update.</p><p>Access controls matter here. Customers should see only their own information, and staff should have access appropriate to their work. Those rules need to be designed and checked, not left until after the screens are built.</p><h3>5. Preparing a daily operational summary</h3><p>Consider an owner who ends each afternoon opening several systems to count unassigned jobs, check tomorrow’s appointments, and find orders that have not moved forward. The information exists, but gathering it is another daily task.</p><p><strong>What automation could do:</strong> A service could prepare a short summary from agreed sources, highlighting items that need action. For example:</p><p>• Tomorrow’s jobs that still need an assignment.</p><p>• Customer requests waiting for a response.</p><p>• Approved orders whose transfer failed.</p><p>• Open jobs with no recent status update.</p><p>Each item could link to the relevant record so the owner can investigate without searching again. The summary should show when its data was last refreshed and flag unavailable sources.</p><p><strong>What still needs a person:</strong> Someone has to define what the counts mean and decide which exceptions matter. A job with no update may be stalled, or it may simply have an expected waiting period. A summary can direct attention, but it cannot explain every circumstance or replace operational judgment.</p><p><strong>Check existing tools first:</strong> Saved reports, scheduled emails, or a dashboard in your current software may already provide the necessary view. A custom summary makes more sense when essential information is spread across systems and bringing it together would support a clear daily decision.</p><h3>Build around one important gap</h3><p>A useful starting scope is one recurring task with a clear beginning, a clear outcome, and an identifiable person responsible for exceptions. Describe what happens today, where time or information gets lost, and what would make the work easier.</p><p>For a conversation with Nerds Who Fish, bring those details along with the tools you already use. Its backend and service-building expertise is relevant to the less visible parts of a dependable workflow: connecting systems, deciding which record is authoritative, controlling access, detecting errors, and making the software maintainable.</p><p>These connections need ongoing attention. Providers can change their interfaces, access credentials can expire, and business processes can evolve. A sensible scope includes monitoring, a way to recover from failures, documentation, and responsibility for maintenance. Automation can reduce repeated handling, but it cannot guarantee error-free work.</p><p>If your actual need is a simple website that explains your services and makes it easy to contact you, that is a worthwhile project too. There is no reason to add an operational app without an operational need. Choose a scope that serves the business and a budget you can sustain, including upkeep.</p><p>Visit <a href="https://nerdswhofish.com/">Nerds Who Fish</a> to discuss hiring the team for a website, a focused browser-based app, or a backend integration. Bring one task you would like to take off your plate, and start with what it needs to accomplish.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=124bbd730493" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Does Your Small Business Need a Website or a Custom App?]]></title>
            <link>https://medium.com/@apollorion/does-your-small-business-need-a-website-or-a-custom-app-00418fdf7032?source=rss-549929542dd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/00418fdf7032</guid>
            <dc:creator><![CDATA[Joey Stout]]></dc:creator>
            <pubDate>Wed, 11 Nov 2026 09:43:13 GMT</pubDate>
            <atom:updated>2026-11-11T09:43:13.691Z</atom:updated>
            <content:encoded><![CDATA[<p>A customer wants to check your hours. Another wants to book an appointment. Your team needs a better way to track jobs. Each need calls for a closer look before you spend money on technology.</p><p>Start with a practical question: <strong>What should customers or staff be able to do more easily?</strong></p><p>The answer may point to a simple website, a ready-made business tool, custom software, or a combination. Choose a starting point that solves the problem and leaves you with costs and upkeep you can manage.</p><h3>Understand your options</h3><p>Consider these illustrative examples as you compare the choices. They describe possible business needs, rather than client projects.</p><h3>A simple website</h3><p>A straightforward business website helps people understand what you offer and take the next step. It can include your services, hours, location, photos, frequently asked questions, and a way to contact you.</p><p>For a local painting business, that may be enough. Prospective customers can check the service area, see the kinds of work available, and request an estimate.</p><p>A website can also link to or incorporate an existing booking, payment, or ordering service. <strong>Online appointments do not automatically require a custom app.</strong></p><h3>Off-the-shelf tools</h3><p>These are ready-made services you subscribe to or purchase. Scheduling software, online stores, invoicing systems, and customer-management tools fall into this category.</p><p>A tutoring business could pair its website with a scheduling service for appointments, reminders, and payments. That gives the owner an option to test before commissioning custom development.</p><p>You will need to work within the product&#39;s capabilities. Check whether essential features require a higher subscription tier, whether it connects with your current systems, and whether its limitations would create extra work. A small adjustment to your process may be reasonable; a daily struggle to complete basic tasks deserves closer attention.</p><h3>A custom web app</h3><p>A web app runs in a browser and lets people complete tasks. Customers might manage requests or approve work, while staff assign jobs and track progress.</p><p>The boundary between a website and a web app is flexible. A business website can include accounts, booking, and other interactive features. Focus on what people need to accomplish rather than the label.</p><p>An equipment-repair company might need to connect customer approvals, parts availability, technician assignments, and repair status. If existing products leave important gaps in that process, a purpose-built web app could be worth exploring.</p><h3>A native mobile app</h3><p>A mobile-friendly website or web app opens in a browser and works on a small screen. A native mobile app is built for a mobile platform, such as iOS or Android, and installed on a device.</p><p>A native app may deserve consideration when frequent mobile use, offline work, or close integration with device features is central to the job. Evaluate those requirements carefully, since browser-based software can support some of them too.</p><p>Customers can book appointments, sign in to accounts, and make purchases through a website. Ask whether installing an app would make their task easier or introduce an unnecessary step.</p><h3>Describe the problem before choosing a product</h3><p>“We need an app” gives a developer little to investigate. “Our staff enter the same order into three systems” identifies a specific problem.</p><p>Write down:</p><p>• <strong>Who needs help:</strong> new customers, returning customers, office staff, or people working in the field.</p><p>• <strong>What they need to do:</strong> find information, book a service, approve work, share files, or track progress.</p><p>• <strong>Where the difficulty occurs:</strong> repeated data entry, missing details, confusing handoffs, or slow responses.</p><p>• <strong>How often it happens and what improvement would look like:</strong> fewer manual steps, clearer job status, or fewer calls to finish a booking.</p><p>A landscaping company receiving frequent calls for updates might initially consider a customer app. Looking at the process could reveal that schedule changes are not being communicated clearly. An existing messaging or job-management tool may be a useful first step.</p><p>This exercise helps you separate essential requirements from features that would simply be nice to have.</p><h3>Try existing tools against real work</h3><p>Before investing in custom software, walk through your common tasks using a potential off-the-shelf tool. Include an awkward situation: a cancellation, a changed order, a partial payment, or a staff member covering someone else&#39;s work.</p><p>Check whether it can handle your essential tasks, connect with systems you rely on, and give staff appropriate access. Find out how you can export business data and what support is available. Look at how subscription costs change with additional users, features, or usage.</p><p>A tool can be a good fit without matching every preference. Adjusting a minor internal habit may be more sensible than paying to reproduce it in custom software.</p><p>If staff still need parallel spreadsheets or repeated copying to complete core tasks, document those gaps. A developer can then assess whether a connection between existing tools would help or whether a focused custom application deserves consideration.</p><h3>Budget for ongoing ownership</h3><p>Every option has costs and responsibilities after launch.</p><p>A website may need domain registration, hosting, content changes, software updates, and help when a form stops working. Subscription tools bring recurring fees. Custom software requires code maintenance and attention to the services it depends on. Native apps also need upkeep as mobile platforms and distribution requirements change.</p><p>Before agreeing to a project, ask:</p><p>• <strong>What will we pay for?</strong> Clarify the initial scope, exclusions, recurring services, and how future changes are charged.</p><p>• <strong>Who keeps it running?</strong> Establish responsibility for updates, backups, security maintenance, and support when something breaks.</p><p>• <strong>What do we control?</strong> Confirm ownership or access arrangements for the domain, service accounts, business data, and source code where applicable.</p><p>• <strong>Could another provider take over?</strong> Ask about documentation, data export, and the handover process.</p><p>Your own time belongs in the budget too. Someone may need to update information, manage accounts, train staff, and coordinate support.</p><p>If you handle sensitive customer information, payments, or regulated activities, identify relevant privacy, security, and legal requirements early. Obligations vary by business, data, and jurisdiction; qualified advice may be needed.</p><p><strong>Be clear about both your initial budget and what you can sustain after launch.</strong> A recommendation should account for each.</p><h3>Where custom development can help</h3><p>Custom development is worth exploring when existing tools leave an important business process poorly supported. It can also help connect tools that otherwise require staff to move information by hand.</p><p>The useful work may happen behind the scenes. A service could transfer an approved order to another system, apply your business rules, or keep job information consistent across tools. Your customers might continue using the same website while staff gain a more manageable process.</p><p>This is where backend and service-building expertise matters. The backend stores information, controls access, and carries out the steps triggered by a form or button. Building it requires attention to how information moves, how errors are handled, and how the system will be maintained.</p><p>Nerds Who Fish brings a backend and service-building focus to these conversations. That technical perspective helps frame concrete questions about what needs to connect, where a process breaks down, and how much custom work the business can reasonably support.</p><p>Owners who need a simple website are welcome too. A clear, mobile-friendly site with useful service information and a reliable inquiry form may cover the immediate need. The scope should serve the customer&#39;s priorities and budget.</p><h3>Choose a useful starting point</h3><p>Use your current needs to narrow the decision:</p><p>• <strong>People need to find your business and understand your services:</strong> consider a clear, mobile-friendly website.</p><p>• <strong>You need common functions such as booking, payments, or invoicing:</strong> test existing tools and how they fit with your website.</p><p>• <strong>A core process still involves burdensome or error-prone workarounds:</strong> explore a focused custom web app or backend service.</p><p>• <strong>The work depends on specific mobile capabilities:</strong> compare native and browser-based approaches against those requirements.</p><p>Start with the essential tasks and decide what would justify further investment. After making an improvement, keep notes on what remains difficult. Those observations give you a practical basis for the next decision.</p><p>If you are weighing a website, an app, or a better connection between your existing tools, visit <a href="https://nerdswhofish.com/">Nerds Who Fish</a> to discuss your needs. Bring the problem you want to solve, the tools you already use, and your budget. A simple website is a welcome place to start.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=00418fdf7032" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Collecting Open Metrics In K8s And Shipping To Datadog]]></title>
            <link>https://medium.com/beambenefits/collecting-open-metrics-in-k8s-and-shipping-to-datadog-5345cd27ef18?source=rss-549929542dd7------2</link>
            <guid isPermaLink="false">https://medium.com/p/5345cd27ef18</guid>
            <category><![CDATA[datadog]]></category>
            <category><![CDATA[prometheus]]></category>
            <category><![CDATA[ruby]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[metrics]]></category>
            <dc:creator><![CDATA[Joey Stout]]></dc:creator>
            <pubDate>Mon, 10 Aug 2020 12:01:02 GMT</pubDate>
            <atom:updated>2020-08-10T12:01:02.229Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/699/1*8iDm48JuRPcFqBtUW1I7Lg.png" /></figure><p>At Beam, we have a lot of metrics that we collect of which we utilize in pretty standard ways. For instance, we collect CPU and Memory metrics and utilize those for our horizontal pod auto scalers. We also collect custom metrics, like how many claims we’ve processed over a given amount of time so we can alert if the number of claims during a set period drops below an expected amount. Beam also utilizes <a href="https://www.datadoghq.com/">Datadog</a> for our metric and log aggregation so it made sense for us to ship custom metrics to Datadog.</p><p>Currently, we utilize the <a href="https://github.com/discourse/prometheus_exporter">prometheus_exporter</a> gem by Discourse to surface our metrics to Prometheus and wanted to continue to surface a subset of those metrics to datadog in the same way. The reasoning behind only surfacing a subset of the metrics to Datadog came down to one thing, cost. We have hundreds of metrics that are sent to Prometheus and we just wanted metrics in Datadog to facilitate alerting in our slack channels and bubbling those alerts into <a href="https://victorops.com/">Victorops</a> in cases where human intervention needed to happen.</p><p>To get started with this tutorial, you’ll need a few things:</p><ul><li>Working knowledge of Ruby</li><li>A Kubernetes cluster and knowledge of how to set up Kubernetes manifests.</li><li>A Datadog account and the <a href="https://docs.datadoghq.com/agent/kubernetes/?tab=helm">Datadog k8s agent</a> installed to your cluster.</li></ul><h3>Installing Prometheus Exporter</h3><p>To make the tutorial as a whole more visible, I have set this up utilizing the <a href="https://github.com/sinatra/sinatra">Sinatra</a> Ruby framework. The first step of setting this all up is getting the Prometheus exporter gem installed. With bundler this is as simple as running:</p><p>bundle add prometheus_exporter and then bundle install</p><p>Once installed, you can then create a client registry in your application and bind the metrics server to 0.0.0.0:9394 . In app.rb:</p><pre>require &#39;sinatra&#39;<br>require &#39;prometheus_exporter&#39;<br>require &#39;prometheus_exporter/server&#39;</pre><pre># client allows instrumentation to send info to server<br>require &#39;prometheus_exporter/client&#39;<br>require &#39;prometheus_exporter/instrumentation&#39;</pre><pre># bind is the address, on which the webserver will listen<br># port is the port that will provide the /metrics route<br>server = PrometheusExporter::Server::WebServer.new bind: &#39;0.0.0.0&#39;, port: 9394<br>server.start</pre><pre># wire up a default local client<br>PrometheusExporter::Client.default = PrometheusExporter::LocalClient.new(collector: server.collector)</pre><p>Once this is all in place, you can then view empty metrics are being served up by running: bundle exec prometheus_exporter -b 0.0.0.0 and then opening your browser to localhost:9394 (we will call this the metrics tab). This should show you an empty metrics page because no metrics have been exported yet.</p><h3>Setting Up Your First Metric</h3><p>Now that Prometheus exporter is configured, let’s go ahead and add a metric that will count HTTP requests. Appending to app.rb above, add the following:</p><pre>http_requests = PrometheusExporter::Metric::Counter.new(&quot;http_requests&quot;, &quot;A counter of HTTP requests made&quot;)<br>server.collector.register_metric(http_requests)</pre><pre>get &#39;/&#39; do<br>  http_requests.observe(1)   <br>  content_type &#39;text/html&#39;<br>  &quot;hello world&quot;<br>end</pre><p>Now you can start up your Sinatra app with the following command: ruby app.rb -p 3000 -o 0.0.0.0</p><p>Once the application is started, in a new tab you can open your browser to localhost:3000 (we will call this the app tab) which should print out hello world . If you switch back to your metrics tab and refresh you will then see</p><pre># TYPE http_requests counter<br># HELP http_requests A counter of HTTP requests made<br>http_requests 1.0</pre><p>The more you refresh your app tab, the higher the http_requests counter will go.</p><h3>Sending To Datadog</h3><p>Now that we are collecting HTTP request metrics, we will want to ship these metrics to datadog.</p><p>To do this, set up a pod with two containers. One that will accept your production traffic and one that will handle metrics:</p><pre>apiVersion: v1<br>kind: Pod<br>metadata:<br>  name: sinatra<br>  labels:<br>    app.kubernetes.io/name: sinatra<br>  annotations:<br>    ad.datadoghq.com/sinatra.check_names: |<br>      [&quot;openmetrics&quot;]<br>    ad.datadoghq.com/sinatra.init_configs: |<br>      [{}]<br>    ad.datadoghq.com/sinatra.instances: |<br>      [<br>        {<br>          &quot;prometheus_url&quot;: &quot;<a href="http://sinatra-metrics.sinatra.svc.cluster.local/metrics">http://sinatra-metrics.sinatra.svc.cluster.local/metrics</a>&quot;,<br>          &quot;namespace&quot;: &quot;sinatra&quot;,<br>          &quot;metrics&quot;: [&quot;http_requests&quot;],<br>          &quot;tags&quot;: [<br>            {&quot;namespace&quot;: &quot;sinatra&quot;},<br>            {&quot;app&quot;: &quot;sinatra&quot;},<br>            {&quot;environment&quot;: &quot;production&quot;}<br>          ],<br>          &quot;ssl_verify&quot;: &quot;false&quot;,<br>          &quot;ssl_ignore_warning&quot;: &quot;true&quot;<br>        }<br>      ]<br>spec:<br>  containers:<br>    - name: sinatra-metrics<br>      image: myawesomesinatrarepo/sinatratutorial<br>      command:<br>        - bundle<br>        - exec<br>        - prometheus_exporter<br>        - -b<br>        - 0.0.0.0<br>    - name: sinatra-app<br>      image: myawesomesinatrarepo/sinatratutorial<br>      command:<br>        - ruby<br>        - app.rb<br>        - -p<br>        - 3000<br>        - -o<br>        - 0.0.0.0</pre><p>The real magic happens with the pod’s annotations. The Datadog Kubernetes agent is looking for pods that have the ad.datadoghq.com/&lt;podname&gt;.&lt;config_option&gt; annotations and utilizes them for autodiscovery of metrics. One thing that I found hard to find when setting this up at Beam was finding all available &lt;config_option&gt;&#39;s which can be found <a href="https://github.com/DataDog/integrations-core/blob/master/openmetrics/datadog_checks/openmetrics/data/conf.yaml.example">here</a>.</p><p>The most important part of this piece was the &quot;metrics&quot;: [&quot;http_requests&quot;] bit, since this is datadogs whitelist of metrics. It will only pull metrics that are in this whitelist and it allows you to use * as a wildcard. So you can pull all [&quot;http_requests&quot;, &quot;ruby*&quot;] metrics or even [&quot;*&quot;] all metrics.</p><p>The final part of this entire thing is that you will need a service configured so that datadog can hit your metrics endpoint from anywhere within your cluster by utilizing the in-cluster DNS of your service:</p><pre>apiVersion: v1<br>kind: Service<br>metadata:<br>  name: sinatra-metrics<br>spec:<br>  clusterIP: 172.20.20.20<br>  ports:<br>  - name: metrics<br>    port: 80<br>    protocol: TCP<br>    targetPort: 9394<br>  selector:<br>    app.kubernetes.io/name: sinatra<br>  sessionAffinity: None<br>  type: ClusterIP</pre><p>Once the service is in place, you should now see your custom whitelisted OpenMetrics flowing to Datadog within seconds!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/519/1*VE8UJTX7GdcNLVRBj8-vXw.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5345cd27ef18" width="1" height="1" alt=""><hr><p><a href="https://medium.com/beambenefits/collecting-open-metrics-in-k8s-and-shipping-to-datadog-5345cd27ef18">Collecting Open Metrics In K8s And Shipping To Datadog</a> was originally published in <a href="https://medium.com/beambenefits">Beam Benefits</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>