Product concept · v0.1
Accounting for people who would rather not.
Quiggy keeps a business's books permanently done. It reads receipts, bank lines and invoices as they happen, posts them itself, files with the tax office on time, and only talks to you when something needs a human. Underneath, it is a full double-entry ledger a Big Four auditor would trust. On top, it speaks plain English.
Always posted
Nothing waits in a shoebox. Every receipt, card swipe and bank line is in the books within minutes, with a confidence score and a paper trail.
Never late
VAT returns, MTD submissions and annual accounts are drafted from live books and submitted through official APIs after sign-off. Late filing stops being possible.
Plain by default
No debits, credits or chart of accounts unless you ask. "Will you use this for more than a year?" is how Quiggy decides what's an asset.
The flip
Every accounting tool digitised the ledger. Quiggy digitises the accountant.
Xero and QuickBooks made bookkeeping software. The person still has to do the bookkeeping. Quiggy inverts the default: the books are done unless Quiggy says otherwise.
Capture
Two ways in. Both end with a posted entry.
The single receipt on your phone and the shoebox of a hundred are the same pipeline; the second just runs it in bulk without asking you anything it can work out itself.
- Amount you typed
- 44.40
- Amount on receipt
- 44.40 ✓ match
- Filed as
- Client entertainment
- Linked to
- Northlight · SKO 2027
- Matched to
- Card ···4471, 12:38
Flow one: a single receipt, ten seconds
Photograph the receipt
Edge detection, glare removal and multi-page capture happen on-device. Thermal receipts and handwritten ones both work.
Say what it was for, in your own words
Voice or text. "Lunch with Sarah about the kickoff" is enough. If Quiggy already knows the merchant and the card swipe, you can skip this entirely.
Type the total
Your number is checked against the number Quiggy read. A match posts instantly; a mismatch shows both and asks which is right. It is the cheapest quality control in accounting.
Quiggy posts it
Account, VAT treatment, currency, client or project, and the matching bank or card line are all resolved. The image is sealed in write-once storage with a hash, which is what an auditor wants to see.
You see a confirmation, not a form
If confidence is high, the screen just says "Posted." If not, a single plain question appears. Never a dropdown of 200 accounts.
Flow two: the shoebox
Connect a mailbox, drop a folder of scans, or photograph a stack. Quiggy runs the same pipeline a thousand times, then hands you one short list.
- Gmail / Microsoft 365 comb (read-only, receipts and invoices only)
- Forward-to address per entity
- Bulk photo or scanner upload
- Supplier portals (Amazon, Uber, SaaS invoices)
- Vision model extracts merchant, date, lines, totals, VAT, currency
- Deduplicates against everything already seen
- Flags non-receipts and personal spend
- Pairs with bank feed and card transactions by amount, date, merchant
- Splits and tips handled
- FX resolved to the rate the bank actually used
- Account, tax code, project from the business's own history
- Confidence score per field
- Rules learned from every correction
- High confidence: posted, sealed, done
- Everything else: one "needs you" pile, grouped so ten similar items become one question
How it decides
Act on everything. Interrupt for exceptions.
The whole product rests on the "needs you" pile being short and every question in it being answerable by a normal person in one tap.
When Quiggy interrupts
Who it's for
One hierarchy from a freelancer to a Big Four firm.
The data model is firm → entity → person from day one. A sole trader is simply a firm of one with one entity. A Big Four office is a firm with four hundred entities and a white-label login page.
The accounting practice
Bookkeeping firm, accountancy practice, Big Four office, or the business itself when it has no accountant.
- White-label: own domain, brand, emails
- One review queue across every client
- Period close and filings, prepared by Quiggy, signed by staff
- Staff roles, engagement scoping, client billing
- Firm-wide rules ("we always treat X as Y")
The legal business
A company, a sole trader, a branch. Multi-entity groups consolidate upward.
- Own ledger, chart, tax registrations, fiscal year
- Own bank feeds, cards, mailboxes
- Own data residency region
- Own audit trail and document vault
- Two-way sync to Xero / QuickBooks / Sage if the firm wants it
Owners, staff, spenders
Anyone who spends money or needs to see it.
- Owner: everything, in plain language
- Spender: capture only, card in wallet, no access to books
- Approver: bills and expenses over a limit
- Viewer: investors, board, lenders
- Accountant: the real ledger, always
Modules & pricing
Pay for the modules you switch on. Everyone gets the core.
Modules are how a freelancer and an enterprise use the same product at different prices. The core is deliberately generous, because the core is what makes people trust the books.
- Core, one entity, one person
- Filing module included (the promise matters most here)
- Cards and invoicing as add-ons
- Core, up to 25 people
- Any Money and Compliance modules, priced per module
- Accountant seat free, always
- Firm modules, white-label, review queue
- Volume steps at 100 / 500 / 2,000 entities
- Firm resells or bundles into its fee
- Multi-entity, consolidation, SSO, SCIM, dedicated region
- Custom retention and audit exports
- Option for own-licence banking later
Prices are indicative placeholders for the model, not a proposal. Usage that costs us real money (card interchange, payment processing, per-filing fees, payroll partner fees) is passed through with a margin so pricing scales with the customer rather than punishing small ones.
Stack
Built for one very productive builder and an auditor.
One language end-to-end, managed services wherever a vendor already carries the compliance burden, and a purpose-built ledger at the centre. Picks marked "to confirm" are candidates whose terms or regional coverage are being confirmed.
Why TigerBeetle and not "just Postgres": a ledger that cannot go out of balance is the difference between a bookkeeping app and financial infrastructure. It also makes the own-licence step later far cheaper, because the same ledger that holds a client's books can hold real customer funds.
Compliance by design
Every framework you named maps to an architecture decision, not a policy document.
SOC 2 Type 2 and ISO 27001 are the entry ticket for firms. GDPR is table stakes in the EU. HIPAA only matters if a firm's clients include US healthcare practices, so it is designed in but switched on per entity.
Regulatory path
Rent the licence first. Design as if you'll own it.
Cards, accounts and payments are regulated money. Partners let Quiggy ship in months. The architecture keeps the door open to an own licence when a Big Four-scale customer asks for it.
Technical service provider
- Stripe or Swan hold the funds and the licence; Quiggy is the experience
- Quiggy owns KYC data, ledger, customer relationship
- No regulatory capital, no MFSA application yet
- Constraint: partner's country coverage and margins
Registered agent of a licensed EMI
- Quiggy appears on the register, can onboard and service customers directly
- Better economics, shared compliance function
- First AML officer, first compliance hire
- Proves the operating model regulators will inspect later
EMI licence, MFSA (Malta)
- Passportable across the EU/EEA; UK via FCA separately
- Safeguarded client funds, own BINs, own interchange
- Capital, board, three-lines-of-defence, 12–18 months
- Only worth it when funds under management make the margin matter
What the architecture does now so Stage 3 is a swap, not a rebuild
Every money movement goes through one internal "rail" interface: issueCard · openAccount · pay · collect · fx. Stripe and Swan are adapters behind it. When Quiggy holds its own licence, the adapter becomes Quiggy's own core banking on the same TigerBeetle ledger, and no product surface changes. KYC, AML screening and transaction monitoring are run by Quiggy from day one (Sumsub, ComplyAdvantage), so the regulator sees a compliance function that already exists rather than one being invented for the application.
Roadmap
A pilot in Malta and the UK first, then the promise, then the world.
Ordered so each phase produces something a real accounting firm will pay for, and so the SOC 2 Type 2 observation window is running from the first commit.
Foundations. Concept locked, design system, compliance scaffolding, first firm signed as design partner.
- Brand and design system for Quiggy and the white-label shell
- Monorepo, AWS + Vercel, Vanta connected, policies drafted
- TigerBeetle + Postgres ledger with the plain-language layer over a Malta chart of accounts
- Design-partner firm interviews: what does their review queue look like today?
Books that do themselves. Capture, matching, posting and the firm queue, for Malta and UK entities.
- Mobile capture with the typed-total cross-check
- Mailbox comb and bulk upload
- Bank feeds via TrueLayer / GoCardless
- Autonomy engine, "needs you" pile, plain ↔ ledger toggle
- Xero and QuickBooks two-way sync
- Firm review queue, first white-label domain
Never late, and the swipe is the receipt. Filing and cards make the promise real.
- HMRC MTD VAT submission; Malta VAT returns
- Period close, annual accounts drafts
- Quiggy cards via Stripe Issuing / Swan with instant receipt prompts
- Invoicing and getting paid
- SOC 2 Type 2 observation window complete; report issued
Scale outward. US, EU country packs, payroll, bills, forecasting, enterprise identity.
- US entities: Plaid, Avalara sales tax, US chart
- Country packs for the largest EU markets
- Bills and approvals, payroll partners, cash forecast
- SSO / SCIM, ISO 27001 certification
- Public API and webhooks
- Stage 2 regulatory conversation begins
Open decisions
Still yours to call.
None of these block Phase 0. Each one changes something in Phase 1 or 2.
Who is the design partner?
A practice with 100–300 clients shapes the review queue fastest. Larger firms join once there is something running to show.
Is our own company entity number one?
Multi-currency projects, expenses across countries and a SOC 2 audit already underway make it a strong first entity, and dogfooding fixes the capture flow fastest.
How opinionated is the plain-language layer per country?
Malta and the UK differ on what is reclaimable and depreciable. The questions Quiggy asks are country-specific data. Who writes and signs off those packs: us, or the firm?
Card programme geography
Stripe Issuing covers US, UK and much of the EU from one integration; Swan is EU-native. Decide by where the first hundred card-carrying customers will be.
Pricing the firm tier
Per client entity is simplest. Firms may prefer a platform fee plus usage. Worth testing on the design partner before Phase 2.
Name and brand register
Quiggy is warm and memorable for owners. Firms will show it white-labelled, but enterprise buyers will see it on the contract. Check trademark availability in EU, UK and US early.