Small-business operations: evidence and commercial tests

Research update: 14 October 2026. Original OP evidence was retrieved on 13 October; newly added NO evidence was retrieved on 14 October. Translation does not imply that original prices were rechecked.

Decision

Prioritize bounded paid-setup experiments for attachment routing, supplier-price review and exact-slot appointment confirmation. Keep certificate renewal tracking and invoice follow-up queues on hold until a meaningful advantage over incumbent tools is established. This is an opportunity catalogue, not a recommendation to build five products.

The expansion adds two distinct workflows: an internal invoice next-action queue, and confirmation of appointments negotiated before booking. Neither is bank-statement extraction, general document collection, or an unrestricted scheduling platform.

Evidence quality

This file accompanies 42 source records and five opportunity cards in operations.json. The original 26 records are fully translated. Sixteen new primary-source records cover the two new candidates, eight each: nine user discussions, one builder-led discussion, two official documentation pages and four vendor pages. All sixteen new pages were opened; two dynamic price pages exposed their numeric prices through search extraction, explicitly noted in their limitations.

The original source set includes 17 user discussions, six vendors, one substitute, one documentation page and one builder post. Three original pages remain search-extraction-only. URL counts are not buyer counts. OP01 and OP04 are the same author, Toobrish. OP06 and OP07 are adjacent Microsoft Lists workflows. OP22 is old historical context. Vendor mentions in comments and claims of using software are not verified purchases.

No interviews, contacts, payments, trials, live charges or remote mutations were performed. Conversion, acquisition cost, retention and revenue are unknown. Proposed prices and development ranges are assumptions. Ranges mean one developer's working days for the stated pilot, not a production SaaS.

Why the two new candidates need restraint

The invoice problem is credible, but a generic reminder product is weak. A small IT-services administrator describes manual follow-up burden (NO02); a Reckon user wants customer-facing reminders but resents an extra paid add-on (NO04). Zoho already documents automatic reminders (NO06). The candidate therefore focuses on ownership, holds and reviewable next actions. It does not assume that sending more messages will resolve payment disputes or cash shortages.

A builder-led discussion reports false reminders after payment (NO05). Its original post is excluded from independent demand evidence; the replies are a reason to test stale-status failures, not a statistically established frequency. Human approval and explicit status checks belong in the pilot.

The appointment candidate has a sharper workflow boundary. A provider wanted payment and forms attached to one assigned appointment, but ultimately retained Acuity workarounds (NO09). Current Square documentation says deposits are available for customer online bookings but not when staff book on the customer's behalf (NO14). That supports checking a narrow integration gap, not claiming an empty market.

Counterevidence matters: deposits did not eliminate one salon's missed appointments (NO12); a customer objected to an extra deposit against already-paid gift certificates (NO13). Test gift-credit exceptions, friction and calendar consistency. Do not promise fewer no-shows or guaranteed payment before measuring results.

Candidate overview

One-time setup prices must not be multiplied into recurring revenue. Optional subscriptions are separate hypotheses.

OP-O1: Reliable attachment routing: setup and support

Configure predictable saving and naming of recurring Excel attachments with an exception log. Value comes from identifying missing or overwritten files and recovering processing.

Decision: research next. Evidence confidence: medium problem low willingness to pay.

Buyer. Operations manager at a small team receiving daily reports in Outlook/SharePoint or Gmail/Drive.

Competition. Mailparser $29.95/month; Power Automate, Apps Script and open-source scripts cover basic transfers. A vacant niche is not established; implementation and support are the initial angle.

Commercial test. Test $199 once for one mailbox-to-storage setup, then optional $29/month error monitoring. Assumptions, not established market prices.

Distribution. Hypothesis: Microsoft 365 or Google Workspace implementation partners and automation projects. Channel performance and acquisition cost unknown.

Main risk. Power Automate and Apps Script solve the basic task. Bespoke exceptions can consume support revenue; price-sensitive users prefer free tools.

Next test. Demonstrate accepted/skipped attachment logs, deduplication and safe retries on three anonymized samples. Test a $199 setup offer with five suitable process owners; no outreach has occurred.

Stop criteria. Stop standalone SaaS if five conversations yield no paid pilot, a standard flow fixes the task in an hour, or support exceeds two hours monthly per $29 customer.

Pilot estimate: 5–10 working days. One developer, working days; client-environment pilot with one mail provider and one storage destination, sender/type filters, deduplication, logs and retries. Excludes public OAuth verification, multitenant billing, arbitrary OCR and ERP integration.

