ERPClaw Q2 2026: What Shipped, What's Next

This is the first ERPClaw quarterly update. The headline for Q2 2026: we shipped two deep integrations, deployed seventy-three pages of marketing site, and rebuilt the demo around three personas with fourteen scenarios.

I am going to tell you what shipped, what is broken or partial, what is coming next, and the actual numbers behind the project. No spin. The point of writing these every quarter is to leave a public paper trail that an investor, an advisor, a potential user, or a future me can scroll through and tell whether the curve is bending the right way.

If you have not seen ERPClaw before, the short version: it is an open source, AI-native ERP. Forty-eight modules. Three thousand one hundred and forty-eight actions. Seven hundred and eighty-nine tables. One SQLite database that lives on disk in a single file you own. open source, free, runs locally, driven by your AI assistant in natural language. The full story of why our co-founder Nikhil started building it lives in from SAP consultant to open source builder.

Now to this quarter.

What shipped

Stripe v1.0 went live on Stripe Marketplace

The biggest shipment of Q2 was the Stripe deep integration reaching v1.0 and getting listed on the Stripe Marketplace. Sixty-seven actions, ten functional domains, twenty-eight tables, full ASC 606 revenue recognition, MRR and churn reports, Stripe Connect application fee accounting, and per-event GL posting that survives the twelve step validation engine.

The internal architecture is the part I am most proud of. Every Stripe webhook lands in an event store, gets deduplicated by signature plus event ID, fans out to a handler that writes draft entries, and then either auto-submits or queues for review based on the merchant’s configured policy. Connect fees, refunds, disputes, payouts, and subscription proration all flow through the same pipeline. The accountant sees journal entries with the original Stripe object IDs in the memo line so any line item is traceable back to the source in two clicks.

The full feature surface lives at /features/stripe and the integration docs are at /docs/stripe/install-walkthrough/. If you want the deep dive on why ASC 606 belongs inside the integration rather than in a separate report tool, that is at /blog/stripe-asc-606-revenue-recognition-guide/.

For context on where this lands in the market, the Rillet alternative comparison is the cleanest framing. Rillet charges around $1,500 a month for a similar surface. ERPClaw charges $0.

Shopify v1.1.3 with App Store OAuth, status mirror, GDPR webhooks, and a daemon

Shopify caught up to Stripe in code surface this quarter. v1.1.3 ships with sixty-six actions, fifteen functional domains, eleven tables, and a real installation flow that goes through a Cloudflare Worker for OAuth pairing rather than the v1 hand-pasted token mess that almost cost me a week.

The new bits in v1.1.3:

• App Store OAuth flow via Cloudflare Worker (the Worker holds nothing; it does the token exchange and hands the credential back to the local install)
• Status mirror so the merchant can see installation health, last sync, webhook backlog, and reconciliation status from a single page
• All seven mandatory GDPR webhooks (customers/data_request, customers/redact, shop/redact, plus the four newer privacy events)
• Daemon mode that subscribes to the Shopify event bus and processes webhooks asynchronously rather than the v1 polling loop

App Store submission is open but pending review. Shopify’s queue is what it is. I will write a separate post when the listing goes live.

The Shopify launch post is at /blog/erpclaw-now-on-shopify-app-store/ and the full feature page is at /features/shopify. For the buyer-intent comparison, the A2X alternative post and the Synder alternative post cover the head-to-head.

Website rebuild from twenty-eight to seventy-three pages

The marketing surface at start of quarter was twenty-eight pages, mostly placeholder copy left over from the launch. By end of quarter it is seventy-three pages, all real, all indexed, all built on Astro content collections so we can scale without architectural drag.

The breakdown:

• 9 comparison pages (A2X, Synder, Rillet, Bookkeep, Webgility, Xero, FreshBooks, ERPNext, QuickBooks)
• 13 vertical pages (ecommerce, SaaS, agency, restaurant, manufacturer, nonprofit, legal, real estate, solo founder, small business, accountants, healthcare, education)
• 12 documentation pages (six per integration, plus the landing matrix)
• 17 blog posts (this one is the eighteenth)
• The remaining headline pages: features, pricing, demo, security, quality, privacy, the integration landings, and the founder page

