Result

# Plan Review: B2B accounting SaaS for solo founders

Hold on. Before we review anything, we need to talk about what we're actually reviewing.

You handed me "B2B accounting SaaS for solo founders." That's not a plan. That's a market category. I can't review architecture, code quality, tests, or performance against a market category. There's no design doc, no scope, no codebase, no diff, no problem statement.

So I'm going to do the most useful thing I can: pressure-test the premise before you spend a single hour building.

## Step 0: Scope Challenge (the real one)

Let me ask the questions a good eng manager asks before greenlighting work:

**1. Who exactly is the user?**

"Solo founders" is not a user. A solo founder running a 6-person agency on $40k/mo revenue has nothing in common with a solo founder pre-revenue building a consumer app. The first one has W-2 contractors, sales tax in 3 states, and an LLC taxed as an S-corp. The second one has a Stripe account and a Mercury balance.

Which one are you building for? Pick one. Write it down. If you can't name three real people who match the description and would pay you next month, you don't have a user yet.

**2. What is the job to be done?**

Accounting is not a job. It's a category. The actual jobs are things like:
- "File my taxes without paying $3k to a CPA"
- "Know if I can afford to hire someone"
- "Send invoices and chase payments without losing track"
- "Categorize 400 Stripe transactions a month so my books aren't garbage at year-end"
- "Be ready for due diligence in 90 days"

Each one is a different product. The first is a tax filing tool. The second is a cash flow dashboard. The third is invoicing + AR. The fourth is bookkeeping automation. The fifth is investor-grade reporting.

Which one is the wedge? You need exactly one to start.

**3. Why hasn't this been built? (It has.)**

This is the part where most plans fall apart. The landscape:

- **QuickBooks** — owns SMB. Bloated, hated, sticky.
- **Xero** — same shape, slightly less hated.
- **Wave** — free, owned by H&R Block, exists.
- **Bench** — bookkeeping-as-a-service, raised $100M+, went bankrupt in Dec 2024, got acquired.
- **Pilot** — bookkeeping for startups, well-funded, well-run.
- **Puzzle** — accrual accounting for startups, YC-backed, going hard.
- **Digits** — AI-native accounting, raised ~$100M.
- **Found, Lili, Relay** — banking + light bookkeeping for solopreneurs.

The graveyard is bigger than the list of survivors. Bench just died. That should make you nervous, not excited. It means the unit economics of "do accounting for small customers" are brutal: low ACV, high support burden, customers who don't know what they need, churn when they grow into QuickBooks.

What do you see that the people who raised $100M and went broke didn't?

**4. What is your unfair advantage?**

Be honest. "AI" is not an answer. Digits and Puzzle have been shipping AI accounting for 2+ years. "Better UX" is not an answer. Every founder thinks they have better UX.

Real unfair advantages look like:
- You were a CPA for 8 years and know exactly which 3 workflows cost agencies $50k/yr in human time
- You built the data pipeline at a previous accounting startup and know the integration shortcuts
- You have distribution to a specific community (e.g., you run a 50k-person solo founder newsletter)
- You found a regulatory wedge competitors can't touch

If you don't have one of these, you are about to compete on features and price against well-funded incumbents in a market with terrible unit economics. That ends one way.

**5. What's the smallest thing you could ship in 2 weeks that proves someone will pay?**

Not the platform. Not the AI-native rewrite of accounting. The smallest thing. Examples:

- A spreadsheet + a Calendly link where you do the work manually for 5 paying customers
- A Stripe → Google Sheets categorizer that costs $19/mo and replaces 4 hours of monthly bookkeeping
- An invoice-chasing email bot that integrates with Stripe and goes after net-30 deadbeats

Charge money. Day one. If five solo founders won't pay $20/mo for the smallest version, they won't pay $200/mo for the full version.

## What I'd actually recommend

I can't review a plan that doesn't exist. So here's the move:

**Run /office-hours before you run /plan-eng-review.** That skill is built for exactly this moment. It produces a structured problem statement, challenges your premise, explores alternatives, and gives a real eng review something to bite into. Takes about 10 minutes. You'll come out with:

- A named user (specific, not "solo founders")
- A specific job to be done (one, not five)
- An honest competitive read
- A wedge hypothesis
- A 2-week shippable test

Then come back here with a design doc and a diff, and I'll review the architecture, tests, performance, and scope against real engineering questions.

## Verdict

**STATUS: NEEDS_CONTEXT**

**REASON:** "B2B accounting SaaS for solo founders" is a market category, not a plan. There's no design doc, no problem statement, no scope, no code, and no diff to review. The category is also a graveyard. Bench died last year. Building here without a sharp wedge is a multi-year way to lose money.

**ATTEMPTED:** Tried to pressure-test the premise instead of reviewing a non-existent plan.

**RECOMMENDATION:**
1. Run `/office-hours` to sharpen the problem.
2. Pick one user, one job, one wedge.
3. Build the smallest paid version in 2 weeks.
4. Come back with a real design doc and I'll do the eng review properly.

If you want to push back, here's the most useful thing you could tell me right now: **who is the specific person you're building this for, what do they do today that's painful, and why are you the one who can fix it?** Answer that and we have something to work with.