<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Poygan Tech Blog</title><link>https://poygantech.net/blog/</link><description>Practical AI, automation, software, and local-business ideas from Poygan Tech.</description><language>en-us</language><atom:link href="https://poygantech.net/blog/feed.xml" rel="self" type="application/rss+xml"/><item><title>Your Software Requirements Need a Volume Knob</title><link>https://poygantech.net/blog/software-requirements-need-a-volume-knob/</link><guid isPermaLink="true">https://poygantech.net/blog/software-requirements-need-a-volume-knob/</guid><pubDate>Tue, 06 Oct 2026 13:31:57 +0000</pubDate><description>A practical, playful guide to using MUST, SHOULD, and MAY as different levels of commitment, so software projects can separate essential behavior from sensible defaults and optional polish.</description><category>Opinion Fun</category></item><item><title>Turn “Something Went Wrong” Into a Useful Error Contract</title><link>https://poygantech.net/blog/useful-error-contract-for-business-automation/</link><guid isPermaLink="true">https://poygantech.net/blog/useful-error-contract-for-business-automation/</guid><pubDate>Mon, 05 Oct 2026 05:33:41 +0000</pubDate><description>A practical build note for replacing vague automation failures with a small, structured error contract that tells people and software what failed, which occurrence they are examining, and what should happen next.</description><category>Build Note</category></item><item><title>If Your Spreadsheet Had a Job Description, What Would It Say?</title><link>https://poygantech.net/blog/when-business-spreadsheet-needs-app/</link><guid isPermaLink="true">https://poygantech.net/blog/when-business-spreadsheet-needs-app/</guid><pubDate>Sun, 04 Oct 2026 05:34:20 +0000</pubDate><description>A playful inventory exercise for identifying whether a business spreadsheet is acting as a calculator, queue, database, report, approval log, or accidental application, followed by the smallest sensible improvement for each role.</description><category>Opinion Fun</category></item><item><title>The One-Screen Project Status Every Client Deserves</title><link>https://poygantech.net/blog/one-screen-client-project-status-template/</link><guid isPermaLink="true">https://poygantech.net/blog/one-screen-client-project-status-template/</guid><pubDate>Sat, 03 Oct 2026 05:39:01 +0000</pubDate><description>A practical one-screen client project status template that shows the intended outcome, present condition, recent progress, next action, ownership, blockers, decisions, reporting date, and meaningful changes without turning the update into a miniature project-d</description><category>Evergreen How To</category></item><item><title>How to Test an Automation Without Betting the Business on It</title><link>https://poygantech.net/blog/how-to-test-business-automation-safely/</link><guid isPermaLink="true">https://poygantech.net/blog/how-to-test-business-automation-safely/</guid><pubDate>Fri, 02 Oct 2026 05:03:59 +0000</pubDate><description>A practical workflow for testing business automation through shadow mode, a bounded sample, written success and stop conditions, manual fallback, audit comparison, and accountable owner sign-off.</description><category>Evergreen How To</category></item><item><title>The Best Automation Might Be a Better Sentence</title><link>https://poygantech.net/blog/best-automation-might-be-a-better-sentence/</link><guid isPermaLink="true">https://poygantech.net/blog/best-automation-might-be-a-better-sentence/</guid><pubDate>Thu, 01 Oct 2026 05:05:08 +0000</pubDate><description>A practical argument for treating clearer form labels, status definitions, checklist steps, and email templates as workflow improvements before reaching for code.</description><category>Opinion Fun</category></item><item><title>How I Would Turn an Inbox Request Into a Visible Work Item</title><link>https://poygantech.net/blog/turn-inbox-request-into-visible-work-item/</link><guid isPermaLink="true">https://poygantech.net/blog/turn-inbox-request-into-visible-work-item/</guid><pubDate>Wed, 30 Sep 2026 05:33:01 +0000</pubDate><description>A hypothetical email-to-intake design that validates the sender, catches likely duplicates, checks required fields, assigns ownership, acknowledges receipt, and keeps customer promises under human control.</description><category>Build Note</category></item><item><title>A Useful Dashboard Starts With Decisions, Not Charts</title><link>https://poygantech.net/blog/useful-dashboard-starts-with-decisions-not-charts/</link><guid isPermaLink="true">https://poygantech.net/blog/useful-dashboard-starts-with-decisions-not-charts/</guid><pubDate>Tue, 29 Sep 2026 13:13:30 +0000</pubDate><description>A practical build note for designing a small-business dashboard backwards from three recurring decisions, with an explicit question, owner, threshold, and next action for every metric. Includes a clearly labeled synthetic example.</description><category>Build Note</category></item><item><title>Would a Clipboard Pass the Bus Test? A Low-Tech Systems Check</title><link>https://poygantech.net/blog/would-a-clipboard-pass-the-bus-test/</link><guid isPermaLink="true">https://poygantech.net/blog/would-a-clipboard-pass-the-bus-test/</guid><pubDate>Sat, 12 Sep 2026 13:35:13 +0000</pubDate><description>A respectful thought experiment for checking whether an important small-business process can survive a missing person, unavailable device, or undocumented decision. Includes a five-part resilience checklist that works for paper and software alike.</description><category>Opinion Fun</category></item><item><title>The Hidden Cost of Copying the Same Customer Details Three Times</title><link>https://poygantech.net/blog/hidden-cost-copying-customer-details-three-times/</link><guid isPermaLink="true">https://poygantech.net/blog/hidden-cost-copying-customer-details-three-times/</guid><pubDate>Fri, 11 Sep 2026 13:45:57 +0000</pubDate><description>A practical guide to reducing duplicate customer data entry by choosing a source of truth, assigning ownership field by field, and designing handoffs that carry references instead of fresh copies.</description><category>Evergreen How To</category></item><item><title>The Exception Queue: The Part Most Automation Diagrams Forget</title><link>https://poygantech.net/blog/exception-queue-business-process-automation/</link><guid isPermaLink="true">https://poygantech.net/blog/exception-queue-business-process-automation/</guid><pubDate>Thu, 10 Sep 2026 13:36:01 +0000</pubDate><description>A practical build note on designing a visible exception queue for incomplete, conflicting, risky, or low-confidence work, including the five fields every queued item needs and a recovery path back into the workflow.</description><category>Build Note</category></item><item><title>A Tiny CRM Can Beat a Giant One When the Team Actually Uses It</title><link>https://poygantech.net/blog/simple-crm-setup-small-business/</link><guid isPermaLink="true">https://poygantech.net/blog/simple-crm-setup-small-business/</guid><pubDate>Wed, 09 Sep 2026 13:33:56 +0000</pubDate><description>A practical guide to building the smallest CRM a team will reliably maintain, using four essentials: useful records, explicit next actions, clear ownership, and reports that prompt decisions. It also explains when a mature CRM platform is worth the added setup</description><category>Evergreen How To</category></item><item><title>How I Would Design a Missed-Call Follow-Up for a Hypothetical Contractor</title><link>https://poygantech.net/blog/hypothetical-contractor-missed-call-follow-up-workflow/</link><guid isPermaLink="true">https://poygantech.net/blog/hypothetical-contractor-missed-call-follow-up-workflow/</guid><pubDate>Mon, 07 Sep 2026 05:06:54 +0000</pubDate><description>A hypothetical contractor workflow that turns a missed call into a permission-aware text conversation, asks only useful job questions, respects office hours, escalates uncertainty to a person, updates the CRM, and preserves a readable audit trail.</description><category>Build Note</category></item><item><title>A Field Guide to “That Is Just How We Do It”</title><link>https://poygantech.net/blog/field-guide-that-is-just-how-we-do-it/</link><guid isPermaLink="true">https://poygantech.net/blog/field-guide-that-is-just-how-we-do-it/</guid><pubDate>Sun, 06 Sep 2026 05:05:54 +0000</pubDate><description>A respectful field guide to spotting workarounds, shadow spreadsheets, copy-paste rituals, and tribal knowledge, then deciding which process problems are worth fixing without blaming the people who keep the work moving.</description><category>Opinion Fun</category></item><item><title>What an AI Assistant Should Never Decide Alone</title><link>https://poygantech.net/blog/what-an-ai-assistant-should-never-decide-alone/</link><guid isPermaLink="true">https://poygantech.net/blog/what-an-ai-assistant-should-never-decide-alone/</guid><pubDate>Sat, 05 Sep 2026 18:20:30 +0000</pubDate><description>A practical guide to deciding when an AI assistant may proceed, when it needs human approval, and when it should stop, covering money, customer promises, sensitive records, destructive actions, and ambiguous exceptions.</description><category>Evergreen How To</category></item><item><title>Before You Buy Another App, Draw This Four-Box Workflow</title><link>https://poygantech.net/blog/map-business-workflow-before-choosing-software/</link><guid isPermaLink="true">https://poygantech.net/blog/map-business-workflow-before-choosing-software/</guid><pubDate>Thu, 03 Sep 2026 13:31:49 +0000</pubDate><description>A practical guide to mapping a workflow as trigger, input, decision, and output, then using that map to decide whether to configure, connect, replace, or leave an existing tool alone.</description><category>Evergreen How To</category></item><item><title>The 15-Minute Automation Audit: Find One Task Worth Fixing</title><link>https://poygantech.net/blog/15-minute-automation-audit-find-task-worth-fixing/</link><guid isPermaLink="true">https://poygantech.net/blog/15-minute-automation-audit-find-task-worth-fixing/</guid><pubDate>Wed, 02 Sep 2026 16:25:08 +0000</pubDate><description>A practical worksheet for finding one repetitive workflow that is frequent, rule-like, measurable, and equipped with a clear path for human review.</description><category>Evergreen How To</category></item></channel></rss>
