[jfrench9]

Summary

Brings the homepage up to date with six weeks of shipped features, fixes three claims that had gone wrong, names the price, and adds groups and consolidation as a first-class part of the page, without making it the headline.

The first commit led the hero with the group ("Your group's books. Consolidated."). The second walks that back to "Connect your books. Ask your AI.", with the group as a sentence beside it. Every search impression roboledger.ai has had in 90 days is about QuickBooks with an AI chat, and none is about groups. Search demand runs about ten to one in the same direction ("ai accounting software" 1,600 a month, "quickbooks mcp" 720, against "accounting software for multiple businesses" 260). The group story moves into the headline once asks on it convert, or once more than one QuickBooks company per group can connect.

Changes

Hero, title, social card

• Headline and badge unchanged from main. The subhead adds: "One company or a whole group: each keeps its own books and close, and your AI drafts the consolidation."
• SITE_TITLE unchanged; SITE_DESCRIPTION adds "consolidate a group" (146 chars). The social card's subtitle now matches its title.
• llms.txt describes the group and the price.

Groups & consolidation (new)

• A Groups spotlight, second after live statements, on a new demo (public/demos/group.js): Driftline's August 2026 consolidation worksheet, rounded to the dollar, with the drafted adjustments named one at a time and a person closing the group's month.
• Proof band: "Nothing writes back", then "Consolidated, not combined", then "Every figure opens".
• How It Works: the group is optional at each step. Only the parent's QuickBooks connects; the other companies come in through a bank feed and an opening balance sheet.
• FAQ: a consolidation question (what is built, and what is not: other currencies, a group inside a group). The "several clients" answer now separates a client's group from unrelated clients.
• Footer link to /#groups; spotlights get anchor ids.

Features since the last pass

• Drill to the account register, figure lineage, segment columns, CSV on every statement.
• Bank reconciliations, loan and custom-curve schedules.
• Learned suggestions with bulk approve, Posting Rules, settle-from-line, AR/AP aging.

Claims fixed

• The inbox "autopilot for trusted sources" (no such setting).
• "the parent's statements combine them" (they consolidate).
• Event-handler rules "without a dedicated form" (Posting Rules reviews and approves them now).
• The retired-phrase guard gains these, plus "the system consolidates" and "all your quickbooks companies".

Price

• $99 a month per graph (Standard) in the FAQ and final band, with a link to robosystems.ai/pricing, and an Offer in the SoftwareApplication JSON-LD. A group's companies share one graph; Standard has no entity cap.

Keywords

• Adds "multi entity accounting software", "multi-entity accounting" and "combined vs consolidated financial statements" after the existing terms. The holding-company and LLC phrasings read blank on volume, so they are not used.

Deploy Notes

None

Testing

• npm run test:all gate via the pre-commit hook: format, lint, typecheck, 1,236 tests passed.
• npm run build not run.
• The group demo not yet checked in a browser.

🤖 Generated with Claude Code

[github-actions]

Change classification: normal — platform or application code changed.

A normal change carries a documented automated review on this pull request before merge, in place of a second human approver. The change-classification job requests that review and passes once it has been posted. Recorded by the change-classification job.

[jfrench9]

@claude please review this PR

[claude]

Claude finished @jfrench9's task in 55s —— View job

---

Review of PR #529: landing refresh (groups, new features, price)

Overall this is a careful, well-scoped copy and metadata pass. I found nothing blocking. I read the full diff and public/demos/group.js, but I did not run the build, the tests or the app, so the items below are from reading the code.

Checked and fine

• Worksheet figures in group.js: every column foots.
  • Revenues 135,830 + 21,400 + 19,600 = 176,830, less the 1,230 intercompany adjustment = 175,600.
  • Net income: 25,862 combined, plus the 1,080 equity share (40% of 2,700), less the 1,504 outside owners' share (30% of 5,012 = 1,503.6), gives 25,438. The adjustments column nets to −424 (1,080 − 1,504).
• Demo wiring: group is registered in render.html. The kit.js imports resolve, because kit.js re-exports runtime.js. ctx.nav('statements') is used by other demos.
• Spotlights: the "Seven views" count matches the seven spotlights. The new ids and scroll-mt-24 give the /#groups footer link a target.
• Retired-phrase guard: the new phrases cover the claims this PR removes.
• Description length: the new SITE_DESCRIPTION stays under 160 characters.

Things to check before merge

1. Docs link may 404. FaqSection.tsx links to /docs/consolidate-a-group. The docs pages come from a remote catalog (getDocsCatalog() in src/app/(docs)/docs/[[...slug]]/page.tsx), so no file in this repo confirms the slug exists. Unknown slugs return notFound(). Please confirm the page is published in the catalog.

2. Bank-feed claims versus Mercury being off in production.

   • CLAUDE.md says the Mercury provider is gated off in production.
   • The new copy leans on bank feeds: the "Bank feeds" tag on step 01, "Bank lines arrive with a suggested account" in step 03 and the inbox spotlight, and "the other companies … come in through a bank feed" in the FAQ.
   • The FAQ also lists "the API or a file", which is accurate.
   • If no bank-feed provider is live for a customer today, step 01 and the inbox spotlight overpromise. Either confirm another feed path is live, or soften the tag and wording.

3. Strong claim in the pricing FAQ. "It's open source with no outside investors, so nobody can reprice it or shut it down on you" is a promise that is hard to keep. Open source doesn't stop the hosted service from being repriced or shut down. Consider "you can fork it and run it yourself", which matches the existing platform FAQ wording.

4. Awkward sentence in HowItWorks.tsx step 01. "For a group, add each company with the share the parent holds, with a bank feed and an opening balance sheet." The two "with" clauses read as if they modify the same thing. For example: "add each company with the share the parent holds, an opening balance sheet and a bank feed."

5. Structured data price. structured-data.ts now advertises $99/mo, while the FAQ says comparing against public companies adds the SEC subscription. That is fine for a base-price Offer, but the price now lives in four places: FAQ, final band, llms.txt and the JSON-LD. A shared constant would keep them in step when pricing changes. Optional.

6. Not yet verified, as the PR says. npm run build wasn't run and the group demo hasn't been checked in a browser. Please check these in the demo:

   • the phone layout, which hides the .mc columns;
   • the poster: 11.5 frame against TOTAL = 12.5;
   • that the ring lands on the right cell for each note.

   Given the CLAUDE.md note about Next 16 differences, a quick npm run build is worth it.

Nits

• FinalCTA.tsx: "$99 a month for the whole group's books" reads oddly for a single-company visitor. "$99 a month per graph" matches the FAQ.
• The footer label is "Consolidation" but the section is titled "Groups & consolidation". That is fine, just noting it.
  · branch feature/landing-refresh-new-features