ChaseList

The problem in detail

Firms have no system of record for outstanding client documents. Requests scatter across email threads, WhatsApp messages, phone calls and portals clients never log into, so staff can't answer 'who still owes us what' without rebuilding a spreadsheet by hand. The result is hours of non-billable chasing each week, plus missing or duplicated records at close.

Proposed product

A document request tracker built around the channel clients actually use: text/WhatsApp and email reply-with-attachment. Staff build a per-client checklist of required items (bank statement, sales invoices, receipts, payroll summary, 1099s), set a due date, and ChaseList sends the request and escalating reminders automatically. Clients reply with a photo or attachment — no login, no portal — and the item is matched to the checklist line, renamed to the firm's convention, and dropped into the client's Drive/Dropbox/SharePoint folder. A single firm dashboard shows every open item across every client, days outstanding, and who was last nudged, so partners can see the chase status without asking staff.

Why now

The evidence shows no platform shift, price rise or rule change that opens this up now — document chasing is a long-standing problem that firms still solve with staff hours (Indeed bookkeeper listings include 'follow up with clients to collect missing documents', and VA vendors sell it as outsourced labour). What has changed only modestly is that several vendors now market SMS-based document collection to accountants, which suggests the channel is accepted but also that the obvious wedge is already taken.

Smallest useful version

A web app where a bookkeeper imports a client list, applies a reusable request template (e.g. 'Monthly close'), and hits send. Clients get an email and SMS with a plain list of what's needed and reply with attachments; inbound attachments are auto-matched to checklist items by the firm, one click, and synced to a mapped Google Drive folder. Automated reminders at day 3, 7 and 14 until an item is marked received. One dashboard: all clients, all outstanding items, sorted by days overdue. No client accounts, no mobile app, no e-signature, no ledger integrations.

Potential ways to charge

• Solo — £19 per month: one user, up to 25 clients, email reminders only, no SMS (typical for comparable tools; evidence has no incumbent prices)
• Firm — £59 per month: up to 5 users, unlimited request templates, SMS reminders with a monthly message allowance, Drive/Dropbox sync, firm-wide outstanding-items dashboard (typical for comparable tools; framed against the 8+ non-billable hours per request round estimated by Sliq360)
• Practice — £149 per month: up to 20 users, multiple entities, custom naming conventions, SharePoint sync, seasonal bulk sends for tax season (typical for comparable tools; anchored loosely to the $75–95/hr senior-staff follow-up cost cited by Enterprise DNA)
• Tax-season pass — £199 one-off for three months: full Firm features for the busy period only, for firms unwilling to commit to a year (typical for comparable tools; no evidence of seasonal pricing)

Routes to early customers

• Firms advertising bookkeeper roles on Indeed whose listings name client document follow-up as a duty — a direct signal they are paying for the task by hand
• Bookkeeping VA and outsourcing providers (the getmagic.com/bookkeeping model) who could resell or use the tool to run chases for multiple client firms
• Accounting-focused reviewer communities on Capterra where Content Snare's accounting reviewers already discuss document collection
• Independent bookkeeper networks and practice-management groups, approaching solo and small practices directly before tax season

Main risks

• Content Snare is an established, well-reviewed incumbent in exactly this ICP (93% small business, 42% accounting on Capterra) whose accounting reviewers already report reduced manual follow-up — ChaseList must beat a known product, not an empty category.
• The SMS/text-reply channel is already occupied by TextBetter, Text Request, Sinch and Soraban, so the wedge must be checklist matching, renaming and the firm-wide dashboard, which is harder to demonstrate in a demo than 'text your clients'.
• The riskiest assumption is untested: clients who ignore portals may also ignore SMS prompts, and attachment-to-checklist matching may take as long as the current ad hoc process.
• Data-protection duties around handling client financial documents over WhatsApp/SMS are an open question; firms may refuse the channel outright on compliance grounds.
• No search-demand or pricing evidence exists, so the firm may not perceive non-billable chase time as a budgeted line item worth paying for.

Questions to test first

• Run a single manual chase round for two or three real firms using a spreadsheet and your own phone: measure what proportion of clients reply by SMS versus ignore, and how long matching attachments takes.
• Ask five bookkeepers who currently use Content Snare or a portal what specifically still fails, to find out whether 'who still owes us what' is a felt gap or already solved.
• Put a pricing question to ten 1–20-person firms: what would they pay per month per user, and does the answer clear the cost of SMS delivery?
• Ask three firms' compliance leads or professional-body guidance whether receiving client documents by WhatsApp/SMS is acceptable in their practice.
• Test one-click attachment matching accuracy on a sample of real inbound emails and photos before building any automation around it.