Evidence and limitations:

• OP01: How to Automate Sending Invoices from Emails — A small-business owner processes about 100 invoices monthly; a Gmail script produced 17–23 copies of some files. They want a simple deduplicated workflow. Limitation: Same author, Toobrish, as OP04: two observations from one person, not two independent buyers. Highly price-sensitive.
• OP02: Save multiple attachments — Two daily inventory Excel attachments are saved to SharePoint for Power BI; the second overwrites the first. Limitation: A naming fix in the existing flow may solve this. Supports an implementation service rather than a new SaaS.
• OP03: Saving attachments into relevant company folders — User wants to route attachments to the correct company folder and Sage 200 Sicon based on file content. Limitation: Budget unknown. Replies warn about maintenance across different formats and recommend starting with one supplier.
• OP04: Saving incoming invoices to Google Drive as PDFs — About 50 invoices monthly; days spent experimenting with scripts, irrelevant PDFs and potentially 40–60 Gmail filters. Author prefers a free solution. Limitation: Repeat observation by Toobrish from OP01; does not increase independent-user count. Low willingness to pay.
• OP05: Alternative to Parsio.io — Email parser — An existing Parsio user with templates and n8n webhooks seeks a self-hosted alternative with an easy template editor. Limitation: Self-reported use; payment not verified. Technical audience differs from typical small-business buyers.
• OP06: Power Automate + Microsoft Lists: 250 flows? — Lists attachment routing by department fails: flows report success but files do not appear in the expected folder. Limitation: Adjacent Microsoft Lists workflow, not incoming email. Not direct validation of demand for an email product.
• OP07: Save Attachments from Existing SharePoint List to Document Library — Request to move existing SharePoint list attachments into separate folders; replies address filename collisions. Limitation: Old adjacent migration request, not subscription demand. Existing platform can solve the task.
• OP08: Mailparser pricing — Starter is $29.95/month for 250 emails and 20 inboxes; duplicate detection and webhook retries cost $3.49/month each. Setup assistance is $99/layout. Limitation: Published prices, not verified sales. Image/scanned-document OCR is outside standard Mailparser.
• OP09: Google Apps Script: attachments to Google Folder — An open Apps Script saves Gmail attachments to Drive and logs sender, subject, time and message ID. Limitation: Code availability does not establish reliability, security or support. Evidence of an inexpensive substitute.

OP-O2: Certificate renewals for small field teams

Training and document-date register for small construction, installation and service teams, starting with spreadsheet migration and follow-through on renewals.

Decision: hold. Evidence confidence: medium problem low differentiation.

Buyer. Office manager or training coordinator at a field-service company.

Competition. Expiration Reminder $49/month for 150 records; ExpiryBoard £19/month for unlimited records. A low-cost offer already exists; price alone is insufficient differentiation.

Commercial test. Test $29/month per team and $149 once for spreadsheet migration. Assumptions.

Distribution. Hypothesis: local training providers and training-administration consultants as implementation partners. Channel untested.

Main risk. ExpiryBoard already offers £19/month. Calendar, Excel and existing HR/LMS software may suffice. Incorrect dates or failed delivery create operational risks.

Next test. Ask five teams with 20–100 workers about bulk migration, responsibility history and acknowledged reminders. Test anonymized imports without promising document-validity checks.

Stop criteria. Hold development if existing HRIS covers the need or users only need calendar reminders; do not scale without willingness to pay for migration.

Pilot estimate: 10–20 working days. One developer, working days; CSV import, manually confirmed dates, 30/60-day reminders, renewal history and exports. Excludes credential-registry verification, medical records, legal-rule determination, mobile apps and complex HRIS integrations.

Evidence and limitations:

