What's built, and what isn't.

Builder, editor and publish work; structured data verified in the generated pages.

Verified in the generated sites' HTML.

Fixed 22 September and verified on development: a summary of the business, its products and services for AI assistants. Reaches production at the next release.

Each site has its own sitemap, but a platform-wide sitemap address takes priority and answers instead, with the wrong pages. It also lists pages only, not blog posts or products.

Real Cloudflare integration; no customer domain created yet.

Answers visitors from the business's live timetable, prices, staff, events, shop and policies as cards; captures a lead when it can't answer; rate-limited per visitor.

Sign-in, shop orders and invoices, packs, subscriptions, downloads, returns, support tickets, profile and security all work.

Bookings are view-only today. A cancel-and-detail module exists but isn't connected; service invoices arrive by emailed link, not in the portal.

Answers from the customer's own bookings, orders, downloads and memberships. Read-only: it can't yet move a booking for them.

Send, verified inbound and a drag-and-drop builder all work.

Sending credential absent and unsubscribe routes unmounted. Deliberately not switched on until both are fixed.

Real Twilio integration and verified webhook; the missing callback settings landed 22 September and reach production at release.

Sync is built: details, hours and closures push to Google automatically on change, and services and products push once registered. New reviews are pulled into the Inbox every 15 minutes, with replies sent back. But connecting a Google account can't complete yet, because the Google app credential isn't configured, so none of it has run against Google. Posts, photos and insights call the wrong Google API, and the review-reply button on the profile page is a stub.

Products go to Google as service items, not a product catalogue. There's no Q&A, no working Merchant Center feed and no GEO visibility tracking.

White-label Stripe Connect accounts, a 7-step onboarding inside Simma, ID verification and an audited KYC trail. Live-mode keys not yet in production, by design before customers.

Shop, bookings, invoices, payment links and first membership charges go to the business's own account with Simma's fee taken. Refunds, disputes, payouts and Xero/QuickBooks sync work. Built and tested in Stripe test mode; switched to live keys before the first customer.

The plan prices (5% + 50p down to 2.5% + 25p) are stored and shown but not what's charged. The code uses older rates (about 1.5–3% plus a fixed fee), and takes no fee on in-person sales, recurring memberships or deposit balances. One rate source is the fix.

The code exists; none of it is on a schedule yet, so today it only runs when triggered by hand.

Not built. Not claimed on the Money page.

A future direction on Stripe's embedded-finance products, country by country. Nothing built.

Resolved on every page, with a precedence test for each pair of layers. 22 industries, 181 specialisms, 364 niches, 23 countries. A café is tested to receive none of a dance school's words, flows or menus.

The machinery runs, but franchise settings, and menus by specialism, niche or country, have no content yet. Website starting templates exist for dance schools only. The customer business-type picker offers four types and is admin-only.

Six languages are declared; French is partly translated. A business is one kind today, so a studio with a shop can't be both.

One definition of headcount, counted live and enforced by tests. By design it changes emphasis (marketing mode, setup, suggestions, AI context) and never hides a feature.

The feed engine and 7 publishers (waitlists, orders, stock, prospects, overdue invoices, content to approve, overdue tasks) are built. The new feed is behind a switch that's still off, so Home shows the older intranet feed with memory cards.

An idea card can be approved from Home; the plan, its steps and who approved them are recorded.

Agents are named identities with a list of permitted tools; every task step records whether a person or an agent did it; every agent action writes to the audit log.

Switched off on 14 September because suggestions appeared in the owner's own to-do list. It returns once agents have their own list.

Roles, limits and approval rules are designed; the reasoning engine they run on is live. As named, customer-facing agents they are the next build, and they appear on this site as vision.