Evidence and sources

The sources this assessment is based on. Evidence level: Indicative, counted from these sources as described in how ideas are assessed. Findings are what a source shows; anything the research only inferred is marked as an inference.

Research findings

• Supportsvendor blog posts · 30 July 2026

  Shows: stated failure mode of the incumbent solution class (portals clients won't log into)

  DokuTrak argues the blocker is friction and prescribes a no-account upload link with no login; Gridex similarly notes firms keep buying portals and organizers while the chasing still lands on staff, and cites an October 2025 ShareFile ad asking whether firms are still chasing clients for documents. This corroborates the candidate's core premise that portal adoption is the failure point — though all three sources are selling something, so it is vendor framing rather than neutral measurement.

• Supportsvendor and industry blog posts · 17 February 2026

  Shows: industry/vendor articles quantifying non-billable chase time

  Multiple independent vendor/industry posts quantify the pain in the same way the candidate describes: Sliq360 estimates 100 clients × 5 minutes of follow-up = 8+ non-billable hours per request round; Enterprise DNA estimates 18–25 hours a month of senior-staff follow-up at $75–95/hr. These are marketing-adjacent estimates, not measured data, so treat the magnitude as indicative rather than verified.

• Supportsjob board aggregator listings (Indeed)

  Shows: job-posting demand for manual document chasing

  Indeed bookkeeper job listings explicitly include duties such as 'Follow up with clients to collect missing documents' alongside kickoff calls and POA tracking, showing firms currently pay staff hourly to do the chasing by hand. A parallel VA-outsourcing vendor page (getmagic.com/bookkeeping) markets assistants to 'follow up with clients or vendors to gather missing receipts, bank statements, and supporting documentation', i.e. the task is routinely outsourced as labour rather than automated — the non-community, paid-work confirmation the brief asked for.

• Weakens the casesoftware review marketplace (Capterra) · 21 July 2026

  Shows: incumbent product with verified buyer reviews in the exact ICP

  Capterra lists Content Snare as a document/information collection tool whose reviewer base is 93% small business and 42% Accounting; reviewers from accounting firms describe using it for tax document requests, onboarding and compliance and say it 'reduced the amount of manual follow-up required'. This validates that small firms buy tooling for this exact job, but also means ChaseList enters a category with an established, well-reviewed incumbent that already sends automated reminders without client logins.

• Weakens the casevendor marketing pages · 8 May 2026

  Shows: competing vendors already selling the SMS/text-reply document collection angle

  TextBetter markets secure CPA texting where clients text photos/documents; Text Request and Sinch publish accounting-specific SMS document-collection use cases; Soraban (seen in a SourceForge listing) auto-reminds tax clients via SMS, email and voicemail. The 'clients reply by text' channel is therefore already occupied at the messaging layer, so ChaseList's defensible wedge would have to be the per-item checklist matching, renaming and firm-wide outstanding-items dashboard rather than texting itself.

Where the problem was reported

Public posts in which people described this problem, grouped into one problem before research began.

• Question for UK Bookkeepers: How do you manage missing client documents? · r/Accounting · 11 July 2026
• Accountants: what’s your preferred client document collection workflow each month? · r/Accounting · 22 February 2026
• Anyone working at accounting firm with 10 - 50 people and used AI/automation? · r/Accounting · 19 February 2026
• What would your ideal client document portal actually look like? · r/Accounting · 17 December 2025
• UK Accountants: What's the biggest admin killer when collecting client documents? · r/Accounting · 5 November 2025
• Following Up with Clients Who Don't Like Tech · r/Bookkeeping · 28 April 2025
• Accountants - I'm researching how much time accountants actually waste chasing client documents · r/Accounting · 25 January 2025

Looked for, not found

• No keyword-volume data (e.g. for 'document chasing software for bookkeepers'), no public issue tracker, and no dated individual support complaint against an incumbent were returned by the searches run. Pricing tolerance for a 1–20-person firm, and whether firms would accept WhatsApp/SMS attachment handling given data-protection duties, are therefore untested; the compliance question in particular is only a hypothesis at this stage.