• OP10: Tracking Employee Certs / Safety Compliance — Employee at a small organization manually tracks certificates for 10+ workers and sends renewal reminders; needs history and notifications to worker and manager. Leadership wants an accessible interface. Limitation: Government organization, not a verified commercial buyer. Replies recommend Excel at this scale.
• OP11: Best Program for Tracking Safety Training Expiration — Construction team reports Access failing to save progress and slow individual uploads in Site Docs; requests batch uploads and reminders. Limitation: Older observation; current Site Docs behavior not checked. No new-product purchase established.
• OP12: Excel Tracker for Managing Certifications — Company employee struggles with conflicting conditional formatting for annual training renewal windows. Limitation: Excel help request rather than a paid-service request. Formulas may satisfy the need.
• OP13: Learning Management System and Tracking Certs — A growing small company manually tracks around 10–15 certificates per employee, including externally delivered training. Limitation: Archived post; current solution unknown. Existing HRIS or SharePoint may replace a separate product.
• OP14: Anyone using software to manage certs? — Small HVAC contractor handles about 20 certificates and discovers an expired one after a general contractor requests it. Limitation: Part of discussion concerns insurance COIs rather than employee training; do not conflate them. Low engagement.
• OP15: Expiration Reminder pricing — Starter is $49/month for 150 expiration items; Professional $99/month for 600. Includes storage, reminders and self-service; higher tier adds escalation. Limitation: Public offer, not verified purchases. Annual labels are ambiguous; comparison uses clear monthly figures only.
• OP16: ExpiryBoard — £19/month or £190/year for unlimited records, email reminders, documents, renewal history and team access. Limitation: Low-cost direct competitor; features not tested. Excludes VAT where applicable.
• OP17: How are you tracking employee certs / expiring IDs? — Author explicitly says they are building an app. Replies reject another app and suggest adding reminders to an existing spreadsheet. Limitation: Not independent demand evidence. Useful as counterevidence and an example of builder-led research contaminating search results.

OP-O3: Supplier price comparison with pack-size checks

Prepare a reviewable report of new products, changed prices and pack sizes between supplier lists. Start with purchasing support in one segment.

Decision: research next. Evidence confidence: medium problem low willingness to pay.

Buyer. Purchasing operator at a small distributor, café group or hotel business receiving incompatible Excel price lists.

Competition. SupplierDelta €39/comparison or €79/month; PriceListIQ advertises $39/month through search extraction; Proceny has a free comparator. Forum users solve simpler tasks with Power Query.

Commercial test. Test $149 once for two-format setup and first report, then $39/month for repeat updates. Service-plus-product hypothesis.

Distribution. Hypothesis: demonstrations on two anonymized price lists, ERP implementation partners and purchasing-report setup services. Acquisition costs unknown.

Main risk. Direct competitors and Power Query are numerous. Wrong pack matches create false savings. Generic comparison lacks a proven advantage.

Next test. Test SKU, GTIN, volume, units, duplicates, tax and currency on three file pairs from one industry. Route ambiguous matches to review, then test a paid first report with five buyers.

Stop criteria. Abandon generic comparison if a Power Query template suffices for three customers without recurring support; do not automate matching when different packs are falsely merged.

Pilot estimate: 7–15 working days. One developer, working days; CSV/XLSX with known columns, two or three formats, approved mappings, exceptions and report export. Excludes OCR, ERP publishing, automated purchasing, global product database and guaranteed fuzzy matching.

Evidence and limitations:

• OP18: Compare different suppliers’ price lists — Thousands of products across supplier lists make copying laborious; user wants matching by product code and later reports Power Query saves hours. Limitation: Successful resolution with an existing tool is strong counterevidence for a separate SaaS.
• OP19: Compare price lists with name and price per kg — User compares produce from 2–4 suppliers with different row order; needs product matching and price per kilogram. Limitation: XLOOKUP and table normalization address the problem; frequency and budget unspecified.
• OP20: Compare old and updated supplier price lists — User wants new products and price reductions identified between old and updated supplier lists. Limitation: Thread marked solved after accepting a spreadsheet answer. Not an unresolved need or willingness-to-pay signal.
• OP21: Matching and comparing prices from different layouts — User needs common products from two supplier lists; different names can cause a simple search to confuse Peroni 330 ml with 5 L. Limitation: Direct evidence of pack-size matching complexity; process frequency and economic impact unknown.
• OP22: Automate weekly price updates from suppliers — Search extraction describes weekly supplier-price entry into a purchasing comparison for a hotel group. Limitation: Search extraction only: opening failed. Very old request; historical context rather than a current buyer signal.
• OP23: PriceListIQ pricing — Published offer states $39/month for up to 100 comparisons, analysis from $299 once, BI dashboards from $799 and managed BI from $499/month. Limitation: Opening failed; prices came from search extraction. Recheck before commercial decisions. An offer does not establish sales.
• OP24: SupplierDelta — €39 per complete comparison or €79/month for up to 10; CSV/XLSX, price changes, additions/removals, pack sizes and local processing. Saved mappings advertised. Limitation: Strong direct overlap. Marketing claims; functionality and purchases not verified.
• OP25: Proceny free supplier price list comparison — Free tool matches rows by supplier code, part number or GTIN. Limitation: Free basic functionality pressures monetization of simple comparison; quality not tested.
• OP26: Microsoft Power Query Merge queries overview — Official documentation describes table merging on selected columns and fuzzy merge. Limitation: Confirms an existing substitute; accuracy for particular product identities requires testing.