Schema.org coverage went from one (incorrectly applied SoftwareApplication on every page) to eight correctly typed schemas (SoftwareApplication for the homepage, Product for feature and comparison pages, FAQPage on pricing, BlogPosting on every blog, Article on every doc, BreadcrumbList auto-derived on every non-home page, Organization on the footer, AboutPage on the founder and security pages). Sitemap went from a 404 to fifty-eight indexed URLs (and counting; we add as we publish).

If you want to inspect the catalog yourself, /docs is the integration matrix and /blog is the full post index.

Animated demo with three personas and fourteen scenarios

The old demo was a single linear walkthrough that showed a generic small business. It converted poorly because nobody is a generic small business. They are a Shopify merchant, or a SaaS founder, or an agency owner, or a restaurant operator, and they want to see the screens that match their reality.

The new /demo ships with three personas (Shopify merchant, SaaS founder using Stripe, multi-location restaurant operator) and fourteen branching scenarios across them. Each scenario is a real flow with real data running against a real ERPClaw instance, animated so a visitor can see what the assistant does without having to install anything. The state persists in localStorage so a visitor can leave and come back to where they were.

This is Phase 1 of the demo plan. Phase 2 is the in-browser sandbox using WebVM/CheerpX so a visitor can actually drive the system rather than watch it. That is queued for Q3 once the commercial license review closes.

Analytics, AI bot opt-in, and per-page OG image generation

A handful of smaller things that mattered:

• GA4 installed in the Layout component so every page emits engagement, time on page, and conversion events
• robots.txt rewritten to explicitly allow ClaudeBot, GPTBot, PerplexityBot, Google-Extended, Bytespider, CCBot, Applebot-Extended, Amazonbot, and meta-externalagent (the bet is that AI search citations are going to matter more than rank position over the next eighteen months, and the right move is to be in the training data on day one)
• Per-page OG image generation so every comparison, vertical, doc, and blog post gets a branded Open Graph card automatically when the page builds

Founder writeup picked up by HackerNoon

The HackerNoon feature on the previous indie SaaS project (ZapInventory) ran in mid-Q2. It drove a small but real spike in GitHub stars and inbound LinkedIn messages. The follow-up post on ERPClaw specifically is being drafted for Q3 placement.

What is broken or partial

I would rather flag this stuff myself than wait for a user to find it.

Shopify App Store listing is pending

The integration is built, tested, and submitted. The listing is in Shopify’s review queue. I do not control the timeline. Until it lands, merchants can install via the custom app flow documented at /docs/shopify/app-store-vs-custom-app/, which is functionally identical but does not get the App Store distribution.

Multi-currency support gap

Both Stripe and Shopify integrations currently assume a single base currency. If your store sells in EUR and your books are in USD, you have to manually configure the exchange rate per period. This is the single largest gap I am hearing about from prospective users. Multi-currency v1.x is the highest-priority Q3 item, scoped to support FX revaluation, presentation currency separate from functional currency, and intercompany consolidation for multi-entity setups.

WebClaw UI for Stripe and Shopify is still CLI-only

WebClaw, the optional dashboard layer, currently does not surface the Stripe or Shopify integration views. Everything works via the natural language assistant or direct CLI invocation, but a merchant who wants a clickable dashboard for their Stripe MRR or Shopify reconciliation status has to wait. The dashboard views are in flight; ETA is mid Q3.

Main website server deploy backlog

The avansaber.com main website (the parent company site, not erpclaw.ai) has a privacy-stripe.php page authored locally but blocked on an SSH key issue with the GitLab origin. The Shopify privacy page is live; the Stripe one is stuck in commit limbo. Cosmetic for now since the integration itself does not depend on it, but I want it cleared before pushing the App Store listing live.

Server deploy of the seventy-three page site happened post-quarter-close

The full Astro build finished on 2026-04-26 and the rsync to RunCloud landed shortly after. Traffic numbers below reflect that, which is to say: the site has been live in its current shape for less than a week as of this writing. Q3’s quarterly post will have the first real traffic curve.

What is next

The Q3 priorities in order:

App Store approval and the public launch beat

When Shopify’s App Store listing goes live, that triggers a coordinated launch sequence: HackerNoon op-ed, ProductHunt, HN, the Shopify subreddit, LinkedIn, X. The launch blog draft is already written and sitting in apps/shopify/LAUNCH_BLOG_DRAFT.md. The countdown starts the day Shopify approves.

Stripe Marketplace is already live so the Stripe push is more of a sustained content drumbeat than a single launch event.

