Pricing — automated bookkeeping for small business | Stillpost

Question 1

Do I have to switch banks to wire up Stillpost?

Accepted Answer

No. The bookkeeping loop reads Plaid-supported banks — Mercury, Stripe, Square and Brex plus the long tail of Plaid institutions — without a migration step. The connection is read-only: the loop pulls a transaction list, the credentials never leave the vault, and the operator keeps the same banking relationship, the same card, and the same ownership they had before. Multi-account setups (operating + payroll + reserve, or main + a card-issuer sub-account) all read in parallel; the loop reconciles against the main operating account the operator picks during wire-up. Switching banks once Stillpost is wired up is also a dashboard thing — revoke the old connection, add the new one, and the loop picks it up on the next 6:00 cash-flow pull (no analyst in the loop, no cutover window to schedule). Per-institution coverage is whatever Plaid supports at the time of connect; an unsupported bank blocks the wire-up early and the operator gets a reply within one business day rather than a half-built loop.

Question 2

What does “multi-state sales-tax” actually cover across states?

Accepted Answer

Pro and Managed run a fifty-state sales-tax estimator: per-state pegs (nexus thresholds mapped to the operator’s footprint), per-state accrual (the running liability the loop posts each night at 23:55), and the next remittance date flagged in the weekly margin digest. The estimator pulls from Avalara and TaxJar alongside the per-state DOR (Department of Revenue) feeds — the operator picks the upstream, the loop reads from the same one on every pull so the published rate and the loop’s posted accrual can’t drift apart. Managed files the actual returns. Pro estimates and accrues — the operator files. Starter ships without the sales-tax layer at all (it’s the single piece of the weekly loop that’s not in Starter; the entry below covers what isn’t in Starter). Multi-state nexus threshold monitoring is on by default across Pro and Managed — when an operator is about to cross into a new state, the loop surfaces it in the next digest rather than waiting until the filing window closes.

Question 3

How does the overdue-invoice chasing actually work?

Accepted Answer

The 9:00 cron step reads the invoice aging report and sends a polite chase email — one nudge per invoice, on the day it ages past its term, at 9:00 instead of at the end of the week. Inbound invoice pickup runs from Gmail and Outlook (plus QuickBooks and Xero when the operator wires them in): the loop reads what arrives, ages each invoice against the term the invoice itself carries, and queues the next chase. The escalation is fixed at three touches (day 1, day 7, day 21) and stops the moment the invoice is paid — there is no further mail without a human override. The chase tone is configurable from the dashboard when an operator wants a softer or firmer touch; the default matches the language the operator would have written themselves, not a templated “please pay your invoice” mass-mail. Disputes pause the cadence automatically: when an invoice is marked disputed in the dashboard or a reply mentions dispute language, the loop pauses the sequence and parks the invoice for a human reviewer rather than continuing to chase a bill that’s already in conversation.

Question 4

What’s actually different between Connect, Run, and Scale?

Accepted Answer

Connect is wiring and the homework-saving layer: the bank feed, the inbox pickup, the overdue chaser fired on day 1 / 7 / 21, the nightly receipts reconcile, the weekly margin digest. It’s the loop that stops the bookkeeping/receivables tax on a single-account operator — one bank, one inbox, one POS. Run is where the full autonomous back-office loop turns on: unlimited Plaid-supported connections, the monthly fifty-state sales-tax estimates pegged to the actual state-by-state remittance calendar, the period close that posts itself, and the margin guardrails that catch a cost spike before lunch. Scale is Run with a human review on top — fractional-CFO working hours, audit-ready books, coordinated sales-tax filings, and a quarterly strategy review on the books themselves.

Question 5

How does Stripe billing actually work — and can I cancel any month?

Accepted Answer

Checkout is Stripe’s hosted page; the operator enters a card once and the subscription runs on the cadence the operator picked (monthly for Connect, monthly or annual for Run and Scale). The charge number you see on the card statement is the post-cut dollars — the public <$81 / $243 / $1,620+ headlines already discount 10% off the base, and that’s the figure Stripe actually invoices. Cancel any time from the Stripe customer portal (link in every receipt email): the loop keeps running through the end of the period you’ve already paid for, then stops without a retention call. Switch tiers at the next renewal — upgrade from Connect to Run when the fifty-state sales-tax obligation shows up, or back down to Connect when the audits don’t need a human review. Annual cadences save the monthly-equivalent cost; a partial-period refund is supported through Stripe on request.

Capability	Connect	Run	Scale
Cash-flow visibility	6:00 daily pull on the operating account	6:00 pull + cash-flow forecast by account	6:00 pull + CFO review of weekly run-rate
Overdue-invoice chasing	Day 1 / 7 / 21, polite	Day 1 / 7 / 21 + tone config + dispute auto-pause	Day 1 / 7 / 21 + tone config + human escalation
Nightly receipt reconciliation	Nightly auto-match against bank + POS	Nightly auto-match + inbox pickup (Gmail / Outlook)	Nightly auto-match + inbox pickup + audit dossier
Sales-tax estimates	—	All 50 states, dated to the remittance calendar	All 50 + coordinated filings end-to-end
Weekly margin alerts	Weekly margin digest	Weekly margin alerts (cost-spike detection)	Weekly margin alerts + quarterly strategy review

Priced like software.

Capability deltas, side by side.

Frequently asked, before you pick a tier.

Drop your email. We'll send the next launch note.