NO-O1: Invoice follow-up queue with payment-status review

Internal queue for service businesses showing invoice owner, next action, expected-payment date, dispute/hold flag and manually verified paid status. Draft follow-ups for approval instead of blindly sending another reminder.

Decision: hold. Evidence confidence: medium problem low differentiation.

Buyer. Office administrator or owner at a small IT-services or project-services business with recurring manual invoice follow-up.

Competition. Zoho Invoice offers free invoicing and documented reminders; Chaser Compact is $259/month with a much broader scope. Existing accounting reminders may be sufficient. A lightweight queue has no proven market advantage yet.

Commercial test. Test $199 once to configure an internal queue and reminder drafts; optional $29/month maintenance is a separate unvalidated hypothesis.

Distribution. Hypothesis: bookkeeping implementation partners and fixed-scope workflow setup projects. No outreach, channel conversion or acquisition cost measured.

Main risk. Stale payment data can trigger inappropriate reminders. Generic reminders are already available free; the operational queue may not justify another subscription.

Next test. Use anonymized examples of paid, partly paid, disputed and promised-payment invoices. Ask five administrators to run their next-action review using the queue; seek payment for setup only after demonstrating fewer manual steps.

Stop criteria. Stop if an existing accounting-system view and reminders solve the task, nobody pays for setup after five suitable interviews, or paid-status checks cannot be made dependable.

Pilot estimate: 8–15 working days. One developer, working days; CSV import, assignment, hold flags, dates, history and draft templates in one client workspace. Excludes bank access, payment execution, automatic external messaging, debt collection, legal escalation and accounting reconciliation.

Evidence and limitations:

• NO01: How do you deal with clients who do not pay on time? — Contract worker reports four unpaid invoices, oldest 47 days overdue, and difficulty remembering and wording follow-ups. Limitation: Self-report, small discussion and no verified purchase. Author identity and independence not verified.
• NO02: Automating overdue invoice reminders — worth it? — Administrator at a small IT-services business describes growing manual follow-up workload and questions whether automation reduces work or adds complexity. Limitation: No quantified time savings or willingness to pay. Displayed date lacks a verified year; publication date left null.
• NO03: Overdue Invoices!! — Owner asks about reminder cadence; replies describe manual calls, existing automatic reminders and different treatment of customers. Limitation: Vendor recommendations in replies are not independent purchase verification. No legal or collection-policy claims adopted.
• NO04: Automatic reminders in Reckon Accounts Hosted — Bookkeeper asks for customer-facing overdue emails, distinguishing them from internal reminders; is disappointed that the suggested add-on costs extra. Limitation: Counterevidence to willingness to pay; older feature discussion does not establish current platform capability.
• NO05: How do you handle overdue invoice follow-ups? — Author discloses building a tool. Replies mention reminders sent to already-paid customers because payment matching lags. Limitation: Builder-led discussion, excluded from independent demand count. Reply anecdotes motivate a failure-mode test, not an incidence estimate.
• NO06: Zoho Invoice reminders — Official documentation supports manual reminders and automated reminders before or after due dates or expected-payment dates. Limitation: Strong existing substitute; regional documentation, no live account test.
• NO07: Zoho Invoice UK — Official product page markets free invoicing with reminders and receivables features. Limitation: Regional offer; usage limits and suitability require checking for the buyer. Free incumbent weakens a generic reminder SaaS.
• NO08: Chaser detailed pricing — Compact software is listed at $259/month or £199/month; annual USD equivalent is $233.10/month. Revenue tiers and usage extras apply. Limitation: Published pricing, not verified purchases. The proposed pilot is not equivalent in scope. Collection services and legal escalation are outside this research.

NO-O2: Payment confirmation for manually arranged appointments

For non-medical independent service providers who agree a slot by message: send a link for that exact appointment, intake details and an optional deposit. Track pending, paid, expired and manually cancelled states without exposing the whole calendar.