WebClaw dashboard views for Stripe and Shopify

Pulling the integration data into clickable dashboard views. The CLI surface stays as the source of truth; the dashboard is a thin read layer on top. Target ship: mid Q3.

Multi-currency v1.x

The biggest functional gap. Q3 scope: FX rate management, period revaluation, presentation versus functional currency, and intercompany consolidation for the multi-entity case. This is a multi-week build and will get its own deep dive post when it ships.

Vertical content build-out

Of the ninety-five posts mapped in the blog universe, seventeen are live. The Q3 plan is twenty-six more posts focused on comparison and education content, plus the first batch of vertical guides (Shopify store accounting, SaaS accounting with Stripe ASC 606, agency time billing, restaurant prime cost). The point is to land in long-tail search for the buyer-intent queries that actually convert.

ERPClaw OS Phase 3

The self-extending architecture (the part that lets AI agents author new vertical modules within constitutional financial laws) is at Phase 2. Phase 3 ships in Q3 and adds the invariant engine to vertical generation, which means a generated module will have its GL behavior mathematically constrained at author time rather than at test time. There will be a separate launch post for this.

Numbers, honestly

This is the part I commit to keeping in every quarterly post. No vanity metrics, no creative framing.

Metric	End of Q2 2026
GitHub stars	~35 (across the org, eight weeks since first public commit)
Site traffic (erpclaw.ai)	TBD; site went live in current shape on 2026-04-26
Total installs	TBD; we do not phone home, so we count via opt-in registration only
Paying customers	0 (intentional; cloud managed launches Q4)
Revenue	$0 (intentional)
Modules shipped	48
Total actions	3,126
Database tables	789
Test count	7,627 (L0 constitutional + L2 contract + L3 smoke + invariant engine)
Public blog posts	17
Public docs pages	12
Marketing pages total	73

A few notes on the zeros and TBDs.

Revenue is zero because cloud managed does not launch until Q4 and the self-hosted product is intentionally open source and free. The business model is hosted plus support contracts, not feature gates. This is a deliberate trade for a slower revenue ramp in exchange for a faster install curve and a defensible open source moat.

Install count is TBD because ERPClaw runs locally on the user’s machine and does not phone home. We can count the opt-in registration page submissions and the GitHub clone count, but neither is a clean install number. If we shift to phone home telemetry later it will be opt-in and disclosed; I am not sure we will.

Site traffic is TBD because the seventy-three page version of the site has been live for less than a week. The next quarterly post will have the first real curve to look at.

The number I am personally watching most closely is GitHub stars, because it is the cleanest leading indicator of community pull. Thirty-five stars in eight weeks is not a viral curve. It is the seed phase. The bet is that the comparison and vertical content the team is shipping in Q3 plus the Shopify App Store launch will move the slope. Q3’s quarterly post will tell whether that bet paid off.

A note on the team

ERPClaw is built at AvanSaber Inc by a small co-founder team — me (Nikhil), my co-founder Varun, and a handful of advisors. On the engineering side day-to-day, I pair with Claude Code as a coding companion, which is how seventy-three pages, two deep integrations, seven thousand six hundred tests, and forty-eight modules ship at this cadence. If you want the engineering writeup of how that workflow actually runs, building ERPClaw with Claude Code is the long form version.

The reason I am flagging this is not humble bragging. It is that the AI-assisted small team economic curve is the thing I am most certain about over the next five years, and ERPClaw is the artifact I am building to test that curve. Every quarterly post will keep the team count and the artifact count visible together so you can watch the ratio.

How to follow along

If you want to actually try ERPClaw, the install is one command:

clawhub install erpclaw

Then talk to your assistant. It sets up your chart of accounts, suggests the modules you actually need, and gets you to a working ERP in about three minutes.

The docs are the right starting point if you want to read first. The demo is the right starting point if you want to see it move. The pricing page is the right starting point if you are trying to figure out what this is going to cost (still free; cloud managed pricing lands in Q4).

If you want to follow the build, the public repo is at github.com/avansaber. A star is the cheapest way to say the curve is bending the right way. An issue or a pull request is the most useful way.

The next quarterly post lands on the last Monday of July 2026. By then we will know whether the App Store listing landed, whether multi-currency v1 shipped on time, and whether the seventy-three page site is moving the traffic needle. I will tell you the truth either way.

That is what shipped. That is what is next. See you in Q3.