Decision: research next. Evidence confidence: medium problem low willingness to pay.

Buyer. Independent stylists, nail artists or other non-medical service providers who negotiate duration and appointment time before booking.

Competition. Square supports deposits for customer online bookings but documents a gap for staff-created bookings. Acuity starts at $20/month and the historical requester stayed with it. Mangomint offers a broad platform including Express Booking, priced at $120/location plus $10/user monthly in current search extraction.

Commercial test. Test $149 once for a configured confirmation flow; optional $19/month support later. Payment processor fees are separate. Neither price is validated.

Distribution. Hypothesis: booking-website implementers and existing service-business web clients. Demonstrate one exact-slot flow; avoid broad salon-software acquisition campaigns before paid pilots.

Main risk. Existing workflows may suffice, providers resist another subscription, and added deposit steps may reduce conversion or mishandle gift-credit customers. Deposits cannot eliminate no-shows.

Next test. Prototype exact-slot confirmation with payment test mode, expiry and manual exceptions; test with five providers and measure staff steps plus completion friction. Verify current incumbent workflows before asking anyone to switch.

Stop criteria. Stop if existing booking/payment links meet the exact-slot requirement, three pilot users prefer their existing workaround, or synchronization can double-book a slot.

Pilot estimate: 10–18 working days. One developer, working days; one calendar and one payment provider in test mode, exact-slot link, small intake form, expiry, webhook idempotency and admin status view. Excludes medical records, legal policy drafting, refund adjudication, live charging and a complete booking platform.

Evidence and limitations:

• NO09: Secure a pre-scheduled appointment with a deposit — Provider wants one assigned appointment link with form and payment instead of open-calendar booking. Later stayed with Acuity workarounds and grandfathered pricing. Limitation: Historical request; explicit retention of incumbent is counterevidence. Cannot claim the gap remains universally unresolved.
• NO10: Booking platforms for service providers — Solo provider finds client account creation cumbersome, values existing provider-side forms, and discusses deposit workarounds. Limitation: Adjacent booking-friction signal, not proof of demand for a specific confirmation add-on. No clinical functionality included.
• NO11: Last-minute appointments and no-shows — Stylist reports no-shows on late bookings and a frozen card preventing a later charge; changes booking lead time. Limitation: Individual experience, not causal proof of deposit effectiveness. An add-on cannot guarantee successful charges.
• NO12: No-shows and cancellations — Salon uses $25 haircut and $50 colour deposits for new guests yet still experiences missed appointments. Limitation: Direct counterevidence to claims that deposits eliminate no-shows. Policies and prices are anecdotal, not recommended terms.
• NO13: Deposit required when using a paid gift certificate — Customer objects to paying an additional deposit after buying gift certificates covering the whole service. Limitation: Buyer-side friction signal, not provider demand. No conclusion about legal enforceability or refund rights.
• NO14: Square Appointments deposits — Official US documentation includes deposits on Free and paid plans for online booking, but says taking deposits when staff book on a customer's behalf is unsupported. Limitation: Feature-specific, regional documentation; account behavior not tested. Existing invoices/payment links may still be substitutes.
• NO15: Acuity Scheduling pricing — Starter is advertised at $20/month or $16/month billed annually, including one calendar, payment integrations, email reminders and forms. Limitation: Page opened; dollar amounts were exposed in search extraction rather than the opened text. Recheck checkout before decisions; processor fees extra.
• NO16: Mangomint pricing — Advertises $120/location/month plus $10/user/month, Express Booking, deposits and forms. Advanced payment features require its processing. Limitation: Page opened; numeric prices exposed in search extraction. Broad platform is not a like-for-like add-on. No product test or verified purchase.

Test sequence

1. Start with attachment routing and supplier comparison using anonymized inputs, because outputs can be checked without contacting anyone or moving money.
2. Prototype exact-slot confirmation only in payment test mode. Test duplicate webhooks, expired holds, cancellation and gift-credit cases before proposing live use.
3. Compare each proposed flow with the customer's existing tool. A successful incumbent workaround is a result, not evidence to discard.
4. Seek explicit payment for a bounded setup only after demonstrating value. The five-conversation gates are proposed decision rules, not completed validation.
5. Measure delivery effort, exception frequency and support minutes before choosing subscription pricing. If recurring work is absent, retain a one-time service.

The research supports further validation, not a sales forecast. No market-size figures or invented conversion rates are included.